Not another bolt-on feature layer. Not a legacy platform with a modern coat of paint. Enterprise loyalty infrastructure — built from first principles, for the buyers that existing platforms have quietly given up on.
The enterprise loyalty market is dominated by legacy platforms that were built for a different era of commerce. Monolithic architectures, REST-only reporting, mutable balance fields masquerading as ledgers, and GDPR compliance implemented as a checkbox rather than an engineering discipline.
VariaOS was started to fill a specific gap: enterprise buyers who need API-first, composable loyalty infrastructure that integrates cleanly into existing stacks, provides financial-grade auditability, and satisfies genuine GDPR obligations — without the overhead of a full-stack platform that competes with their own front-end team.
Every capability we advertise is an architectural commitment. "GDPR compliant" is not good enough — we document the DEK/KEK model, the cryptographic erasure path, and the CI gates that prevent PII from reaching the event bus.
We have not yet achieved SOC 2 Type II. We do not have a built-in gamification library. We do not have AI-powered personalisation. We say so openly, with a roadmap — rather than burying the gaps in small print.
We do not build front-end loyalty experiences. Your front-end team is better placed to do that than we are. We provide the infrastructure; you provide the experience. This division of labour is a feature, not a gap.
Designed and built VariaOS end to end — the append-only ledger, the governed DSL rules engine (ANTLR4 grammar + sandboxed evaluator), the GraphQL reporting layer, envelope encryption with cryptographic erasure, and the PII-free event bus. Decided on day one that the ledger would be append-only, and has been unreasonably strict about it ever since. Answers "why 50ms?" with approximately 3,000 words.
Evaluating enterprise loyalty platforms surfaced the same problems in all of them: mutable balance fields, REST-only reporting, and GDPR compliance treated as a tickbox. The gap was obvious — and unfilled.
The founding design decision: the ledger is append-only, and that is not up for debate. Everything since has been built around financial-grade integrity rather than bolted on afterwards.
The ledger engine, the DSL rules engine (ANTLR4 grammar + sandboxed evaluator), the GraphQL reporting layer, envelope encryption with cryptographic erasure, and the PII-free event bus — designed and built by one founder, tested rather than promised. "50ms or it doesn't ship" is an actual rule, not a slogan.
VariaOS is in private beta, opening to a small number of design partners. Independent and bootstrapped — no outside funding, no growth-at-all-costs pressure, just the product.
The near-term milestone: onboarding the first design partner in Q4 2026, then hardening toward SOC 2 Type II. Deliberate pace, honest roadmap.
VariaOS is self-funded and independently owned — no outside investors, no board deck steering the roadmap. Decisions are made on engineering merit and customer need, and the product ships when it is genuinely ready rather than when a quarter closes.
VariaOS is a one-person company today, so there are no open roles — just one founder and a long backlog. If that changes, openings will be posted here. In the meantime, design partners and serious collaborators are always welcome to get in touch.
The private beta is open to a small number of design partners — no lengthy procurement process required.