Self-host Soriku Cloud

Run the same managed setup that hosted Soriku Cloud uses, on your own infrastructure.

Why self-host the cloud variant

Local mode is fine for one developer. Team mode through Simezu Cloud is fine for most teams. Self-hosting the cloud variant makes sense when you want full data sovereignty, on-premise deployment, or a hybrid setup where some workloads run in your DMZ.

Requirements

A Linux host with Docker (or Kubernetes if you want HA).
A Postgres-compatible database for tenant data.
A Simezu app registration (for SSO).
A domain name with TLS termination.

Bring it up

git clone https://github.com/atypisch/soriku.git
cd soriku/deployments/self-hosted
cp .env.example .env
# fill in DATABASE_URL, SIMEZU_*, SORIKU_BASE_URL
docker compose -f docker-compose.cloud.yml up -d

Verify

curl -s https://soriku.your-domain/api/health | jq

For HA and zero-downtime updates, use the Kubernetes manifests in deployments/k8s/. They include rolling-update strategies and health probes tuned for Soriku's startup pattern.