Free
For side projects, prototypes and agents.
$0per month
- 1 organization
- 5 projects
- 2.5 GB storage0.5 GB per project included
- Unlimited shared compute hoursEarly bird special
Serverless PostgreSQL 17
Postgres that branches like code.
Spin up a database in seconds, give every pull request and every AI agent its own branch, and connect with the drivers you already use.
- Free plan
- No credit card
- Sign in with GitHub or Google
- PostgreSQL major version, not a lookalike
- 17
- to start, with no credit card
- $0
- projects on the Free plan
- 5
- GB of storage included free
- 2.5
Platform
Everything a Postgres app needs, already wired up
Real PostgreSQL plus the pieces you would otherwise assemble yourself: branches, separate storage and compute, auth, vectors and an API.
Branch the database, not just the code
A branch is a copy-on-write fork of its parent with the full data set. It is ready in seconds whatever the size, so every pull request, test run or agent can have its own.
Compute that sleeps when you do
Each branch runs on its own compute, sized in CUs (1 CU = 1 vCPU + 4 GB RAM). Storage lives separately, so an idle compute can suspend and resume on the next connection without touching your data.
- Preview
Managed auth next to your data
Turn on managed auth for a branch to sign in your app's users. Tokens are short-lived, EdDSA-signed JWTs published through JWKS; verify them in a few lines with the open-source @relyt/auth SDK.
Vector search built in
The vectors extension (pgvecto.rs) is preloaded in every database, so embeddings live next to the rows they describe and you query them with plain SQL.
Made for coding agents
An open-source skills pack teaches Claude Code and other agents to create projects, branch and connect, through the same Open API you use.
See what your database is doing
Charts for CPU, memory, connections and storage, plus live active queries and query history for every compute.
Automate everything
A REST Open API with API keys covers organizations, projects, branches and computes, so scripts and CI can do anything the console can.
Developers
From sign‑in to SELECT in a minute
No new client and no proprietary protocol. If it speaks Postgres, it works with Relyt One.
- 01
Sign in
Use GitHub or Google. A free organization is created for you.
- 02
Create a project
It starts with a main branch and a primary compute, ready in seconds.
- 03
Connect
Paste the connection string into psql, an ORM or any PostgreSQL driver.
# connection string from the console's Connect dialogexport DATABASE_URL="postgresql://<role>:<password>@<host>/<db>"psql "$DATABASE_URL" -c "select version();"Open source
The tooling around it is open
MIT-licensed and on GitHub. Read it, fork it, send a pull request.
relytcloud/relyt-auth-jsVerify managed-auth tokens on the server and cache them in the browser. Published on npm as @relyt/auth.
relytcloud/relyt-auth-examplesExample apps, starting with a multi-user to-do list built on managed auth.
relytcloud/agent-skillsSkills that teach coding agents how to create and branch Relyt One databases.
- Browse examples
Pricing
Start free. Upgrade when you're ready.
Every account starts on the Free plan. No credit card required.
Pro
Coming soonFor production apps that need more room.
- 1 organization
- 50 projects
- 20 GB storagethen $0.25 per GB
- 500 compute hoursthen $0.10 per CU hour
Blog
Latest from the blog
Why Postgres IDs skip numbers, and how to fix "duplicate key" errors after an import
Where gaps in PostgreSQL serial and identity columns come from (rollbacks, ON CONFLICT, crashes, CACHE), why inserts fail with duplicate key value violates unique constraint after a data import, one query that resets every sequence, running out of integer IDs, and gapless invoice numbers. Every statement reproduced on Postgres 17.11.
Postgres as a job queue: FOR UPDATE SKIP LOCKED, done right
How to build a background job queue in PostgreSQL 17 with SELECT ... FOR UPDATE SKIP LOCKED: why the naive SELECT-then-UPDATE claims the same job twice, why FOR UPDATE alone makes workers wait, leases and retries, LISTEN/NOTIFY, vacuum, and what polling workers do to a serverless compute. Every statement reproduced on Postgres 17.11.
INSERT ... ON CONFLICT vs MERGE in Postgres: which upsert to use, and the errors each one throws
When to upsert with INSERT ... ON CONFLICT and when to use MERGE in PostgreSQL 17, why MERGE can fail with a duplicate key error under concurrency, and how to fix 'cannot affect row a second time', empty RETURNING and 'no unique or exclusion constraint matching the ON CONFLICT specification'. Every statement reproduced on Postgres 17.11.
FAQ
Questions, answered
What is Relyt One?
Relyt One is a serverless PostgreSQL service. You get standard PostgreSQL 17 with database branching, storage separated from compute, managed auth for your app's users and built-in vector search, all run for you in the cloud.
Is it real PostgreSQL?
Yes. Relyt One runs PostgreSQL 17, so your existing drivers, ORMs and tools such as psql work unchanged, along with extensions like pg_trgm, citext and pgcrypto.
What does the Free plan include?
One organization, up to 5 projects, 2.5 GB of storage and unlimited shared compute hours as an early-bird offer. No credit card is required.
How does branching work?
A branch is a copy-on-write fork of its parent. It shares unchanged data with the parent, so creating one takes seconds regardless of database size, and only the changes take up new storage.
Can AI agents use Relyt One?
Yes. With an API key, agents can create projects, branches and computes through the Open API, and the open-source agent skills pack shows them how.
Do I have to use managed auth?
No. Managed auth is optional and currently in preview. Without it, Relyt One is a regular PostgreSQL database that you connect to with a role and password.
Your next database is one branch away.
Create a free project in under a minute. No credit card, no setup.