Features

Isolated database cells

A dedicated PostgreSQL process per project, with its own storage, credentials, and CPU and memory limits. Not a schema in a shared database.

Direct and pooled connections

A standard postgres:// URL on the direct port, and a transaction pooler on the pooled port for serverless and edge runtimes. Same database, two doors.

Extensions

A curated catalog you enable per cell, kept current in-database rather than left to drift behind the packaged version.

Isolation and security

Private network namespace, no egress from standard cells, SCRAM relayed rather than held, and API keys stored only as hashes.

Preview databases

A full copy of your database, cloned rather than dumped, with a time to live. One per pull request, torn down when the branch merges.

Imports and migrations

Bring a database over from another managed provider or from your own server, with a follow mode that stays in sync until you cut over.

Schema tooling and typegen

Dump and diff your schema from the CLI, and generate TypeScript types, Zod schemas, or Drizzle definitions from the live database.

Studio

A SQL editor in the dashboard with schema browsing, linting, and a restore point taken before anything destructive runs.

K/V stores

A key-value store in its own isolated cell, in the same region as your database. Use it for rate limiting, sessions, queues and caching - or on its own, with no database involved.

Rate limiting

Sliding-window, fixed-window and token-bucket limiters through @upstash/ratelimit, checked against a store that sits beside your application rather than an ocean away.

Clients you already use

The Upstash REST protocol and RESP, both supported. @upstash/redis, ioredis, redis-py and redis-cli connect unmodified - there is no CapyDB client to adopt.

Backups and point-in-time restore

Continuous off-node archiving with restore to any moment inside your retention window, plus scheduled verification that the restore actually works.

Observability

Resource usage, connection counts, and query-level drill-down per cell, with alerts on the conditions that actually precede an outage.

Alerts

Notifications on the conditions that actually precede an outage - storage pressure, backup staleness, connection saturation - delivered by email or to your own webhook.

Pause when idle

An untouched cell goes to sleep and stops consuming its share of the node. The next connection wakes it, typically inside a quarter of a second.