Keep shared data
connected.
Commons helps organizations collect data under shared rules, publish from existing systems and subscribe to local copies they control. Published updates and verifiable history let the same data support more programs, partners, and applications.
For publishers, programs, and teams that build on shared data.
| Key | Status | Updated |
|---|---|---|
| record/118 | withdrawn | v42 · 09:14 |
| record/204 | active | v41 |
| record/311 | active | v40 |
| files/guide.pdf | file | v40 |
| record/402 | pending | v38 |
Teams keep rebuilding the same data workflows.
A program gathers submissions from several organizations or applications. A publisher shares the same data with different networks. Other teams check, combine, and prepare it for reports, data lakes, applications, and AI.
Each team ends up maintaining its own process. A correction triggers another round of uploads, checks, and refresh jobs, while some copies fall behind. Work that could be reused gets repeated.
Contributions that don’t line up
Contributors use different tools and formats. Submissions often need manual checks, and corrections mean repeated follow-up.
Separate uploads for every network
Publishers maintain separate uploads and feeds for different programs or networks. Each correction has to be carried through those separate delivery processes.
The same cleanup, again
Different teams standardize the same fields, remove the same duplicates, and reconcile the same corrections before they can use the data.
Earlier versions are hard to trace
A record changes or a document is replaced. Finding the version used in an earlier report or decision means searching through old exports and logs.
Maintain one publication.
Serve many ecosystems.
Publish an agreed dataset from the systems you already use. Authorized organizations across programs and networks subscribe to their own local copies and receive its published changes.
Serve authorized subscribers across several programs and networks, with fewer duplicate uploads, separately maintained distributions, and repeated corrections.
You maintain the publication. Subscribers run queries against their local copies, so the publisher’s infrastructure does not have to serve every read.
Shared collection rules.
Different tools and formats.
Define what contributors need to provide and how submissions should be checked. A collection capability applies those requirements to connected entries, files, and feeds.
Participating teams can keep their own tools and formats while contributing to an agreed model.
Explore capabilities →Make the next program
easier to connect.
Reuse a collection capability, build on a maintained source connection, or subscribe to data another team has already prepared. Teams can adapt that work to their requirements and publish useful results for others.
Use the publication a maintained connection feeds, or adapt the connection for a related requirement.
Reuse or adapt a collection model and its validation behavior.
Use data another team has cleaned, combined, or enriched, rather than preparing it again.
Build on an established approach to onboarding, permissions, updates, and maintenance.
As more organizations participate, there is more established work to build on.
Coming soon Beckn and DeDi capabilities: shared data models and protocol interfaces for open networks.
Give applications the current record and the history behind it.
The same local dataset can support reporting, data lakes, operational tools, and AI. Applications can use received updates to refresh their inputs and record the versions behind their results.
Retained history lets teams compare changes and return to the information used in an earlier report, answer, or decision. MCP tools let compatible assistants list, read, and search datasets.
Commons shows who published a version and that it hasn’t been altered. Applications and organizations interpret the information and decide what to do.
See how AI builds on it →Run Commons
where the work happens.
Run Commons in data centers or on laptops, with mobile support planned. Every instance can publish, serve, or subscribe to data, within its permissions.
Connect your existing source or collection workflow to a Commons Store. Once connected, your application supplies records and updates; Commons handles versioning, synchronization, integrity verification, and retained history.
Read the developer guide →Built for data that others depend on.
Start where collection is difficult, handoffs repeat, or received data needs to stay usable. The data doesn’t need to change constantly.
Keep every subscriber connected to changes in the registers a regulator maintains.
Explore the use case →Coordinate service, asset, and operational data across water and energy organizations.
Explore the use case →Follow changes in supplier records, product information, and certificates.
Explore the use case →Give AI current inputs and record-level history to build on, with MCP capabilities to list, read, and search datasets.
Explore the use case →Define a common collection and validation model, while participants keep their formats and applications.
Explore the use case →Explore Commons with the data you collect, publish, or depend on.
Join the waitlist for product updates and access announcements. Tell us which collection, publication, or access problem you want to improve.
Keep shared data connected as it changes.