Lumis SDK and Lumis
Understand the open-source framework boundary and the planned managed Lumis platform from Qadim Labs.
Two complementary layers
| Lumis SDK | Lumis |
|---|---|
| Apache-2.0 Python framework | Planned managed hosted platform — coming soon |
| Local and self-hosted workflows | Multi-tenant team workflows |
| Project-owned adapters and policies | Managed connector fleet and approvals |
| Local inspectable memory | Hosted multi-user memory and audit |
| Community support and extension | Enterprise RBAC, SSO, runners, deployment, and support |
Independence rule
Lumis SDK must remain useful without a Lumis key. It must not make remote calls by default, hide essential local capability, emit telemetry without opt-in, include proprietary product code, or require a commercial database or model provider. These commitments are part of the project's governance, not marketing.
Open-core contribution flow
Generally useful primitives are proposed and implemented publicly, released from Lumis SDK, and then consumed by Lumis—the same way any other application consumes the framework. Product-specific UI, hosting, multi-tenancy, billing, and enterprise operations remain in the managed product.