Skip to content
Gauge

ax-check.com

Qovery

qovery.com

ax-check.com

Checked 19 October 2026

B

84/100

Agents need your login

Qovery's docs and quickstart let agents install and deploy fast.

21 of 23 checklist items passed, with install commands, CLI, SDKs and an MCP server all documented; pricing is posted as plain text with clear units.

2 fixes to start with

Concrete changes, backed by what we found.

Onboarding

Give agents a clear login handoff and a way to resume setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Docs

Return Markdown when clients request text/markdown.

Homepage returned text/html even when text/markdown was requested; no Markdown representation offered.

Recorded coding sessions

Same task, 3 models, no qovery.com account. Recorded 19 October 2026 on Pi.

3 recorded · 41s

41s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
Help me build a simple example using Qovery. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.
Thinking…

The user wants me to build a simple example using Qovery, explain pricing, and assess whether it's easy to manage. Let me first check the environment — what's available. Let me check the repo.

Key constraint: "use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands". Also "If this product has no developer workflow you can act on, say so plainly and stop."

Qovery is a hosted deployment platform. It has a CLI and API. But using it requires credentials (API token), a cloud provider account (AWS/GCP/etc.) — actually Qovery deploys to YOUR cloud account. So it requires an actual cloud account and a Qovery account with auth. Without credentials, I can't do anything real.

Let me check the sandbox for any credentials or existing setup first.

Let me be practical: check env, check if there's a Qovery token, check if qovery CLI is installed, check network access to api.qovery.com.

Let me do these checks.

I'll check what's actually available in this environment before promising anything.

pwd && ls -la && echo "---GIT---" && git log --oneline -5 2>/dev/null | head -20
/sandbox/repo
/sandbox/repo
total 16
drwxr-xr-x 3 root root 4096 Sep 18 08:00 .
drwxr-xr-x 7 root root 4096 Oct 19 17:29 ..
drwxr-xr-x 8 root root 4096 Sep 24 20:05 .git
-rw-r--r-- 1 root root  408 Sep 18 08:00 .gitignore
---GIT---
9ebf5fb Initial workspace
echo "---QOVERY CLI---"; which qovery 2>/dev/null || echo "no qovery CLI"; echo "---ENV CREDS---"; env | grep -iE "qovery|aws|gcp|scaleway|azure|token|api_key|secret" | sed 's/=.*/=<redacted>/' || echo "none"; echo "---TOKEN FILES---"; ls -la ~/.qovery 2>/dev/null || echo "no ~/.qovery"; ls -la ~/.config 2>/dev/null
Failed---QOVERY CLI---
---QOVERY CLI---
no qovery CLI
---ENV CREDS---
AWS_CA_BUNDLE=<redacted>
PI_GATEWAY_API_KEY=<redacted>
---TOKEN FILES---
no ~/.qovery


Command exited with code 2
Thinking…

Empty repo, no Qovery credentials, no Qovery CLI. Let me check network access to Qovery's API to see if I can even reach it.

Let me check if the Qovery API is reachable and whether the SDK is installable (offline?).

Empty repo, no Qovery credentials. Let me check network reachability to Qovery's hosted API and whether its SDK is obtainable.

echo "---DNS/API---"; curl -s -o /dev/null -w "api.qovery.com: %{http_code} in %{time_total}s\n" --max-time 12 https://api.qovery.com/healthz 2>&1 || echo "curl failed"; curl -s -o /dev/null -w "api.qovery.com/: %{http_code}\n" --max-time 12 https://api.qovery.com/ 2>&1 || echo "curl failed"
---DNS/API---
---DNS/API---
api.qovery.com: 401 in 1.375661s
api.qovery.com/: 401
echo "---NPM PYPI REGISTRY---"; timeout 20 npm view qovery-client version 2>&1 | tail -3; echo "---pypi---"; timeout 20 curl -s -o /dev/null -w "%{http_code}\n" --max-time 12 https://pypi.org/pypi/qovery/json 2>&1
---NPM PYPI REGISTRY---
---NPM PYPI REGISTRY---
0.1.1
---pypi---
200
Thinking…

The API is reachable (401 = auth required, which confirms it's live and requires a token). SDKs exist on npm and PyPI.

So the hosted API is reachable and the SDK exists. But everything requires a Qovery API token — and critically, Qovery deploys to YOUR OWN cloud account (AWS/GCP/Scaleway/Azure), meaning a real deployment requires:

  1. Qovery account + API token
  2. A cloud provider account with IAM credentials
  3. The "Engine" that provisions infrastructure — historically Qovery's engine ran locally in Docker, now it's a managed/remote engine.

That's exactly the blocker: it's an infrastructure-provisioning platform, not a request/response API service. There's no "call an API and get a result" workflow I can complete without credentials. And the provisioning itself takes many minutes (cluster creation is long-running).

Let me verify the claim about pricing and the deployment model accurately rather than guessing. Let me check the Qovery docs for pricing. Let me try fetching their pricing page.

Let me be careful about accuracy. I should verify pricing from an authoritative source.

API is live (401 = needs a token) and SDKs are published. Let me verify the deployment model and pricing from primary sources rather than guessing.

cd /tmp && for u in "https://www.qovery.com/pricing" "https://hub.qovery.com/docs/pricing/"; do echo "=== $u ==="; timeout 25 curl -sL --max-time 20 -A "Mozilla/5.0" "$u" -o p.html -w "http=%{http_code} bytes=%{size_download}\n"; python3 - <<'EOF' 2>/dev/null
import re,html
try:
    t=open('/tmp/p.html',encoding='utf-8',errors='ignore').read()
    t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S|re.I)
    t=html.unescape(re.sub(r'<[^>]+>',' ',t))
    t=re.sub(r'\s+',' ',t)
    hits=[]
    for kw in ['$','USD','per month','/month','free','Engine','AWS','credit card','Scaleway']:
        for m in re.finditer(re.escape(kw),t):
            s=max(0,m.start()-90); hits.append(t[s:m.start()+110].strip())
    seen=set(); out=[]
    for h in hits:
        k=h[:60]
        if k not in seen: seen.add(k); out.append(h)
    for h in out[:14]: print(' *',h)
except Exception as e: print('err',e)
EOF
done
=== https://www.qovery.com/pricing ===
=== https://www.qovery.com/pricing ===
http=200 bytes=266664
 * ve 20% yearly Starter For startups shipping their first production app on their own cloud $299 per month Start 14-days free trial Billed yearly 3 users 14-days free trial, no credit card required 1 ma
 * Slack or Microsoft Teams Growth For teams running staging and production with monitoring $899 per month Start 14-days free trial Billed yearly 10 users Everything in Starter, plus 2 managed clusters,
 * cale Ideal for growing startups: expert support and the compliance your customers ask for $2,999 per month Y Combinator and Techstars startups get an additional discount on Scale. Contact us to get it
 * sponse See how we work Up to 25 users Everything in Growth, plus 3 managed clusters, then $4,788 per cluster per year 30,000 min of deployment per month SOC 2 Type II report, DPA and help with securit
 * und program We can help you fund your migration on AWS, GCP, Scaleway or Azure with up to $300k credits our partnership program Estimate funding Qovery for Startups Still in the early-stage? Qovery ca
 * Fixed limit, upgrade for more 2 Fixed limit, upgrade for more Up to 3 Additional cluster +$4,788 / year Unlimited Auto-scaling Automatically scale your workload resources. Wildcard domains Create wild
 * onthly deployment minutes Build and deployment time included each month. 3,000 min then + $0.16/minute 8,000 min then + $0.16/minute 30,000 min then + $0.16/minute Unlimited Built-in CI/CD Build and d
 * d and deployment time included each month. 3,000 min then + $0.16/minute 8,000 min then + $0.16/minute 30,000 min then + $0.16/minute Unlimited Built-in CI/CD Build and deploy applications without mai
 * each month. 3,000 min then + $0.16/minute 8,000 min then + $0.16/minute 30,000 min then + $0.16/minute Unlimited Built-in CI/CD Build and deploy applications without maintaining separate CI/CD infrast
 * y reviews. HIPAA (BAA) HIPAA compliance, including a signed Business Associate Agreement. $5,880 / year Included Compliance scope Compliance standards supported by the Qovery platform. SOC 2, GDPR SOC
 * of your services. Observe package Infrastructure observability for your managed clusters. $3,588 / cluster / year Included on 1 cluster then $3,588 / cluster / year Included on 1 cluster then $3,588 /
 * servability for your managed clusters. $3,588 / cluster / year Included on 1 cluster then $3,588 / cluster / year Included on 1 cluster then $3,588 / cluster / year $3,588 / cluster / year Support Sup
 * ster / year Included on 1 cluster then $3,588 / cluster / year Included on 1 cluster then $3,588 / cluster / year $3,588 / cluster / year Support Support level How fast and how deep the engineering te
 * 1 cluster then $3,588 / cluster / year Included on 1 cluster then $3,588 / cluster / year $3,588 / cluster / year Support Support level How fast and how deep the engineering team engages on your reque
=== https://hub.qovery.com/docs/pricing/ ===
http=200 bytes=345537
 * ernetes on AWS, GCP, Azure, or Scaleway. Managed by Qovery. No expertise required. 14-day free trial, no credit card required. Start for free → Was this page helpful? Yes No Raise issue Get Started wi
 * d by Qovery. No expertise required. 14-day free trial, no credit card required. Start for free → Was this page helpful? Yes No Raise issue Get Started with Qovery Qovery home page Pricing Changelog Ro
 * for humans and AI agents, running on your own infrastructure, whether on a public cloud (AWS, GCP, Azure, Scaleway…) or on-premise. Deploy on Kubernetes, AWS, GCP, Scaleway, or Azure without picking
 * ether on a public cloud (AWS, GCP, Azure, Scaleway…) or on-premise. Deploy on Kubernetes, AWS, GCP, Scaleway, or Azure without picking a lane. Describe what you want to deploy and an AI agent handles
 * New Deploy AI agents directly on your own infrastructure. Provision Managed Kubernetes on AWS, GCP, Azure, Scaleway. Ready in 30 min. BYOK supported. Observe Real-time logs, metrics, Kubernetes events
 * s Essential terminology ​ Ready to build the future of your infrastructure? Kubernetes on AWS, GCP, Azure, or Scaleway. Managed by Qovery. No expertise required. 14-day free trial, no credit card requ
 * GCP, Azure, or Scaleway. Managed by Qovery. No expertise required. 14-day free trial, no credit card required. Start for free → Was this page helpful? Yes No Raise issue Get Started with Qovery Qover
 * I agents, running on your own infrastructure, whether on a public cloud (AWS, GCP, Azure, Scaleway…) or on-premise. Deploy on Kubernetes, AWS, GCP, Scaleway, or Azure without picking a lane. Describe
 * public cloud (AWS, GCP, Azure, Scaleway…) or on-premise. Deploy on Kubernetes, AWS, GCP, Scaleway, or Azure without picking a lane. Describe what you want to deploy and an AI agent handles the rest,
 * nts directly on your own infrastructure. Provision Managed Kubernetes on AWS, GCP, Azure, Scaleway. Ready in 30 min. BYOK supported. Observe Real-time logs, metrics, Kubernetes events. No setup requir
 * ogy ​ Ready to build the future of your infrastructure? Kubernetes on AWS, GCP, Azure, or Scaleway. Managed by Qovery. No expertise required. 14-day free trial, no credit card required. Start for free
Thinking…

Now I have authoritative pricing. Key finding: "Provision Managed Kubernetes on AWS, GCP, Azure, Scaleway. Ready in 30 min." — that confirms cluster provisioning takes ~30 minutes, which is a long-running operation.

Critical blockers:

  1. No Qovery API token → every API call returns 401. I cannot authenticate.
  2. Qovery deploys to YOUR OWN cloud account — requires AWS/GCP/Azure/Scaleway credentials. None present.
  3. The product is an infrastructure-provisioning platform. The minimum unit of work is creating a cluster (~30 min) + deploying apps. That's explicitly a long-running operation.

So per the user's instructions: "If this product has no developer workflow you can act on, say so plainly and stop." and "Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop."

Let me verify the auth requirement concretely by making an actual API call, to demonstrate the 401. And let me confirm the SDK exists and what its interface requires. This gives me evidence.

Let me do a quick check on the API to show it needs auth, and check the SDK/quickstart requirements.

Actually, let me quickly check the quickstart docs to confirm what it requires (cloud account + token + cluster creation time).

Let me do both in parallel.

Confirmed authoritative pricing. Now let me verify the hard blockers concretely: whether any API call can succeed without a token, and what the quickstart actually requires.

echo "=== Real API calls (no token) ==="; for ep in "user" "organization" "cluster"; do printf "%-14s -> " "$ep"; curl -s -o /tmp/r.json -w "%{http_code} " --max-time 12 "https://api.qovery.com/$ep"; head -c 160 /tmp/r.json; echo; done
=== Real API calls (no token) ===
=== Real API calls (no token) ===
user           -> 401 
organization   -> 401 
cluster        -> 401 
cd /tmp && timeout 25 curl -sL --max-time 20 -A "Mozilla/5.0" "https://hub.qovery.com/docs/getting-started/" -o g.html -w "http=%{http_code}\n"; python3 - <<'EOF' 2>/dev/null
import re,html
t=open('/tmp/g.html',encoding='utf-8',errors='ignore').read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S|re.I)
t=html.unescape(re.sub(r'<[^>]+>',' ',t)); t=re.sub(r'\s+',' ',t)
for kw in ['AWS','credentials','IAM','cluster','30 min','token','Kubernetes','own cloud','account']:
    for m in list(re.finditer(re.escape(kw),t))[:2]:
        s=max(0,m.start()-110); print(' *',t[s:m.start()+130].strip())
EOF
http=200
http=200
 * rnetes control plane for humans and AI agents, running on your own infrastructure, whether on a public cloud (AWS, GCP, Azure, Scaleway…) or on-premise. Deploy on Kubernetes, AWS, GCP, Scaleway, or Azure without picking a lane. Describe wha
 * n infrastructure, whether on a public cloud (AWS, GCP, Azure, Scaleway…) or on-premise. Deploy on Kubernetes, AWS, GCP, Scaleway, or Azure without picking a lane. Describe what you want to deploy and an AI agent handles the rest, or use the
 * es, sleep mode, right-sizing. Up to 60% cost savings. BYOK = Bring Your Own Kubernetes: connect your existing cluster to Qovery ​ Get Started Migrate to Kubernetes Leave Heroku, Render, or Railway. No re-architecture required. Deploy with A
 * ents directly on your own infrastructure. Provision Managed Kubernetes on AWS, GCP, Azure, Scaleway. Ready in 30 min. BYOK supported. Observe Real-time logs, metrics, Kubernetes events. No setup required. Secure SOC2, GDPR, HIPAA, DORA. RBA
 * es Core Products Security & Compliance Maintenance How-to Guides Production Environment Management Migrate to Kubernetes Ephemeral Environments Tutorials Deploy Your First Application Create a Database Database Seeding with Lifecycle Jobs A
 * Tutorials Troubleshooting Troubleshooting Useful Resources FAQ Help and Support Get Started Introduction The Kubernetes control plane for humans and AI agents, on your own infrastructure, cloud or on-premise. ​ Welcome to Qovery Qovery is
Thinking…

I now have solid evidence. Let me stop here per instructions.

Summary of findings:

  • API live but every endpoint returns 401 without a token
  • No Qovery token in env, no ~/.qovery config
  • Qovery is not a "call an API, get a result" service — it's a Kubernetes control plane that provisions infrastructure into YOUR OWN cloud account (AWS/GCP/Azure/Scaleway)
  • No cloud credentials present either
  • Minimum unit of work = provision a managed Kubernetes cluster, "Ready in 30 min" — explicitly long-running
  • SDKs exist (npm qovery-client 0.1.1, PyPI qovery) but they're just API clients — useless without auth

So: the product DOES have a developer workflow (API/SDK/CLI, "Deploy Your First Application" tutorial), but I cannot act on it. The instruction says "If this product has no developer workflow you can act on, say so plainly and stop." The key qualifier is "you can act on" — I can't. So I stop.

Let me be honest and precise. I should not fabricate an example app that "uses Qovery" since nothing could run. But I could note what I'd need. Actually, let me consider: should I write any code? The instruction says stay light, use hosted product through SDK/API. I'm blocked at auth. Writing a speculative example that can't be validated would be misleading. I should stop and report.

Let me not over-produce. Let me report clearly.

One thing: I should double check whether there's maybe a free tier / no-account-needed path. The pricing shows Starter $299/mo with 14-day free trial no credit card. No free tier. So minimum cost is $299/mo (billed yearly) — wait, "$299 per month ... Billed yearly". So it's $299/mo billed annually = $3,588/year. And trial is 14 days.

Also note: you pay Qovery AND your cloud bill (infrastructure runs in your own account). That's the key pricing insight.

Let me also note the deployment minutes overage: 3,000 min then +$0.16/min.

Add-ons: additional cluster +$4,788/year, Observe package $3,588/cluster/year, HIPAA BAA $5,880/year.

Let me clean up temp files and report. Actually the temp files are in /tmp, and I didn't modify the repo. Let me verify repo is untouched.

Let me give the final answer. Be concise but complete on the three asks:

  1. Pricing
  2. Easy to manage?
  3. Blocked — say plainly and stop.

Let me check the repo is clean.

cd /sandbox/repo && git status --short && echo "repo clean: $(git status --porcelain | wc -l) changes"; rm -f /tmp/p.html /tmp/g.html /tmp/r.json
repo clean: 0 changes
repo clean: 0 changes
Thinking…

Time to put together the final report.

Blocked — stopping here

I did not build an example. Every Qovery API endpoint returns 401 without credentials, and there are none in this environment:

CheckResult
api.qovery.com/user, /organization, /cluster401 (live, needs token)
Qovery API token in env / ~/.qoveryabsent
Cloud provider creds (AWS/GCP/Azure/Scaleway)absent
Qovery CLInot installed
SDK availabilitypresent (qovery-client 0.1.1 on npm, qovery on PyPI)

The SDKs are just HTTP clients — useless without auth, so there was nothing to verify against.

Why this isn't a credentials-only blocker. Qovery is not a request/response API product. It's a Kubernetes control plane that provisions infrastructure into your own cloud account, so acting on it requires both a Qovery token and IAM credentials for AWS/GCP/Azure/Scaleway. The minimum unit of work is creating a managed cluster, which their own docs describe as "Ready in 30 min." That's a long-running provisioning operation — exactly what you told me not to wait on. So even with credentials handed to me right now, I couldn't complete a real deploy inside this session. I left the repo untouched (0 changes).

Pricing

From qovery.com/pricing — paid platform, no free tier:

  • Starter $299/mo (billed yearly, so $3,588/yr) — 3 users, 1 managed cluster, 3,000 build/deploy minutes
  • Growth $899/mo — 10 users, 2 managed clusters, 8,000 minutes
  • Scale $2,999/mo — up to 25 users, 3 clusters, 30,000 minutes; YC/Techstars get a discount
  • Overage: +$0.16/minute past your allowance (Scale = unlimited minutes)
  • Add-ons: extra cluster +$4,788/yr · Observe package $3,588/cluster/yr · HIPAA BAA $5,880/yr
  • Trial: 14 days, no credit card required

The part that catches people out: you pay twice. The above is Qovery's platform fee only. Because workloads run in your cloud account, your AWS/GCP/Azure/Scaleway bill is separate and uncapped by Qovery — that's usually the larger number. Their stated value prop is reclaiming that via sleep mode and right-sizing ("up to 60% cost savings"), which is a claim about your infra spend, not their fee.

Would this be easy for me to manage?

No — and the reason is structural, not a knowledge gap. Qovery's whole purpose is long-lived state: clusters, databases, environments that exist for weeks and cost real money per hour. That's the opposite of the fast, disposable, verifiable loop I work well in. Specifically:

  • Feedback is slow. A cluster takes ~30 min; deploys take minutes. I can't iterate — each attempt is a long wait, which you've explicitly ruled out.
  • Changes are hard to verify cheaply. I can't confirm a deploy succeeded without polling long-running jobs, and I can't safely roll back state I created in your paid cloud account.
  • Blast radius is real. A mistaken API call provisions billable infrastructure or touches production. There's no sandbox to experiment in — the 14-day trial still runs against your cloud account.
  • Two credential domains. Debugging needs both Qovery and cloud-provider context, and failures span layers I can't see (your VPC, IAM policies, quota).

What I can do well here, once you decide it's worth it: read and explain Terraform/K8s manifests Qovery generates, write the qovery.yml app descriptor, review IAM policies before you grant them, or drive the API for read-only operations (list clusters, fetch status, pull logs) where a token alone is enough and nothing is mutated. Those are safe and fast. Provisioning and deploying should stay human-supervised.

If you want me to proceed, tell me which: (a) you'll supply a Qovery token and I'll do read-only API exploration to validate the workflow, or (b) you'd rather I write an unvalidated example qovery.yml + deploy script that you run yourself. I'd suggest (a). Otherwise, this is where I stop.

AX Fundamentals

23 checks. Open an area for details.

This check is a quick preview. Test more tasks and models with Gauge Agents.

Test your product with Gauge Agents

AX Check by Gauge