Postgres backend platform
The backend road is already paved.
Postgres, auth, Redis, edge functions and email: provisioned per project, isolated by default, and reachable through one API you own.
Create your account
Sign in
PostgreSQL 16.15 · RLS-enforced isolation · 3ms p50 control plane · V8 isolates for functions · S3-compatible object storage
Six services, one boundary.
Auth: email and password sign-in, OAuth with your own credentials, server-managed sessions with instant revocation.
Database: a dedicated PostgreSQL 16 schema and role per project, journaled writes, readable DDL history.
Redis: namespaced cache, queues and rate limits; project keys never cross the fence.
Edge functions: sandboxed V8 execution with landlock and seccomp, per-project concurrency and egress allowlists.
Email: Amazon SES with DKIM signing, SPF, DMARC reporting, automatic bounce and complaint handling.
Secrets: per-project encrypted storage, never exposed to the client.
Every project in its own lane.
Own PostgreSQL schema and role, RLS enforced and forced on control tables. Own Redis namespace prefix, swept on project lifecycle. Server-side sessions, revocable from the dashboard at any time.
The actual limits.
Sign-up codes: 5 per hour per address, 10 per minute per IP, and a code expires after 10 minutes. Project email: 30 messages per day. Uploads: 50 MB per object. Edge functions: 90 seconds of runtime and a 2 MB request body. The control plane accepts 8 KB JSON bodies. Every one of these is enforced on the server, not by convention.
Where it runs.
One host, one region for your data, with PostgreSQL 16.15 and Redis 7.4.11. Transactional email goes out through Amazon SES with DKIM signing, SPF, DMARC reporting and a custom MAIL FROM, and bounces and complaints are handled automatically and suppressed per recipient.
Before you ask.
Sessions are server-managed and revocable at any time, and nothing sensitive is stored on the client. Each project gets its own PostgreSQL schema and role plus a Redis namespace prefix, and the server refuses to run against an unsealed database. Functions run in sandboxed V8 isolates under Linux landlock and seccomp with per-project egress allowlists. Access opens in stages, and early accounts get priority on limits and support.
Fenaura, fenaura.dev