Skip to content
singularity://database

Ship your product.
Skip the backend.

Most SaaS teams spend their first quarter building the backend nobody pays for: auth, permissions, sync, hosting, billing, metrics. The Singularity Database is that whole layer, delivered as one European service. You write the front end. You ship.

In early access · Built by the team behind iCloud · Made in Sweden, stored in the EU

  1. 1Declare the view
  2. 2Bind it to data
  3. 3Give Lars access
  4. 4Lars adds an app
Appsidentity: Emma
My Application Library
NameUpdated (UTC)
Appsidentity: Lars
My Application Library
NameUpdated (UTC)
Lars has no access to tenant://Applications yet

Eighteen lines of XML and two CLI commands. No fetch, no state, no sync code — the binding does it.

 KB
A complete, deployed, multi-user CRM — smaller than a typical lockfile. How it was measured
lines
of API code. The part you usually spend the most time on does not exist.
bill
what it means for you

Six things you stop building.

Launch in weeks, not quarters

The quarter of auth, sync and permission plumbing before the first feature? Gone. Bind your front end to data and you are done.

How one data model does it

Every app is collaborative and works offline

You never write sync code. Changes reach every client by themselves, and writes keep landing when the network drops.

How real-time and offline work

Your users' privacy is built in

No privacy layer to design, test or audit. Each user gets a private database the tenant cannot read.

How privacy by design works

Run the business from launch day

No analytics tool, billing plumbing or support desk to buy. MRR, subscriptions and tickets are in the console already.

What the console gives you

One bill you can predict

No metered reads, egress or per-request fees. A flat monthly price you can put in a forecast.

See the plans

European by construction

No "under whose law?" conversation to lose. EU-only storage, Swedish law, and keys that stay with your users.

How sovereignty works here
one service, one bill

Six vendors, six integrations, six invoices — or one.

You did not set out to run six services. A database, an auth provider, a sync engine, hosting, analytics and a support desk — or one service and one invoice. See the line items.

Databaseinvoice 1
Auth providerinvoice 2
Sync engineinvoice 3
Hosting + CIinvoice 4
SaaS metricsinvoice 5
Support deskinvoice 6
CloudBackendone flat invoice
  • Database, files and query
  • Identities, groups, roles, MFA
  • Real-time and offline cache
  • App hosting and deployment board
  • Subscriptions and live KPIs
  • Support tickets
who builds on it

You will recognise yourself in one of these.

SaaS teams

You have a product to ship and a backend in the way. Teams, roles, billing and metrics without wiring six services together.

Builders working with AI

Your AI builder just handed you a schema and a security-policy language. Here the whole app is a few kilobytes a model can hold in full.

CTOs with a sovereignty requirement

Procurement asked "under whose law?" and "EU region" was not the answer. Swedish company, EU-only storage, Swedish law.

eu://sovereignty

Your data stays in Europe. Only your users hold the key.

An EU region tells a buyer where the disks are — not whose court can order the data out. Here the answer is Swedish law, EU-only storage, and client-side encryption that leaves us nothing to hand over. That works for European teams and for US services with European customers.

Your user's device
encrypts before sending
Singularity Database
EU storage · Swedish law
company://linköping

Built by the team behind iCloud.

Founded in 2018 in Linköping, Sweden, by Daniel Arthursson — previously founder of iCloud, CloudMe, XIOS/3 and Xcerion. The console itself runs on the Singularity Database.

The CloudBackend console: Applications launcher, XMLPad editor with a Kanban app open, and the icon browser

Early access means direct access to the engineers who built it.