One open roadmap
Available, preview, and planned gateway, registry, policy, identity, audit, and deployment work stays public.
Open-source commitment
LiteMCP Composer is licensed under Apache 2.0. Current code and future security, identity, policy, audit, high-availability, and on-prem work are intended to mature in public—not behind closed feature gates.
Project covenant
These boundaries are part of the product definition and should be reviewable in source, tests, and release artifacts.
Available, preview, and planned gateway, registry, policy, identity, audit, and deployment work stays public.
Self-hosted operation never requires a cloud account, activation server, or call-home path.
Configuration export exists in preview; complete cross-target import and execution remains an acceptance gate.
SDKs and gateway fixtures are public; the connector and named-client compatibility matrix is planned.
The disclosure policy and limitations are public; signed releases, revocation feeds, and supported release lines remain planned.
The current slice has no telemetry exporter; any future self-hosted export must be opt-in and documented field by field.
Governance
The project is being established with a public roadmap, contribution process, security policy, release notes, and a maintainer path. Foundation governance can be evaluated after meaningful ecosystem participation exists.
Priorities, validation gates, and known limitations are visible.
Signed manifests, checksums, SBOMs, and rollback notes are release gates, not current artifacts.
Connector and core contributors retain visible attribution and a maintainer path.
Diagnostics do not require customer tool arguments or responses.
Portability is achieved only when a cloud-exported configuration executes on the self-hosted target without proprietary conversion; that live test is still pending.