TECHNICAL REFERENCE
Plans and PostgreSQL
Application slots, shared resources and database beta scope.
Service resources are shared
Applications and attached managed databases share the service’s CPU, RAM and disk limits. Do not assume each application receives the whole plan’s resources independently.
The permanent free plan is not a trial. Each account can have only one non-terminated free service. Its current limits are 0.5 vCPU, 512 MB RAM, 2 GB disk and one application. Use the live catalog and pre-payment invoice for currency, tax and campaign eligibility.
Optional setup packages
Setup packages are optional, one-time services. You can always set up your applications yourself at no charge. Prices are fixed per currency (USD / EUR / TRY) and are not converted.
Quick setup (49 USD / 49 EUR / 1,799 TRY, 2 business days): one app with a Git repository, Dockerfile or automatic detection, domain and SSL, environment variables, one database connection and a live check. Migration (149 USD / 149 EUR / 5,490 TRY, 5 business days): up to 3 apps and 1 database moved from Heroku, Vercel, a VPS or a Compose project. Agency starter (390 USD / 390 EUR / 14,490 TRY, 10 business days): up to 10 client projects plus an onboarding workshop.
Quick setup is free for the first project of the first 10 design partners and is included with a yearly prepaid Standard or Pro plan. The founder discount does not apply to setup packages. Request one at /contact?topic=setup.
Managed PostgreSQL
PostgreSQL can be created as a beta managed database attached to a container service. The public installation’s default quota is three managed databases per service; the limit reported for the particular service is authoritative. Creating a database does not create a separate database subscription.
Get the private endpoint and credentials from the panel. Connect the application and database through the service’s private network. Set DATABASE_URL in the actual application runtime; keep it out of the repository.
API and database are separate resources
An API application consumes one application slot. A managed database uses the separate database quota. Installing a database inside an application image is a different arrangement with different resource, storage and backup responsibilities.