What exists
Every concept this product names, and what it is today. A concept is in the beta only when a test that proves it passed against the running service.
| Concept | Today | What you get |
|---|---|---|
| Accounts | in the beta | By 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. |
| Organizations | in the beta | An organization groups people and projects, with the roles owner, admin, member and viewer. Owners and admins sign in with a second factor (an authenticator app's six-digit codes). |
| Management API keys | in the beta | A key reads your organizations and projects through the management API. It is shown once, never opens a database, and stops working when it is revoked or its owner leaves the organization. |
| Management API (/api/v1) | in the beta | https://control.agenticpostgresql.com/api/v1 manages accounts, organizations, members, invitations and keys, and creates and manages your projects, their branches, their connections and their backups. |
| CLI against the hosted service | in the beta | The login, logout, context, org and project commands sign in with a password and a second factor, or with a key, and act through the management API only. |
| Web console | planned | Not open yet. |
| Create a project | in the beta | A member of an organization creates a project on a slot the operator prepared, and claims its first administrator with a one-time token only they hold. On the Free plan an organization holds one project; 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. |
| Delete a project | in the beta | An admin or owner deletes a project with its data; the slot it ran on is never reissued, and its backups are kept by the operator. |
| Export a project | in the beta | A member exports a project's own data -- the app, api and public schemas -- as one archive, downloaded once by the person who asked within 15 minutes. |
| Region | in the beta | Every project runs in one location, the one server this beta runs on, and each project's record names it. |
| Compute size | in the beta | A member changes a project's compute size (small, standard or large -- every size is on the Free plan); the change restarts it, the message says for how long it was measured to take, and a size the server has no room for is refused with nothing changed. |
| Sleep and wake | in the beta | A member puts a project to sleep and wakes it; its data is kept, and while it sleeps its addresses and its database doors refuse connections and its backups stop, so its last restore point is the moment it went to sleep. |
| Sleep when idle | in the beta | A member may set a project to sleep after 15, 30 or 60 minutes with no request and no connection; it is off unless you turn it on. While it sleeps its backups stop, so its last restore point is the moment it went to sleep, and it wakes only when someone asks. |
| Pooled connection string | in the beta | A project's pooled connection string -- pool.<project domain>, port 5432, TLS required (sslmode=verify-full) -- reaches the project's own transaction pooler as its application role. The password is one your CLI generated (apg endpoint credential); it never left your machine. |
| Direct connection string | in the beta | A project's direct connection string -- direct.<project domain>, port 5432, TLS required -- reaches a session pooler as the project's administrator role, for migrations and tables in the public schema. Setting a role's password again (apg endpoint credential) replaces the previous one. |
| Wake on connect | planned | Not open yet. |
| Branches | in the beta | A member makes a branch of a project: a full copy restored from the project's own backups, with its own two passwords and its own two names. One branch per project on the Free plan. A branch is not backed up: deleting it, or losing the server, loses what it holds. An expiry, if you set one, deletes it then. |
| Restore to a new branch | in the beta | A member restores a project to a point in time inside its backup window, into a new branch; the project itself is never overwritten. |
| Restore a project in place | not offered | Not available, by decision. Restore to a new branch instead; your project is never overwritten by a restore. |
| Promote a branch | not offered | Not available, by decision. Apply the change to your main branch as a reviewed migration instead. |
| Query Insights | in the beta | Your statements' calls and time over a window, normalised; no recommendations. |
| Monitoring | in the beta | A short list of readings, each naming where it comes from. |
| Usage | in the beta | A project's usage over a window -- its database's size, its backup repository's, its branches, its connections, the requests it answered, its agent calls and workflow runs, the time it was awake and asleep -- read every five minutes; a figure that could not be read is said, never shown as zero. |
| Network egress usage | not metered | Not measured. Usage pages will not show network egress, provider calls or embeddings. |
| Free plan | in the beta | During the beta every organization is on the Free plan, at no cost: one project, one branch per project, every compute size; storage and agent calls are shown against usage and not enforced. |
| Premium plan | in the beta | The Premium plan is defined but not available during the beta. You can ask to be told when it is; nothing is charged, and nothing moves you onto it. |
| Notifications | in the beta | In-app notifications for an organization: one for every finished operation, and a notice once a day when a project passes 80% of a shown limit. Nothing is emailed. |
| planned | This beta sends no email. Invitations and password resets are handed to you by the person who issued them. | |
| Passkeys | planned | Not available yet. Owners and admins will use a password and a one-time code. |
| SQL editor | not offered | Not available, by decision. Connect with psql or your own client through your project's direct connection string. |
| Temporary support access | not offered | The operator of this single node has root on it; support access is not technically bounded in this beta. |
| Autoscaling | not offered | Not available. A project's size changes only when you resize it, and a resize restarts it. |
| High availability | not offered | Not available. Every project runs on one server; if it fails, your project is down until it is restored from backup. |
| Multiple regions | not offered | Not available. Every project runs in one location. |
| Service level agreement | not offered | Not available. This beta carries no uptime commitment. |
| Billing | not offered | Not available. The beta is free and takes no payment details. |
| PostgreSQL | in the beta | Projects run PostgreSQL 18 with pgvector. |
| Project isolation | planned | Not open yet. Each project will have its own database cluster, roles, network, volumes and credentials; projects on the server share only the edge that routes requests. |
| Backups and point-in-time recovery | in the beta | Backups are continuous to off-site object storage, with a nightly copy to a second provider; a project's restore window -- the span a branch can be restored to -- is shown with how recently it was read, and never shown when it could not be read. |
| Agents (MCP) | planned | Not open yet. |
| Workflows | planned | Not open yet. |
| Connectors | planned | Not open yet. |
| Audit log | planned | Not open yet. |