Implementations
Multiple implementations validate the category and strengthen the movement.
What Makes an Implementation
AI Sovereignty 2.0 means controlling where your AI thinks.
To be listed here, implementations must embody:
- Self-hosted pipes, outsourced brain → You solve the brain part (reasoning happens locally)
- Shows its work → Transparent reasoning, auditable decisions
- Designed for thinking → Architecture built for complex decisions, not retrofitted
- Open principles → Shared standards, not proprietary lock-in
Hurozo (Reference Implementation)
Status: Production, Commercial Platform
Location: Amsterdam, Netherlands
Founded: 2024
Hurozo is the founding company and reference implementation of these principles. Production-grade private reasoning infrastructure built from the ground up for AI Sovereignty 2.0.
What Hurozo provides:
- Sovereign: Reasoning happens locally, no external API calls
- Capable: Handles complex multi-step coordination and decisions
- Transparent: Full reasoning logs, auditable decision paths
Hurozo acts as founding steward of the movement, with governance transitioning to the community at 10 implementations.
Becoming an Implementation
We welcome additional implementations—commercial, open source, consulting-led, or any model that embodies the four principles.
Criteria for Listing
Technical:
- Reasoning happens locally (not via external APIs)
- Shows its work (transparent, auditable decisions)
- Designed for thinking (not AI glued onto workflows)
Community:
- Acknowledge these are shared principles, not proprietary
- Commit to participating in open governance
- Welcome collaboration with other implementations
Maturity:
- Deployed in production OR clear production roadmap
- Can demonstrate the four principles in practice
Submit Your Implementation
Building private reasoning infrastructure based on these principles?
To be listed:
- Deploy in production (or have credible production roadmap)
- Document how you embody the four principles
- Commit to open governance participation
- Submit via (form coming soon)
Benefits of listing:
- Recognition as early implementer
- Input on principle evolution
- Seat on governance council (at 10 implementations)
- Visibility in the movement
- Connection to community
Governance Transition
When we reach 10 independent implementations, governance transitions from Hurozo to a community council.
Council Structure
Representatives: One from each implementation
Election: By community vote
Rotation: Staggered terms to maintain continuity
Process: RFC-style open proposals
Why 10 Implementations?
Enough to be credible (not just Hurozo)
Small enough to move fast
Validates reasoning sovereignty as a real category
For Consultants & Integrators
Building solutions for clients based on these principles? You’re part of the movement too.
We welcome:
- Consulting firms implementing for clients
- System integrators building on these principles
- Freelance developers deploying sovereign infrastructure
List your practice here by submitting via the form above.
Implementation Gallery
Founding Implementation
Hurozo - Production, Commercial Platform
Private reasoning infrastructure for enterprises
Coming Soon
(Space for additional implementations as they launch)
Building an implementation? Submit here →
The Evolution
AI Sovereignty 1.0: Running local models
AI Sovereignty 2.0: Controlling where reasoning happens
Current implementations solve 2.0. That’s what belongs here.
Technical Resources
For implementers:
- Four principles - Foundation to build on
- Manifesto - Complete vision and architecture thinking
- Community - Connect with other builders
Questions about:
- Architecture approaches?
- How to embody the principles?
- Governance participation?
Join the community or reach out: hello@reasoning-sovereignty.org
Why Multiple Implementations Matter
Validates the category - One company = product. Many = movement.
Strengthens principles - Multiple approaches improve the standards.
Prevents capture - No single vendor can own this.
Accelerates adoption - Choice drives market growth.
The movement grows through multiple implementations.