Incubating open infrastructure for accountability and sustainable development
We develop and spin out reference implementations of international standards—creating digital infrastructure that serves the public interest. Our tools are open source by default, interoperable by design, and mission-locked to reinvest margins into continuous improvement.
What We Do
sd17 builds the missing layer between policy ambition and practical measurement.
Global standards exist for climate action, biodiversity protection, and sustainable development. Trustworthy open implementations of those standards do not. We create reference implementations that demonstrate how these frameworks can work in practice, then spin them out as independent organizations when they reach maturity.
This is infrastructure for measuring what matters, built as a commons.
Our approach:
- Standards-based — We implement existing frameworks, not invent new ones
- Open by default — Apache 2.0 and MIT licensing for all code
- Non-extractive — Mission-locked structures that optimize for impact, not exits
- Designed to spin out — Mature implementations become independent organizations with their own governance
Current Focus
We're maturing our first reference implementations focused on full-chain provenance—systems that track how data about sustainability, verification, and accountability flows from source to decision.
These address critical gaps: organizations need to report on climate commitments, verify content authenticity, and track development outcomes, but lack trusted open tools to do so. We're building spatial data frameworks and content authentication systems that will spin out as independent organizations in 2025-2026.
Early implementations include tools for ocean and natural capital accounting aligned with UN System of Environmental-Economic Accounting (SEEA) standards, and content provenance systems implementing Coalition for Content Provenance and Authenticity (C2PA) protocols.
How We Work
Our Principles
Open source by default
All implementations are released under Apache 2.0 or MIT licenses. We build infrastructure that anyone can use, inspect, and improve.
Non-extractive by structure
sd17 and all spin-out organizations are mission-locked. We optimize for impact, not exits. Surplus is reinvested in the mission, never extracted by shareholders.
Standards-based
We don't invent new protocols where good ones exist. We demonstrate how international standards work in practice.
Interoperable by design
Our implementations connect rather than compete. Each tool strengthens the ecosystem.
Governed in common
We maintain governance relationships with spin-outs through board participation, ensuring shared values persist as organizations mature.
The Spin-Out Model
When our implementations reach maturity—validated market demand, operational team, stable technology—we spin them out as independent organizations. Each spin-out:
- Operates autonomously with its own board and leadership
- Maintains mission-locked governance (company limited by guarantee)
- Commits to open source licensing and interoperability
- Includes an sd17 board seat to preserve ecosystem alignment
- Reinvests margins into improving the open source implementation
This creates an ecosystem of organizations that can sustain themselves through earned revenue while remaining accountable to purpose rather than investors.
About
sd17 was founded by a team with expertise spanning systems transformation for climate action, natural capital accounting, international policy frameworks, and software development. Our work includes development and implementation of environmental-economic accounting standards (SEEA), ocean governance frameworks, and climate finance mechanisms across the Asia-Pacific region and globally.
We bring together capabilities in computer science, law, natural resources governance, and partnership building across government, business, and civil society.
sd17 takes its name from the 17 Sustainable Development Goals—a reminder that infrastructure for measuring progress toward global ambitions must itself be built as a common resource.
Get Involved
For Standards Bodies and Policy Organizations
If you're working on frameworks that need better implementation tooling, or governance challenges that need better data infrastructure, we'd like to hear from you. We partner with governments, international organizations, and research institutions to identify where open reference implementations can unlock adoption.
For Developers and Designers
Our implementations will be developed in the open. If you're interested in contributing to commons infrastructure for sustainability and governance, repository links and contribution guidelines will be published as projects reach public release.
For Mission-Aligned Funders
We're building a new model for creating digital public goods—one that combines the rigor of open source development with the sustainability of earned revenue. If you support digital commons infrastructure, non-extractive technology models, or implementation of the SDGs, we welcome the conversation.
Contact: hello@sd17.org
Newsletter: Coming soon
FAQ
What is a "reference implementation"?
A working demonstration that shows how a standard or framework can be implemented in practice. Our reference implementations prove feasibility, provide templates for others, and become production-ready tools that organizations can deploy.
Why "incubate" rather than just build?
We grow implementations to independence. Our goal is not to operate infrastructure indefinitely, but to create sustainable organizations that can serve their communities long-term. Incubation includes technical development, partnership building, operational planning, and governance design.
What does "mission-locked" mean?
Our legal structures (companies limited by guarantee) ensure that any surplus must be reinvested in the mission, not extracted by shareholders. The organization can never be sold for private gain. This aligns incentives with long-term impact rather than short-term exits.
How is this different from consulting?
We build reusable infrastructure, not bespoke solutions. Our implementations are designed to be maintained by communities and deployed widely. While we may provide implementation support, our goal is to reduce the need for expert intermediaries over time.
When will the first spin-outs launch?
Initial implementations are in active development and will enter public release in phases through 2025-2026. Join our newsletter for updates.
How can open source be sustainable without venture capital?
Our spin-outs generate revenue through managed hosting, implementation consulting, support contracts, and technical services—not through restrictive licenses or exits. This is infrastructure-as-a-service for the commons, following models proven by organizations like Red Hat, WordPress, and GitLab (before their exits).
What's the relationship between sd17 and its spin-outs?
sd17 appoints one director to each spin-out's board, maintains governance oversight, and provides ecosystem coordination. Spin-outs operate independently but commit to shared principles: open source licensing, non-extractive structures, interoperability, and contribution back to common infrastructure patterns.
Coming Soon
- First reference implementation public release
- Technical documentation and contribution guidelines
- Ecosystem partners and collaborators
- Spin-out announcements
Follow our progress: Newsletter signup coming soon