A SQL database that sleeps when idle.
Connect with any SQL client. It wakes on the first connection and stops when idle; you pay for its compute time and its data. Branch it, go back in time.
What you get
Any SQL client
psql, pg, Prisma, Drizzle and any other SQL driver, over an encrypted connection. Your existing code does not change.
On with a connection, off when idle
The first connection wakes the database and later ones share it. When idle it sleeps, and the data stays.
Branches
A full copy of the database in a moment, without copying the data: from its latest state or any time in its history. For tests, migrations or reports.
A branch per preview
Each app or function preview gets its own database branch, removed with the preview. Production data stays safe.
Restore to a point in time
Bring a branch back to its state at any moment in its history. The state before is kept as a backup, so a restore can be undone too.
History by plan
Hobby keeps 1 day of history and Pro keeps 7 days.
env.DB in functions
Bind a function or app to the database and run SQL with no connection string or password.
Observability
Compute time, size, connections, cache hit ratio and your most frequent SQL statements.
A narrow role
Your database user can do anything with its own data, and has no way into the server or anyone else's database.
Create, connect, branch
Every branch has the same host; only the database name in the connection changes: branch--database.
cloudhost db create shop
# host shop.database.trustpage.ir:5432
# user app
# password shown oncePay for work, not for a server
Compute counts only while the database is awake; data is billed per GB-month. Hobby includes a free amount each month.
Questions
No. No server stays on for you. The database starts with a connection, stops when idle and costs what you use. You only ever see a connection address.
The connection that wakes the database takes a little longer; later connections use the running database. We will publish an official figure once it is measured on the production infrastructure.
No. A branch starts from the same data and keeps only its own changes apart, so making one is immediate and it takes no extra space until it changes.
Up to 50 branches and previews per database. Backups made by a restore are counted apart.
As far as your plan keeps history; the pricing table shows each plan's amount.
From anywhere with internet access, encrypted. From our own functions and apps, with no password, through env.DB.
Yes. It is a standard SQL database; pg_dump works over a normal connection.
Create a database
One command, one connection address.
Sign-up is by invite for now. If you have a code, create your account.
Sign up withEmail codeSMS code