Architecture and preflight
Topology, threat model, capacity, ingress, identity, storage, vault, and observability review.
Enterprise on-prem · Planned services
The commercial model is accountability, not permission.
Future LiteMCP Composer engagements are intended to cover installation, integration, upgrades, reliability, security response, and support inside customer environments. No current SLA or production service commitment is asserted.
Engagement scope
A planned service scope around a public codebase.
A future contract can define deliverables, response commitments, environments, release lines, and ownership without creating a private product fork.
Installation and migration
Repeatable deployment, existing MCP inventory import, policy translation, and cutover support.
HA and recovery
Replica strategy, disruption budgets, backups, restore drills, rollback, and disaster-recovery exercises.
Identity integration
OIDC, SAML, SCIM, group mappings, service principals, and existing vault or KMS integration.
Supported operations
LTS planning, upgrade assistance, security patch response, diagnostics, and named escalation paths.
Restricted environments
Private registry mirroring, signed artifact transfer, offline installation, and air-gap runbooks.
Boundary
What a services contract does and does not buy.
| Open-source maturity | Potential contracted operations |
|---|---|
| Policy and audit available; SSO/SCIM wiring and approvals in preview | IdP implementation, mapping review, and lifecycle runbooks |
| Docker images and Helm renders in preview; live HA/recovery proof pending | Environment design, installation, validation, and recovery drills |
| Security fixes and public advisories | Defined response targets, supported patch windows, and escalation |
| Stable/LTS release mechanisms planned | Upgrade planning, compatibility assessment, and assisted rollback |
| Audit export in preview; OpenTelemetry and SIEM integrations planned | Integration with your SIEM, traces, metrics, and on-call process |
No enterprise service is represented as generally available here. Certifications, availability SLAs, support response times, named LTS dates, pricing, and contractual terms are not yet published.