Skip to main content
Leamout’s public customer API is versioned under /v1. Within a version, clients should depend on documented public fields and behavior rather than internal packages, storage schemas, runtime identifiers, service topology, or carrier-provider implementation details. Self-hosted runtime releases are pinned artifacts. Production deployment compatibility is defined by the release bundle and supported-host contract rather than by running arbitrary development artifacts. Carrier-specific behavior stays behind provider integrations so the public communications model remains provider-neutral where practical.