The Atypisch ecosystem
Soriku is one piece of a wider set of local-first tools built by the same team. Simezu handles sign-in and billing for the ecosystem, so one account works across every product.
The products
| Product | Role |
|---|---|
| Soriku | Local AI workspace: routing, agents, capability map, MCP |
| Simezu | Sign-in and billing for the ecosystem, multi-tenant identity |
| Wemazu | GitHub orchestration (wemazu.com) |
| Rozuro | Invoicing and CRM (rozuro.com) |
| Kimezu | A white-label Simezu on the same codebase, so anyone can start their own ecosystem (kimezu.com) |
| Modular CMS | Our own open-source CMS, used across the whole ecosystem and all our projects. Almost ready to ship (modularcms.org) |
More pieces of the puzzle are in the making and will be released later this year.
How Simezu fits in
When you run Soriku in local mode there is no auth and Simezu isn't involved. When you run Pro or Team plans, Soriku delegates sign-in and billing to Simezu. One account works across every product in the ecosystem. Teams share one workspace, one capability map and one bill.
Auth modes
| Mode | Set with | Use case |
|---|---|---|
local | SORIKU_AUTH_MODE=local (default) | Single user on a single machine. No login. |
simezu | SORIKU_AUTH_MODE=simezu | Multi-tenant with Simezu SSO. Teams, billing, tenant isolation. |
Data boundaries
Even in Simezu mode, agent memory and capability data stay scoped to the tenant. Soriku Cloud (when it lands) will store tenant data in EU-region infrastructure with workspace isolation enforced at every layer.