Platform
Isolation by construction, not by convention.
How OpenStake is put together: a small shared kernel, modules with their own contracts, and a separate set of databases for every operator.
Front end, CRM, data warehouse
Studios, payment providers, KYC, trading
Tenant registry · identity · access and four-eyes · configuration · audit · events · secrets
A database set per operator
No shared tables between operators. Every query is routed to the caller's own databases, and two-operator isolation tests run on every change.
Restore one operator, not everyone
Point-in-time recovery per operator, rehearsed as code with measured recovery targets.
Integer money
Amounts are integer minor units with a currency, everywhere. Journals must balance or they are refused.
Events per operator
Every event stream is separate per operator, so retention, replay and deletion follow your data.
Secrets never in data
Supplier credentials live in a dedicated secret store and are used by reference, never stored in a row or a log.
Audited by default
Staff actions are recorded with who, what and why. Sensitive ones need a second approver.