Forge backend infrastructure

Forge runs inside an application backend. It provides key/value storage, queues, pub/sub, blobs, authentication helpers, rate limits, schedules, and configuration through one contract. PostgreSQL is the shared durable backend; memory is the process-local test backend. Blob bytes may also use a filesystem or S3-compatible store.

The application owns its HTTP or RPC framework, business tables, authorization policy, worker handlers, deployment, process signals, and telemetry export. Frontend frameworks, browser transports, client caches, WebSockets, SSE clients, and refetching are also application concerns. Forge ships no browser package.

Eight primitives, one connection

Key/valueGet, set, counters, compare-and-swap, prefix scan, TTLs. Lineage: Redis.

QueueBackground jobs with acks, retries, delays, dedup, and dead letters. Lineage: SQS.

Pub/subConnected-only backend fan-out with no retention or replay. Lineage: Postgres LISTEN/NOTIFY.

BlobPut, get, delete, and presigned upload and download URLs. Lineage: S3.

Authargon2 password hashing, sessions, and API keys. Lineage: OWASP and PHC.

Rate limitToken-bucket or sliding-window checks with IETF headers.

ScheduleRecurring cron jobs and one-off work at a future time.

Config and flagsRuntime settings and feature flags with percentage rollout.

Runtime boundary

One coordinated schema

PostgreSQL-backed primitives use one Forge-owned schema and bounded pools. A measured hot primitive can use a separate PostgreSQL target without changing the public contract.

One contract in four languages

Rust, JavaScript, Python, and Go are checked against one versioned contract and the same declarative conformance scenarios.

Explicit backend differences

Memory and PostgreSQL implement the same supported operations, while runtime capabilities report durability, process scope, notification, and blob differences.

Application-owned integration

Forge does not install a web server, signal handler, metrics exporter, MCP server, or frontend adapter. The host application owns those boundaries.

Minimal PostgreSQL setup

forge.toml

[postgres]
url = "${DATABASE_URL:-postgres://localhost/myapp}"

init() reads forge.toml and returns one client. Development may run Forge migrations during initialization. Production startup validates the schema by default; run migrations as a separate deployment step before serving traffic.

QuickstartInstall Forge and make your first calls in five minutes.

TutorialsBuild a to-do app, a URL shortener, and a chat app, step by step.

PrimitivesThe eight building blocks, with the methods that matter for each.

SemanticsDurability, ordering, retries, expiry, outages, and crash boundaries.