Engineering wants to slow down and fix stability issues. Product wants to ship faster and hit deadlines. Who’s right? Both - and neither. The real question isn’t “should we prioritize reliability or velocity?” but “how much unreliability can we tolerate while still meeting our promises?” That’s your error budget: the quantitative answer that turns endless debates into data-driven decisions. With a 99.9% SLO, you get 43.2 minutes of downtime per month to spend on innovation, experiments, or controlled risks.

We welcome contributions! This project is open source under the Apache 2.0 license.

To contribute:

• Fork the repository at GitHub
• Read our Contributing Guidelines
• Create a feature branch
• Make your changes and write tests if applicable
• Submit a pull request

We appreciate all contributions, whether they’re bug fixes, new features, documentation improvements, or examples!

We use GitHub Issues to track bugs and feature requests.

To report a bug or request a feature:

• Visit our Issues page
• Search existing issues to avoid duplicates
• Click “New Issue” and provide detailed information
• For bugs: include steps to reproduce, expected vs actual behavior
• For features: describe the use case and desired functionality

Your feedback helps us improve the tool for everyone!

You can reach Cardinality Cloud through multiple channels:

• Email: jjneely@cardinality.cloud
• Website: cardinality.cloud
• For general feedback about this tool, use the feedback email above

We’d love to hear your thoughts on how we can improve this tool!