Hosted PostgreSQL 18 that only claims what it has proven.
Your team's own PostgreSQL 18 projects, with pgvector, on one hosted server. Each project has a pooled and a direct connection, both over TLS; a branch is a full copy you can restore to a point in time; backups run continuously off-site, and the console shows the window you can restore to.
Request an invitation Read the quickstart Already invited? Open the console
pool.[domain]:5432direct.[domain]:5432Mon 19 Oct 02:00 UTCLatest restore point
Fri 23 Oct 08:40 UTC
apg branch create --branch before --password-dir ./branches --at 2026-10-23T08:40:00Z --waitWhat every project gives you
Two connections, both over TLS
- Pooled connection stringin the beta
- Direct connection stringin the beta
Every project has two doors, both on port 5432 and both requiring TLS (sslmode=verify-full): the pooled door for your application, the direct door for migrations.
Pooled is a transaction pooler as customer_app; direct is a session pooler as customer_admin.
Branches you can restore to a moment
- Branchesin the beta
- Backups and point-in-time recoveryin the beta
A restore makes a new branch at a moment inside the project's backup window; the project itself is never overwritten.
A branch is not backed up: deleting it, or losing the server, loses what it holds.
Continuous off-site backups
- Backups and point-in-time recoveryin the beta
Backups run continuously off-site, and the console shows the window you can restore to.
While a project sleeps its backups stop: its last restore point is the moment it went to sleep.
Numbers that name their source
- Monitoringin the beta
- Usagein the beta
- Query Insightsin the beta
A short list of readings about a project, each with the moment it was read and where it comes from -- or not read, with the reason.
There is no threshold, no colour and no alert: the reading and its age.
From invitation to connection string
Accept your invitation
Open the link you were sent: choose a username and a password. The link works once and expires.
Create your organisation
An invitation to the beta opens an account; New organisation on the console's overview makes yours, and you are its owner.
Set up your second factor
Owners and admins sign in with a six-digit code from an authenticator app. The console shows a QR code: scan it with the app.
Create a project
Your organisation's New project in the console: a name, a size and the project administrator's username. The page shows a token once -- save it if you will claim the administrator from a terminal -- and links to Connect when the project is ready. Or, from a terminal:
pipx install agentic-postgres-cli
apg project create --name NAME --profile small --admin-username ADMIN
apg project claimConnect
Set a new password for the pooled door; the console shows the password and the connection string once.
apg endpoint credential --role app --password-file ./app-password --wait
apg endpoint connect --role app --password-file ./app-password44 concepts. 25 of them work today.
- in the beta, 25
- being verified, 2
- planned, 8
- not metered, 1
- not offered, 8
Every concept this product names, with what it is today -- generated from the same file the product checks itself against.
- Accountsin the betaBy invitation only. A person who receives an invitation creates an account with a password and signs in to the management API; there is no public signup.
- Create a projectbeing verifiedBeing verified: a member of an organization creates a project in the console or with the command-line client, on a slot the operator prepared. The console follows the creation step by step -- each step's time and the usual total, about 23 to 28 minutes, with no percentage -- on a page that a refresh reads again, and the organization's Activity lists every operation. The one-time token it shows once is optional: it claims the project's first administrator from a terminal, and connecting does not need it. On the Free plan an organization holds one project, one being created included; a second is refused with "plan limit reached", and when no slot is ready the request is refused with "capacity exhausted" -- in both cases nothing is created.
- Wake on connectplannedNot open yet.
- Network egress usagenot meteredNot measured. Usage pages will not show network egress, provider calls or embeddings.
- Restore a project in placenot offeredNot available, by decision. Restore to a new branch instead; your project is never overwritten by a restore.
Free during the beta
During the beta every organisation is on the Free plan, at no cost.
| Limit | Free | Premium |
|---|---|---|
| Active projects | 1 | 3 |
| Branches per project | 1 | 3 |
| Compute sizes | small, standard, large | small, standard, large |
| Storage | 5 GB of database | 20 GB of database |
Pricing lists what each plan allows.
The beta is invite-only.
There is no public signup. To ask for an invitation, write and say who you are and what you would build. The invitation arrives as a link; opening it creates your account.