A first-party overview, not an independent review.
Best for: developers who can build an app but do not want to run infrastructure; anyone leaving usage-based hosting after a surprise bill; people who want their app on their own server with a modern deploy experience.
Not ideal for: teams that need fully managed auto-scaling serverless with zero infrastructure responsibility; teams that require a public SLA and status page today; workloads that specifically need a self-hostable, open-source control plane (see Coolify).
Pros:
- Push-to-deploy from a GitHub repo, with deploys on push and one-action rollback.
- Native systemd runtime, no required Docker; lower overhead than a container stack.
- Ops on by default: HTTPS, monitoring, 30-day logs, and manual backups (scheduled backups on paid plans).
- Fixed, predictable price and no lock-in, because you own the server.
- AI + MCP with scoped permissions and confirmation; multi-provider including GPU; 85+ one-click templates.
Cons:
- AWS provisioning covers selected regions and instance families, not the full AWS surface.
- Guardrail story is real but still maturing in places.
- No public SLA or status page yet (two-founder company).
- The low price can read as hobby-grade.
- You keep infrastructure responsibility.