Postgres for agents — fr-par-1
MCP PyPI GitHub

One database per agent, opened in under a second, in France.

Your agents create, query and destroy their own databases through the API or the MCP server. Each one works on an isolated branch of your real data — no copy, no human in the loop, nothing leaving the country.

Create a project Connect an agent

No credit card — PostgreSQL 17.4 — pgvector, MCP server, CLI

100%

Of your agents' databases hosted in France: compute, storage, WAL and backups.

Scaleway fr-par-1 — Vitry-sur-Seine

99.991%
Measured average availability of the services
DB & PageServer, DB Proxy, K8S, console
< 1 s
To create a branch for an agent
copy-on-write, no data copied
51
MCP tools for your agents
plus a CLI and a REST API
€0
Of compute billed while an agent's database is idle
suspends after 5 min without queries
operational Measured on Oct 19, 2026 — status page
§ 01 — ONE AGENT, ONE DATABASE

An agent that breaks a database only breaks its own.

Each agent gets a copy-on-write branch of production: the same data, readable immediately, with no duplication. It migrates, writes, gets it wrong, then deletes. Production never noticed.

mainproduction — 8 GB — human and CI writes only
agent-7f3a — cohort analysisread-only — 1,240 queries — destroyed after 4 min
agent-9c21 — schema reworkwrite — 6.8 MB delta — rollback requested by the agent
Per-branch fee: noneDuplication: noneDestruction: immediate, by the agentCompute billed: active time only
active
susp.
susp.
active
active
susp.
susp.
susp.
susp.
active
susp.
susp.
active
active
susp.
susp.
susp.
susp.
susp.
active
susp.
susp.
active
susp.
susp.
susp.
susp.
active
susp.
susp.
susp.
active
susp.
susp.
active
susp.
susp.
susp.
susp.
susp.
active
susp.
susp.
susp.
active
susp.
susp.
susp.

48 databases in a single project — 13 active, the rest suspended, with no compute billed.

§ 02 — GUARDRAILS

An agent is a user you don't take at its word.

Each branch carries its own privileges, masked columns and log. You can read back what the agent ran, what it was refused, and what it saw in clear text.

audit log — agent-7f3a — branch agent-7f3a1,240 queries, 3 refusals
09:14:02 SELECT cohort, count(*) FROM subscriptions GROUP BY 1 allowed
09:14:09 SELECT email, iban FROM customers LIMIT 50 masked — 2 columns
09:14:22 UPDATE invoices SET status = 'paid' WHERE id = 8814 refused — read-only
09:17:48 COPY (SELECT * FROM customers) TO PROGRAM 'curl …' refused — exfiltration
09:18:03 DROP DATABASE agent-7f3a allowed — its own branch

Exportable log, 90-day retention, webhook on every refusal.

DATA RESIDENCY
PROJECT my-app — AUGUST 4, 2026
DOCUMENT GENERATED BY THE API
§ 03 — SOVEREIGNTY

What your agent reads does not leave France.

An agent multiplies the places your data passes through: vector memory, traces, tool logs. At Lampion each of those layers has an address and an attestation, queryable through the API and exportable for an audit.

Layer Operator Site Host attestation
compute (agent branches) Scaleway fr-par-1 — Vitry-sur-Seine (DC2) ISO/IEC 27001 · HDS
storage (pageserver) Scaleway fr-par-1 — Vitry-sur-Seine (DC2) ISO/IEC 27001 · HDS
vector indexes (pgvector) Scaleway fr-par-1 — same cluster ISO/IEC 27001 · HDS
audit trail (console database) Scaleway fr-par-1 — Vitry-sur-Seine (DC2) control-plane actions — project, branch, member, API key
backups (Object Storage) Scaleway fr-par-1 — Vitry-sur-Seine ISO/IEC 27001 · HDS
control plane Lampion (EI) Paris, France SIREN 947 709 275 — not HDS certified yet
GET /v1/projects/{id}/residency — versioned, timestamped, exportable as PDF. Scaleway (host) certifications: ISO/IEC 27001 and HDS. Lampion itself is not HDS certified yet: the host certification does not cover Lampion operating your databases. None of your database data leaves France, no transfer to a model provider.
create_branchexecute_sqlget_schemamerge_branchadd_masking_ruleenable_anonymizationrestore_backupget_slow_queriesset_allowlistgrant_permissionget_residencyget_security_questionnaireget_dpa_statuslist_subprocessors
§ 04 — CONNECT AN AGENT

Fifty-one tools, one configuration file.

The MCP server exposes projects, branches, SQL execution, PII masking, backups, observability and compliance (security questionnaire, DPA, subprocessors, data residency). Nothing to host: it runs against your project, with an API key that carries its own role.

~/.config/mcp/servers.jsonMCP server
{
  "lampion": {
    "command": "lampion-mcp",
    "env": {
      "LAMPION_TOKEN": "lmp_live_…",
      "LAMPION_API_URL": "https://api.lampion.cloud"
    }
  }
}
# the API key carries the agent's role (e.g. analyst),
# masked columns are never read in clear text

Without MCP: POST api.lampion.cloud/v1/projects/{id}/branches — API reference

app.lampion.cloud / my-app / agentsscreenshot
Lampion console — project branches view

The console as it stands today.

§ 05 — THE REST

What Lampion does, without the staging.

The complete list is in the documentation. This one is here to be skimmed.

Agent branches
Self-destructing TTL configurable in hours, branches protected from deletion, per-plan branch quota.
Scale to zero
Suspends after five minutes, wakes on connection, billed on active time.
pgvector
Memory and RAG in the same database as your business data, HNSW and IVFFlat.
Masking
Columns anonymised when the branch is created, never read in clear text by the agent.
Audit log
Per-organization log, kept for 12 months: projects, branches, API keys, members, roles, anonymization and full exports.
PITR
Restore to the second or to the LSN, into a new branch.
Access
SCRAM-SHA-256, IP allowlists, per-organization RBAC (owner, admin, developer, viewer, analyst), OIDC SSO.
Pooling
PgBouncer in transaction mode, up to 200 client connections multiplexed per endpoint.
Encryption
TLS required in transit (1.2 minimum on the proxy, 1.3 negotiated). Encryption at rest being rolled out, available in Q1 2027.
Extensions
PostGIS, TimescaleDB, pg_cron, pg_stat_statements, and 60 more.
Migration
From RDS, Supabase, Neon or a dump, into a dedicated branch; you keep control of the cutover.
Automation
REST API, CLI, MCP server.

Full documentation

§ 06 — PRICING

Usage-based billing.

You pay for active compute and the storage actually used. A suspended agent database uses no compute, and no branch is billed as such. The line-by-line comparison is on the pricing page.

Free€0
Three projects, 512 MB, 0.25 CU, 3 branches per project.
Get started
Startup€29 / month
Compute €0.10/CU-h, up to 8 CU, unlimited branches, SSO, IP allowlists, 99.9% SLA, email support.
Get started
Souveraincustom quote
Dedicated isolation, CMEK, 99.95% SLA with penalties, HDS-certified host, dedicated on-call, payment by transfer.
Contact us

The MCP server is included on every plan, Free included.

Storage €0.40 per GB per month — plan comparison

Give your agent
a database.

Create a project No credit card — MCP server included — immediate destruction