Enterprise Deployment Models

3Deployment ModelsSaaS · On-Premises · Hybrid Cloud

2-4 weeksOn-Premises Startup

99.95%Enterprise AvailabilitySaaS Enterprise

SM4-GCMSM Cryptography

Model Comparison

Deployment Model Matrix

One product, three deployment models — choose by data sovereignty and startup timeline.

Capability	SaaS	On-Premises	Hybrid Cloud
Lurus API Gateway	✅ Out of the box	✅ Private image	✅
Kova Execution Engine	✅	✅	✅
MemX Memory Engine	✅	✅	✅
Lucrum Quant	✅	🔜 2026 H2	✅
Switch / Creator	✅ Desktop	✅ Desktop	✅
Identity & Compliance	✅	✅	✅
Data Sovereignty	AWS / Alibaba Cloud	Enterprise internal	Hybrid
SM Cryptography SM4-GCM	—	✅	✅
Startup Timeline	Immediate	2-4 weeks	1-2 weeks

Compliance

Data sovereignty, audit trails, SM cryptography — a clear picture for your reviewers at a glance.

Data Stays In-Country

With on-premises deployment, no data passes through the Lurus public cloud.

Audit Logs

All API calls, identity events, and administrative operations are persisted to disk.

SM Cryptography Support

Symmetric encryption with SM4-GCM, asymmetric SM2 (on the roadmap).

MLPS / Industry Certifications

Please contact business@lurus.cn for the latest list.

Identity Federation

Employees sign in to every Lurus product with their company account — no new identities required.

Employees use their existing enterprise IdP (Okta / Azure AD / self-hosted Keycloak) to sign in with their company account:

Enterprise IdP Federated Login

graph LR; A[Enterprise IdP] -->|OIDC| B[Lurus Casdoor]; B --> C[All Lurus Products]

Supported protocols: OIDC / OAuth 2.0 / SAML 2.0 / SCIM (user lifecycle).

Service Level