Deploy flow: git push -> CI build -> live HTTPS app with PostgreSQL
Clouderized treats databases as workloads in your plan, not as a separate add-on. Your app container and database container share the Starter or Pro resource pool you buy. If you want the base runtime model first, see docker hosting for backend apps.
Same pool
CPU, RAM, and storage are allocated across your app containers and database containers.
Managed setup
PostgreSQL or MariaDB is provisioned with persistent storage and connection details for your app.
Flat pricing
Choose Starter or Pro capacity upfront instead of stacking a separate app plan and database plan.
Which capacity fits?
| Capacity | Monthly price | Best fit | Database note |
|---|---|---|---|
| 1 Starter | S$5 | One lightweight app, several tiny apps, lightweight app plus lightweight MariaDB/MySQL, or PostgreSQL-only | PostgreSQL usually consumes the full 512 MB RAM pool. |
| 2 Starter | S$10 | Small app plus PostgreSQL, or multiple small services with more database headroom | Good entry point when app and PostgreSQL need to live together. |
| 1 Pro | S$15 | Always-on APIs, JVM apps, WebSockets, workers, and heavier app plus database workloads | Best fit when cold starts or tight memory are unacceptable. |
Good fits for Docker plus PostgreSQL
This page is for backend developers who want a normal containerized app with a relational database, without managing a VPS by hand.
FastAPI or Flask
Small APIs, dashboards, and internal tools with PostgreSQL persistence.
Node backends
Express, NestJS, or webhook services that need a relational database.
Rails and Django
Backend-heavy apps that benefit from predictable capacity and persistent storage.
Java and Scala
JVM apps should use Pro so the app stays warm and has enough memory.
PostgreSQL hosting FAQ
Can I host a Docker app with PostgreSQL?
Yes. Clouderized supports Dockerized backend apps with managed PostgreSQL. PostgreSQL runs inside your Starter or Pro resource pool.
Is PostgreSQL a separate add-on?
No. Managed PostgreSQL and MariaDB are included inside your Starter or Pro resource pool. Apps and databases share the included CPU, RAM, and storage.
Can 1 Starter run an app and a database?
Yes for a lightweight app plus lightweight MariaDB/MySQL. PostgreSQL usually consumes the full 512 MB Starter RAM pool, so PostgreSQL plus an app usually needs 2 Starter units or Pro capacity.
When should I choose Pro?
Choose Pro for JVM apps, always-on services, WebSockets, long-running workers, or app plus database workloads that need more memory and no idle sleep.
Try Docker hosting with a real backend app
Book a free 4-hour sandbox, push code, and validate whether your app and database fit Starter or Pro capacity.
Book a Free 4-Hour Trial