Frontend-first backend
The easiest backend for
frontend developers
testers,
and teams.
Projects bundle collections, app users, logs, and automations — all callable with fetch(), cURL, Postman, or any HTTP client.
Designed
Designed for modern frontend teams
Calm visuals that mirror how projects, speed, and flows feel in production.
Collections, app users, logs, automations in one place.
Latency-friendly defaults for every request.
Auth → session → records, end to end.
No servers.
No databases.
No DevOps.
Just HTTP:
fetch(),
cURL,
Postman.
Pillars
A real backend your frontend can own.
Projects, collections, app users, and logs live together so frontends stay production-ready without backend tickets.
Projects
Isolated environments with keys, limits, and observability.
Collections
Schema-backed JSON with CRUD you call directly from the UI.
App Users
Magic links issue session tokens scoped to each user.
Logs & automations
Every request is logged; triggers and webhooks fire on events.
Chapter 1
Projects bundle everything
One project holds collections, app users, and automations with clear prod/dev environments. Scoped keys; searchable logs.
Chapter 2
Collections are your JSON database
Define schemas, write with fetch(), and read per user or admin. Pagination and search are built in.
Chapter 3
App Users: real auth without backend
Magic links create app users; verification returns session tokens you use to scope data.
Chapter 4
Logs & automations: debug and react
Every request is logged. Fire webhooks on record events to keep QA and production in sync.
todos, orders, sessions
magic links enabled
search & export
record.created webhooks
{ "title": "string", "completed": "boolean", "priority": "number", "app_user_id": "uuid (optional)" }
POST /api/app-users/login POST /api/app-users/verify Authorization: Bearer <session_token> GET /app/collections/todos/records
Flow
The project lifecycle
Six quick steps from zero to production-grade data and auth.
Create project
Namespace keys, collections, logs.
Add collection
Define your JSON data model.
Invite user
Magic link creates an app user.
Verify token
Mint a session token.
Read & write
Scoped CRUD via Bearer token.
Observe & react
Logs + webhooks on events.
Code realism
Works from any HTTP client
Use fetch(), cURL, Postman, or any HTTP client for apps, QA, or lessons.
Browser · Node · cURL · Postman · HTTPie · mobile · desktop
Flows
Switch between authentication, CRUD, and pagination.
Scope data with Authorization: Bearer <session_token>.
Use cases
Made for modern frontend teams
Client-only apps, QA suites, and demos stay production-ready with the same project.
Client-only SaaS
Client-onlyFrontends call collections and auth directly; no servers to run.
Ship faster with scoped tokens.
QA & automation
QAPredictable data, logs, and webhooks for Playwright or Cypress.
Assert against real responses.
Demos & MVPs
DemoPresent working software with persistent data and logs.
Credibility without backend lift.
Education
TeachTeach HTTP, auth, and pagination without local setup friction.
Why: focus on concepts, not tooling.
Foundations
Built on strong foundations
Edge delivery, persistence, and observability by default.
Cloudflare edge
- Fast, global delivery
- Managed TLS
Persistence
- Postgres-backed data
- Logs + retention
Security
- HTTPS + CORS
- Rate limits + status page
Pricing
Start free. Scale when you're ready.
Upgrade limits without rebuilding your projects.
Start
Build your backend from the frontend.
Collections, app users, logs, and automations - ready for production teams.