Christian Crank

Owner, Security Engineer

Network security engineer with deep roots in the MSP and MSSP world. Years of onboarding clients, building monitoring across fragmented platforms, and watching tools fail at the one thing they all need: real multi-tenancy.

The problem that started it all

If you have worked in managed security, you know the drill. An MSSP manages MSPs. MSPs manage clients. Clients sometimes have sub-clients. That is four levels of hierarchy, and almost no tooling handles it correctly.

The hierarchy Stratum models

MSSP
  MSP (Partner A)
    Client (Acme Corp)
      SubClient (Acme EU)
  MSP (Partner B)
    Client (Globex Inc)

Instead of one platform with proper tenant isolation, you end up running multiple instances of the same tool. One per MSP, sometimes one per client. Monitoring sprawls. Costs balloon. Things get lost between instances. You spend more time boxing tooling than actually building solutions for your clients.

Why Stratum

Stratum models tenants as a tree, up to 20 levels deep. The hierarchy above is not a diagram. It is a real data structure in Stratum. Config flows down the tree automatically. Isolation strategies apply per tenant. GDPR compliance is built in, not bolted on.

Node.js had no serious multi-tenancy library. The ecosystem gap was obvious to anyone building B2B SaaS or managed services tooling. Stratum fills that gap.

npm install @stratum-hq/lib pg

Read the docs GitHub