Skip to main content
Akter Cloud requires your own Postgres on every plan. Open an account with your database provider, choose a database size and backup policy, and pay that provider separately. Akter supplies hosted compute, not a database.

​
Choose the region first

Cloud runners start in Fly iad, Northern Virginia. Prefer AWS us-east-1 for your Postgres database, rather than a region close to your laptop. Akter probes from the runner region at deploy: p50 above 5 ms warns but does not block deployment. Your database’s latency and capacity still limit the app, even when Akter adds runners.

​
Provider options

RDS uses an AWS RDS CA bundle. Cloud’s current TLS rule requires a publicly trusted certificate and does not load a custom sslrootcert from the URL. RDS is not a usable option until its CA is trusted by Cloud; do not disable certificate verification to work around this.
These links explain provider setup, not provider-specific Akter certification. Check the framework’s support matrix for verified server versions and evidence boundaries. A successful deploy-time probe establishes connectivity, not backup, recovery or failover support.

​
Before you deploy

  • Use a direct, non-pooled URL to the writable database. Transaction poolers cannot preserve the session semantics the runtime needs and are refused.
  • Give your app’s role permission to create and alter its tables for migrations. Keep credentials and backups under your control.
  • Check available connections as well as database size. Akter budgets 9 connections per runner after subtracting connections already in use and a reserve of 10; Connect your Postgres explains the runner cap.
  • Use separate databases and roles for environments whose data must stay isolated. Akter never creates, copies or deletes those databases for you.
Next, set DATABASE_URL and deploy.