Should I self-host or use Qodex cloud?
Use Qodex Cloud unless you have a clear reason to operate Qodex yourself. The product experience is meant to be the same. The difference is where the infrastructure runs, who maintains it, and where your data lives.Choose Qodex Cloud when
- You want the fastest onboarding path.
- You do not want to manage Postgres, blob storage, containers, or upgrades.
- Your security review allows SaaS.
- BYOK gives you enough provider billing control.
- Your application is reachable from Qodex Cloud.
Choose self-hosted when
- Test data, findings, screenshots, or transcripts must stay in your infrastructure.
- Your app is reachable only from a private network.
- Compliance requires your own cloud account, VPC, region, or controls.
- LLM traffic must go through an internal proxy or AI gateway.
- Your team already operates the required infrastructure and wants Qodex inside that stack.
What changes operationally
| Area | Qodex Cloud | Self-hosted |
|---|---|---|
| Infrastructure | Operated by Qodex | Operated by your team |
| Postgres | Managed by Qodex | Your database |
| Artifact storage | Managed by Qodex | Your storage backend |
| Updates | Applied by Qodex | You deploy new versions |
| Network access | SaaS connectivity | Your VPC, firewall, and egress controls |
| Secrets | Managed by Qodex platform | Managed by your secret store |
Data residency rule
If scenario data, findings, screenshots, memory, and transcripts must live inside your infrastructure, choose self-hosted. If that is not required, Qodex Cloud is usually simpler and faster.Next steps
Self-hosted overview
See what self-hosting requires.
Single-container deploy
Try the smallest self-hosted setup.
Plans and pricing
Compare plan behavior.
AWS Terraform reference
Review the production AWS shape.