Why one console for every project

Every product you operate needs roughly the same back-office: a place to edit content, manage members and roles, wire up billing, expose an AI surface, and answer support. Teams rebuild that admin, badly, on every single project.

The two-scope model

Svitrio is two scopes welded into one admin. The project scope is the per-tenant editorial work — pages, templates, translations, insights. The operator scope is the work of running it — dashboards over every tenant, roles, API keys, audit log, the plugin manager. Access is the membership: surfaces appear only when you are allowed in.

The result is that you learn one tool once, and it works the same across every product you run.