---
title: Wance — The backend, already solved.
description: Multi-tenant Backend-as-a-Service for developers and startups. Auth,
  database, storage, functions and webhooks — automatic per-tenant isolation, no manual RLS.
canonical: https://wance.dev/
human_url: https://wance.dev/
markdown_url: https://wance.dev/index.md
updated: 2026-07-16
---

# Wance

**The backend, already solved. You just ship.**

Auth, database, storage, functions and webhooks. Postgres enforces tenant
isolation — you never write a line of RLS.

- Start free: https://app.wance.dev/register
- Sign in: https://app.wance.dev/login

## How it works

You create an organization and a project in the dashboard, then generate an API
key for that project. Every request you make with that key is automatically
scoped to your tenant — the isolation is a Postgres policy, not code you write.

Base URL: `https://api.wance.dev/v1`  *(to confirm)*
Auth: `X-API-Key: <your project API key>`

## Available today

### Database
Entities and records over HTTP. Postgres enforces tenant isolation with real RLS.
*Limits: document/entity model over JSON, with a read-only translated SQL layer.
No arbitrary SQL. No pgvector or embeddings.*

### Authentication
Sign-up and login for your app's users: password or one-time code (OTP). Includes
user management, quotas and lockout on failed attempts. Each project gets its own
isolated user base.
*Limits: password and OTP only. No magic links. No social login for your app's
end users.*

### Storage
Files on real S3, isolated per tenant. Buckets, direct upload or presigned URL,
download via presigned URL.
*Limits: "public file" means a presigned URL with an expiry — not a permanent
public CDN.*

### Functions
Node.js 20/22 and Python 3.12 on real AWS Lambda. Secrets, env vars and per-function
logs. Each tenant/project gets its own isolated IAM role.
*Limits: you upload the zip as-is — Wance does not transpile. Synchronous
invocation only; no automatic database triggers.*

### Webhooks
Register endpoints, subscribe to events, and Wance delivers them with
HMAC-SHA256 signing and retries with backoff. Rotate the secret, inspect
delivery history, replay failures, test from an event catalog.
*Limits: events are delivered at entity level, not per individual row.*

## Plans

Every plan includes all five services above. Limits are per project unless noted.
Requests beyond a plan's limits are rejected until you upgrade.

- **Free** — 500 MB database, 25,000 MAU, 1 GB storage, 1 project
- **Starter ($19/mo)** — 8 GB database, 75,000 MAU, 75 GB storage, 2 projects
- **Business ($89/mo)** — 25 GB database, 250,000 MAU, 250 GB storage, 10 projects
- **Growth ($299/mo)** — 100 GB database, 750,000 MAU, 1 TB storage, 30 projects
- **Enterprise** — custom

MAU = monthly active users. Signup creates a Free project; no card required until
you upgrade.

## On the way

### MCP / agent-native
The MCP engine is built: it generates agent tools straight from each service's
OpenAPI, over local (stdio) and remote (http) transports, covering database,
auth, storage, functions and tenancy. Today it runs locally with a personal
token. Remote OAuth access, broader service coverage, and the public agent
surface are on the way. **Not yet usable without manual setup.**

### CLI
`@wanceapp/cli` exists. The browser-based login flow is still in development.
**Do not assume `wance login` works today.**

### Payments · LLM gateway
Coming soon. Not available yet.

## Not sure? Ask.

If a capability is not listed under "Available today", assume it is not available.

---
Human version: https://wance.dev/
Markdown version: https://wance.dev/index.md