Sovereign Modular Architecture™

We wrote the Sovereign Modular Architecture standard. The reference implementation is open source. The judgment to apply it is what we sell.

Get the foundation on GitHubRead the standard

Trusted by teams at

The architecture

Three things that make Sovereign Software structurally different.

01

Sovereign Modular Architecture™

Every module is a first-class service.

Its own data model, its own API contract, its own lifecycle, its own Module AI Agent.

  • Modules know nothing about each other except through declared interfaces. No hidden coupling.
  • New customers, new features, and new tenants are configuration — not code.
  • When a module needs to change, you change that module. Nothing else moves.
02

4-Layer Permission Architecture™

Four layers that compose, not nest.

Not a permissions diagram — the rule that lets your platform grow. Every new capability becomes a module that plugs in.

  • Add almost any capability as a new module — projects, pricing, integrations, reporting — without rewriting what’s already there.
  • Granularity at three levels: module access, function access (view vs. edit), and data access.
  • Operators use the same architecture as customers, scoped by role. No backdoors.
  • Teams ship faster, with fewer bugs, because every module is first-class — and the platform expands into new applications without rebuilding what already works.
03

The sidecar approach

Your legacy platform stays live the entire time.

We deliver one sovereign module at a time, with traffic cut over on your timeline.

  • No migration weekend. No downtime. No big-bang replacement.
  • Every module is a discrete, reversible decision.
  • You are never committed to more than one module at a time.

The reference implementation

The architecture, working, on GitHub.

Sovereign Portal · Foundation release

A working sovereign foundation for owned software.

Users, Customers, Workspaces, and a Standard Module Interface for everything you build on top. Self-host, fork, extend. No license keys, no hosted SaaS, no lock-in.

Stack
Node · Express · React · MongoDB
License
Apache 2.0
Deploy
docker compose up
Get it on GitHubAdd a custom module on top

Two ways to use it

Replace a legacy monolith, or start a new build.

Replace a legacy monolith

Your platform stays live the entire time. We sidecar a sovereign module alongside the old system and cut traffic over on your timeline — one reversible decision at a time. No migration weekend.

Diagnose legacy software →

Start a new build

Start on the open-source foundation. Ship the first module designed and built right the first time, on an architecture that won’t rot — and add the next module when the business is ready.

Start a new build →

The framework is the marketing. The work is what we sell.

See pricing