This site is currently under construction — things may change or break.

A database, served over REST.

Stop provisioning databases. LeopardDB gives every one of your users or customers an isolated, self-service database behind a single HTTP API — with EU data residency and Auth0 identity built in from the first request.

Request a demoSee the API
Hosted in the EU GDPR by design Auth0 identity PostgreSQL Auto-scaling infrastructure
Your data never leaves the EU.

LeopardDB runs on EU-based auto-scaling infrastructure, full stop. No transatlantic transfers to explain to your DPO, no Standard Contractual Clauses to paper over, no region toggle you have to remember to set. If GDPR is a hard requirement — and for most European teams it now is — this is the shortest path to a compliant backend.

One API, one database per tenant.

Every user or Auth0 organisation gets an isolated namespace inside a shared PostgreSQL instance. No provisioning scripts, no per-customer instance sprawl, no cross-tenant leak waiting to happen. You send products; you get back products. LeopardDB handles the isolation underneath.

Identity you already trust.

No user table. No stored passwords. No tokens of our own. Authentication and role-based access control run entirely on Auth0, with every request validated against your tenant — signature, audience, expiry, permissions, and a live check that the user hasn't been blocked or removed from their organisation.

From nothing to a working backend, in three calls.

That's the entire onboarding. No migrations, no ORM, no DBA.

# 1. Create a database
curl -X POST https://api.leoparddb.com/v1/database \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"name":"mydb"}'

# 2. Create a table
curl -X POST https://api.leoparddb.com/v1/schema/table \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"tableName":"products","databaseName":"mydb",
     "columns":[{"name":"title","type":"text","nullable":false},
                {"name":"price","type":"numeric","nullable":true},
                {"name":"image","type":"bytea","nullable":true}]}'

# 3. Insert a record
curl -X POST "https://api.leoparddb.com/v1/data/table?table=products&database=mydb" \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"records":[{"title":"Widget","price":9.99}]}'
Schema that keeps up with your product.

Add a column on Tuesday, rename it on Thursday, drop it when the feature dies. All from JSON, all live, all over the same API. Every table gets a UUID primary key for free.

Files are first-class.

Upload and download binaries straight into bytea columns. Record listings never inline your bytes — they report HasValue or Empty — so a query stays fast and a download stays a download.

Built on proven components.

PostgreSQL for storage. Auth0 for identity. A mature, production-grade Pascal stack for the server itself. Nothing here is a science project.

Self-hosting available.

Need LeopardDB inside your own walls? It runs as a Windows service, a Linux daemon, or a Docker container against your own PostgreSQL — under a custom licence. Contact us for a quote.

Built for teams who have to answer to an auditor.

LeopardDB exists because European software teams keep solving the same problem twice: build the product, then retrofit the compliance story. GDPR isn't optional, and for a growing number of buyers, neither is a serious information-security posture. So we built the backend the other way round — compliance first, features on top.

Send us your security questionnaire
  • EU data residency. Your data is stored and processed on EU-based infrastructure. There is no non-EU region, because there is no non-EU option.
  • Auto-scaling by default. LeopardDB runs on EU-based auto-scaling infrastructure, growing with your load rather than your forecast.
  • No credentials at rest. LeopardDB stores no passwords and issues no tokens. Identity is Auth0's job, and Auth0 does it well.
  • Tenant isolation by construction. Namespacing is applied at the storage layer on every request, not bolted on in application code.
  • Defence in depth. Rate limiting before the request body is read. JWT validation on every call. A live check that revoked users stay revoked.
  • Information security. Our security practices are aligned to the ISO 27001 framework.

Priced per user, per month. No setup fee. Cancel whenever.

Start free. Add seats as your team or your customer base grows. Every plan runs on the same EU infrastructure with the same isolation guarantees.

FreeProfessionalEnterpriseCustom
Price€0€35 / user / DB / mo€65 / user / DB / moQuote
Users includedup to 5up to 50up to 100Your call
Databases1up to 10up to 25Your call
Tables1050100Your call
Fields per table1025100Your call
Records per table1,000100,0001,000,000Your call
EU data residency
Auth0 identity & RBAC
Blob storage
Client libraries
Self-hosting———
SupportCommunityEmailPriority emailNamed contact
Start freeRequest a demoRequest a demoGet a quote

Prices are per user, per month, excluding VAT. Tier limits are generous by design — if you're approaching a ceiling, talk to us before you hit it rather than after.

Docs & resources

Want the full docs before you commit? Ask us: info@owlhatsoftware.com

Request documentation
Postman collection

Every endpoint, ready to run. The fastest way to see the API for yourself.

Client libraries

Source on GitHub, binaries for Windows x64 and Linux x64.

User Manual & Docs

Available on request. Email us and we'll send them over.

Frequently Asked Questions

No. LeopardDB is hosted — you need a token, nothing else. If you'd rather run it yourself, that's available under a custom quote.
Per user, per month. Free covers up to 5 users at no cost; Professional is €35 per user per month, Enterprise €65. Self-hosting is quoted separately.
On EU-based infrastructure. There is no non-EU region.
In Auth0. LeopardDB has no user table, stores no passwords, and issues no tokens of its own.
Every database and table is stored under a prefix derived from the caller's Auth0 identity. The API only ever accepts and returns unprefixed names.
By design — binary columns are never inlined in record responses. Fetch the bytes from the blob endpoint.
The user-active check is cached for about a minute. Wait out the window, or ask us to lower the cache TTL.
Talk to us and we'll move you up. Limits are policy today rather than a hard stop in the engine, so you won't hit a wall mid-transaction — but we do expect plans to reflect actual usage.
Yes, under a custom licence. Windows service, Linux daemon or Docker, against your own PostgreSQL. Contact us for a quote.
The client libraries are. The server is a commercial product.

See it against your use case.

Fifteen minutes, your requirements, a live API. If LeopardDB isn't the right fit we'll say so — a bad-fit customer is worse for us than no customer.

info@owlhatsoftware.com

Request a demo