Public roadmap
What we are building, and in what order.
Carbonex is in development. We publish this because anyone evaluating a pre-launch platform deserves to know what exists, what is next, and what is still an intention.
Read this first.
This is phase-level. It describes direction, not execution. You will not find internal scheduling detail here, because that would tell you less than it appears to.
This carries no dates. We do not publish a launch date because we are not certain of one, and publishing an uncertain date would be the first thing we asked you to trust that we could not deliver.
This is direction, not commitment. Order can change if what we learn while building says it should. When that happens we will change this page and say what changed.
The phases
| Chip | Meaning |
|---|---|
| In progress | Being actively built now |
| Next | The phase we move to when the current one lands |
| Planned | Committed to in direction, not yet started |
- 1In progress
Platform foundation and the core ESG journey
The foundations everything else depends on: one shared way of organising ESG information and the evidence behind it, a history that is added to rather than overwritten, access control for each organisation, and the core working journey running from start to finish — Configure, Generate Requirements, Collect, Validate, Resolve Gaps, Calculate, Review, Approve & Lock.
This is the stage where telling missing apart from zero is built in rather than added on. Missing, unavailable, not applicable and approved estimate exist as distinct answers from the very beginning, because adding them later would mean rebuilding everything above them.
It is the least visible phase and the one that determines whether any of the rest is worth building.
- 2Next
Enterprise reporting and the evidence pack
Turning a closed period into the documents an organisation actually has to produce. Closed periods fixed to the exact information behind them, then the reporting outputs drawn from them: the GHG Inventory, the Executive ESG Summary, the Board & Risk Pack, the Detailed Calculation Annex, and the Audit Evidence Pack.
The goal for this stage is repeatability. A report drawn from a closed period should give the same numbers whenever it is run, and every figure in it should lead back through the calculation to the evidence it rests on.
This stage also brings the assurance workspace, so an external assurance provider works against a closed period in a shared workspace rather than through an email thread.
- 3Planned
Full ESG breadth — social, governance, materiality and suppliers
Extending the same approach across the rest of ESG rather than adding separate tools alongside it. Social and governance topics with the same evidence and approval discipline as environmental data. Double materiality assessed against the same record, in both directions — impact on the world and financial impact on the organisation. Target setting and progress tracked against the evidence rather than against a slide.
And suppliers taking part directly: access limited to what concerns them, structured requests, evidence attached as it is submitted. This is the part that decides whether Scope 3 and value-chain data are genuinely usable or merely collected.
- 4Planned
Industry sector packs
The industry packs we build and verify, carrying the methods and activity types a particular industry needs — added to the same platform, never a separate product.
The priority packs are Banking & Financial Services (with PCAF methodology for financed emissions), Real Estate & Facilities, Manufacturing & Industrial, and Logistics & Transportation. The extended set — Energy & Utilities, Retail & E-commerce, Hospitality & Tourism, Healthcare & Pharma, Technology & Telecom, Construction & Infrastructure, Agriculture & Food, and Public Sector & Education — follows.
This phase also carries the framework mapping work: structuring data to match what GHG Protocol, ISSB/IFRS S1 & S2, GRI, ESRS/CSRD, SASB, TCFD-style disclosures, CDP and UN SDG reporting ask for. These are mappings, not certifications, and they are being built rather than held.
- 5Planned
Delivery as a service, integrations and security hardening
The work that turns a working platform into a product an enterprise can adopt. Onboarding new organisations. Administration at scale. Connections to the systems the data already lives in. The submission workspace. Analysis and risk over the same information the reports use.
And security hardening as a distinct, deliberate stage rather than an assumption: penetration testing, formal review of how each organisation’s information is kept separate, and pursuing the independent certifications an enterprise buyer will ask for. We hold none today. When we hold one, we will name the certification, the certifying body and the date.
We will update this. We will not backdate it.
As phases complete and priorities sharpen, this page changes. What will not happen is a phase quietly being reworded to look like it was always what we said. If we change direction, the page will say that we changed direction.
Planned launch — January 2027.
That is a month rather than a day, and the difference is deliberate: a day is a precision we do not have, and precision we cannot keep is the shape a broken promise arrives in. It is the only forward-looking date on this site.
The phases above are not dated individually. If the launch moves, this page will say so rather than quietly re-cutting the phases to fit. In the meantime, contact@yottanexa.com reaches us directly.