Simezu integration
How to switch Soriku from local mode to Simezu-backed multi-tenant mode with SSO and billing.
Prerequisites
- A Simezu workspace (created at simezu.com)
- A Simezu app registration for Soriku, which gives you APP_ID, APP_API_KEY, APP_API_TOKEN
- Your Soriku instance reachable at a known base URL
Configure Soriku
SSO flow
User clicks Sign in on Soriku → redirected to Simezu → authenticates → redirected back with a token. Soriku exchanges the token for tenant context (org, role, plan). All subsequent API calls carry the bearer token and are scoped to that tenant.
Billing
Subscription state comes from Simezu via webhooks. Soriku reflects the plan in its rate limits and feature gates (e.g. Pro adds Soriku Cloud, Team adds shared agents). You don't need Stripe credentials on the Soriku side unless you want direct billing.
Tenant isolation
Every workspace has its own subset of agents, keystore, capability map, and routing logs. No cross-tenant leakage by design: queries always include a tenant filter at the database layer.