Inari Documentation¶
Inari is 7KGroup's Platform Team as a Service (PTaaS). Every client gets a dedicated Internal Developer Platform — Backstage, Crossplane, ArgoCD, Dex, and full observability — deployed in their own cloud account and operated by 7KGroup from a central management plane.
A working platform team in 2–4 weeks, on a monthly retainer, for less than one platform hire. No lock-in: the stack is open source, your cloud account stays yours, and every engagement has a documented handover story.
:octicons-arrow-right-24: Talk to us at 7kgroup.org{ .md-button }
What lives here¶
| Section | Contents |
|---|---|
| Architecture | How Inari is built: the fleet model, per-client control planes, secrets, observability, onboarding, and pilot scope. Start with the Introduction and read in order. |
| Decisions (ADRs) | The Architecture Decision Records behind the design — why cluster-per-client, why CNOE as a baseline, why client-local ArgoCD, the mTLS CA strategy, and more. |
| Runbooks | How we operate: client onboarding, overlay management, access provisioning, certificate rotation, disaster recovery. |
Why we publish this¶
Engineering buyers trust what they can read. Our architecture, our decisions, and our operational runbooks are public because they're the strongest evidence of how we work — and because our clients keep the keys. If you're evaluating Inari, your engineers should start here.
Related¶
- 7KGroup — company site
- Inari product page — the commercial offering
- github.com/7K-Group — open-source stacks (Hiroba catalog, Minato, workflows)