Projects and test branches
Create projects and separate branches to test changes without affecting the main branch.
Create projects, test changes on separate branches, and manage your databases in one place.
Sign in with an account provided to you. Self-service registration is currently unavailable.
PostgreSQL 17
mainMain branchdevTest branchSELECT 1 AS result;| result |
|---|
| 1 |
From testing to day-to-day operations, the tools you need are here.
Create projects and separate branches to test changes without affecting the main branch.
Start, stop, resize, and automatically pause database compute when idle.
Run SQL, save queries, and review your account’s query history.
Track database activity, resource usage, and costs.
Manage branch backups and restore data when you need to.
Manage users, access permissions, and connection details.
Standard user accounts need an active USDT plan. Check your plan in Billing before creating a project.
Create your project and choose PostgreSQL 14, 15, 16, or 17.
Create a separate branch to try changes before applying them to the main branch.
Start the branch's database compute, then use the SQL editor or connect your application with a PostgreSQL client.
Pageserver stores database data and manages the timelines used by branches.
Safekeepers replicate PostgreSQL change logs, called WAL, to support data recovery.
Compute runs PostgreSQL queries. You can adjust its resources separately from storage. PostgreSQL 14–17 is supported.
Reference prices. Confirm current prices and limits in Billing.
20USDT/month
50USDT/month
100USDT/month
200USDT/month
CU is a unit of database compute resources. One CUh is one CU running for one hour. These monthly limits apply to your account.
USDT payments require administrator approval. Opening Billing does not create a payment request.
Sign in with an account provided by your administrator. Standard user accounts need an active USDT plan to create projects and test branches. Check your plan in Billing. Self-service registration is currently unavailable.
A branch is a separate version of your database for testing. Changes on the test branch do not change the data on the main branch.
When configured for a compute, automatic pausing stops it after a period without activity. Check the pause settings and current compute state in your project.
Open Billing to confirm your plan and create a payment request. Follow the USDT transfer instructions, submit the transaction reference, and wait for an administrator to verify it.