Replacing marketing ambiguity with a verifiable, engineering-first standard for building truly cloud-agnostic systems.
The multi-cloud paradigm promised flexibility but often delivered operational chaos and a new, insidious form of vendor lock-in. Most "multi-cloud" strategies fail to deliver true portability, resulting in higher operational complexity and a disguised form of vendor lock-in.
The Open Omni-Cloud initiative was created to fix this. Our mission is to build an ecosystem where cloud systems can be verified, tested, and trusted across providers. We believe in Contracts Over Abstractions: a verifiable, testable contract is what defines a standard, not lowest-common-denominator abstractions. We are building the open standard for the next generation of cloud architecture.
A contract is only as good as its enforcement. The core of our work is the Technology Compatibility Kit (TCK), a pytest-based test suite that validates and certifies that a provider implementation adheres to the strict behavioral contracts of the Open Omni-Cloud standard.
A provider that successfully passes the TCK is guaranteed to be a certified drop-in replacement, enabling true portability and resilience by design.
Our standard is built upon six specific, verifiable criteria:
- Agnostic Providers: Interact with external dependencies through unified interfaces with consistent semantics.
- A Technology Compatibility Kit (TCK): A suite of automated tests that validates any provider implementation against the defined contract.
- Swap by Configuration: Switching between compliant providers must require only configuration changes, with zero refactoring of business code.
- Cross-Cloud Failover Targets: Demonstrated failover capabilities with pre-defined, aggressive, and tested recovery targets.
- Standardized Observability: First-class OpenTelemetry (traces, metrics, logs) and "Golden Signals" dashboards by default.
- Portable Policies & Compliance: Policies for data residency, encryption, and auditing must live inside the abstraction layer and travel with the workload.
Our primary focus is the development and maintenance of the TCKs that enforce the standard.
- tck-py: The official Technology Compatibility Kit (TCK) for Python implementations of the Open Omni-Cloud standard. It provides an executable contract for everything from primitives and messaging to resilience and observability patterns.
This is a community-driven initiative, and we invite engineers, providers, and organizations to join us in shaping a truly Omni-Cloud future.
| Contribute Code | Sponsor the Initiative | Join the Discussion |
|---|---|---|
| We are actively looking for contributors to help shape the future of cloud-agnostic computing. From fixing a typo to implementing a new contract, every contribution is valuable. See our Contribution Guide to get started. | Our work is funded by the community. Your financial support helps us cover infrastructure costs and allows our core maintainers to dedicate more time to the project. Become a sponsor through our [TBD] | For questions, open ideas, or general discussions about the standard and its future, please join us on GitHub Discussions. |
This project and all associated repositories are licensed under the Apache 2.0 License.