MAKEMIND

Multi-tenant SaaS infrastructure

Run a multi-tenant SaaS without building the operations layer underneath.

Isolated tenants, a verified settlement ledger, subscribers, and identity — managed for you. You set the policy; MAKEMIND runs it.

Early access · dogfood stage

The shift

AI is making domain software cheap to build.

Consulting apps, ERPs, storefronts, device controllers — anyone can build them now, and it gets easier every month.

So the domain is the wrong thing to sell.

The asymmetry

But the operations layer under it is not.

Fast to build with AI

Your product

The domain you know — getting faster to build every month.

Slow, risky, a distraction

Tenancy, ledger, identity

Tenant isolation, a settlement ledger, metering, auth — regulated, easy to get subtly wrong, months before you earn a dollar.

Bring the product. We bring everything under it.

What we sell

Everything under a multi-tenant SaaS.

01

Multi-tenancy & isolationUnlimited tenants, each isolated — own users, roles, billing, config. Nest sub-tenants.

02

Settlement ledgerDouble-entry, hash-chained. Subscriptions, usage, points, deposits, commissions, tax.

03

Subscribers & identityDistinct-MAU metering, identity↔billing bridge, GDPR. Sessions, API keys, MFA, SSO.

04

And the rest, built inAI, knowledge / RAG, durable logic, marketplace, data & storage — one gateway.

You set policy; the platform runs it.

The structure

Isolated tenancy that nests.

Control plane

MAKEMIND

Tenants

Your customers

Sub-tenants (optional)

Their customers’ customers

End-users

Final consumers — distinct MAU

Every layer is isolated and sees only the one above it — own users, billing, and policy. You decide how money flows between them: route it through you, or stay out of the money path entirely. A setting, not a limit.

Two ways in

Take one service, or the whole stack.

Model A — Partial

Keep your backend.

Borrow the settlement ledger — or data, storage, messaging, AI — over an API key.

You build your own product
Auth — machine-to-machine key
Surface — REST + RPC, scoped by allowlist

Model B — Full platform

Build it all on us.

Tenants → app build → publish → custom-domain hosting, via the SDK.

You build your app on the platform
Auth — user sessions
Surface — the full SDK

Why teams build on it

The differences that decide it.

01

Multi-tenant management, done

Isolate and operate any number of tenants, sub-tenants, and end-users from one control plane.

02

A verified settlement ledger

Double-entry, hash-chained — the correctness you can’t get wrong with other people’s money.

03

Settlement on your terms

Entry fee, usage, subscription, points, deposit; your channel and money-flow — all configuration.

04

One service, or the whole stack

Take just the ledger over an API key, or build your whole app on the platform. No migration.

Where we are

Proving it on ourselves first.

Now

Dogfood

We run our own SaaS — the marketplace and others — on the platform and usage-test them.

Selected external tenants onboard with hands-on support.

Then

Public onboarding

Self-serve sign-up and published pricing.

Live card charging currently runs through one provider; additional providers and seller payout are being connected.

Not yet publicly open

Talk to us about early access.

Get early access

MAKEMIND — settlement & operations infrastructure for SaaS