Carbon Management & Regulatory Compliance
Calculate your CBAM reports and corporate carbon footprint in one place. When the verifier asks where a number came from, the answer is on record.
| Process | SEE | Intensity | Status |
|---|---|---|---|
| Cement grinding | 4.0685 | ✓ Done | |
| Clinker cooling | 4.0595 | ✓ | |
| Rotary kiln | 4.0324 | ✓ | |
| Preheater | 3.7375 | Awaiting data | |
| Raw meal grinding | 3.4425 | ✓ |
Capabilities
Four core capabilities, shown with the real screen structure.
Every emission factor lives with its own version, validity window and citation. A published version can never be edited; a new value is added alongside.
Inputs are defined per tonne; period data is derived by scaling with declared output. Numerator and denominator share one multiplier, so a ratio error is structurally impossible.
Every write is recorded with who, when and what changed. Records are archived rather than deleted, so the basis of a past report stays readable.
The report is produced from a frozen run. Both languages read the same source, so figures cannot diverge between them.
Problem & fix
A verifier doesn't check the number; they check where it came from.
Product
Every link leaves its own record; no undocumented step anywhere in the chain.
System Overview
The numbers below are real — one example consumption record becoming a declaration. Fuel, electricity, purchased precursors: every input type takes the same path.
Exactly what the invoice says. You don't do the conversion.
Every factor from a versioned catalogue; nothing hardcoded.
The same calculation reproduces exactly, years later.
Output
A table alone isn't enough; the source behind each row travels with it.
| Goods category | Direct | Indirect | Total |
|---|---|---|---|
| Demir-çelik ürünleri | 2.9895 | 1.0790 | 4.0685 |
| Öncül: paslanmaz sac | 1.8420 | 0.7310 | 2.5730 |
| Toplam | 4.8315 | 1.8100 | 6.6415 |
Carbonixsha256=e391cd4676d0891cd77f67d3bd76e0e6775386b468ce5ce7ebe2311a6ea1ac45
Örnek belgedir — gerçek beyan değildir.
The document is produced in TR and EN; both read from the same frozen run, so the numbers cannot diverge.
PDF · WeasyPrint · TR / ENServices
Embedded-emission calculation and declaration-ready documents for goods covered by CBAM.
Fuel, electricity and process emissions in the same engine, under the same provenance discipline.
Compliance and reporting for EU packaging rules — recyclability, recycled content and waste reduction; phased in from 12 August 2026.
(EU) 2025/40Digital sustainability identity and life-cycle transparency — a QR-accessible passport; textiles, steel and electronics first, obligations 2028-2030.
ESPR (EU) 2024/1781What sets us apart
These aren't promises — they're the architecture.
Values live in versioned rule sets, not code. Every factor arrives with a citation and digest.
A published rule set never changes; a frozen run keeps inputs and intermediates.
Decimal arithmetic, dimensional checks, locked units. In doubt it stops rather than guesses.
Tenant data separated at database level; the audit trail answers who, when and what.
Who it's for
Producers exporting iron & steel, aluminium, cement, fertilisers, hydrogen and electricity to the EU.
Companies turning fuel and electricity consumption into a corporate inventory.
Timeline
CBAM definitive period. Embedded-emission declarations and verification obligations.
PPWR. Phased application of the packaging regulation begins.
DPP. The digital product passport becomes mandatory for certain products.
DPP first obligations. Textiles, iron & steel and electronics first.
FAQ
Each tenant's data is separated with row-level security at the database level. One tenant's query can never reach another's rows.
Nothing. A published rule set cannot be modified; a new version is added alongside. An old run stays bound to its version and keeps producing the same result.
No. For gas you enter the meter reading, correction factor and heating value as-is; the system converts and stores the intermediates. The unit is also locked to the stream type.
Every calculation is stored with the factors and intermediates it used; the audit trail shows who changed what and when. Source documents are bound by sha256 digest.
Yes. Documents are produced in TR and EN; both read the same frozen run, so the figures cannot diverge between languages. The interface itself is available in 12 languages.
Pricing
Questions first? The plans differ by term; the product is the same in all three. Amounts exclude VAT.
In every plan
Let's talk through your data and reporting timeline, and find the plan that fits.
Privacy notice
Last updated: —
Under Law No. 6698 on the Protection of Personal Data, the controller is — (legal name, address, MERSIS).
Name, organisation, role, e-mail, phone; account records and session data; request-form contents; support correspondence. Payment data is not processed — no collection takes place through the platform.
Providing and maintaining the service; evaluating requests and quotations; providing support; meeting legal obligations; ensuring system security and keeping an audit trail.
Art. 5/2-(c) performance of a contract, 5/2-(ç) legal obligation, 5/2-(f) legitimate interest; explicit consent where none applies.
Shared with hosting and infrastructure providers and competent public authorities, limited to the stated purposes. Any transfer abroad complies with Art. 9.
Retained for statutory limitation and retention periods; absent such a period, for as long as the purpose requires, then erased, destroyed or anonymised.
Under Art. 11 you may learn whether your data is processed, request information, learn whether it is used for its purpose, request rectification or erasure, learn the third parties it was transferred to, object to adverse outcomes of automated analysis, and claim compensation. Applications may be sent to —.
Policy
Last updated: —
This policy explains how information collected through the Carbonix website and application is used.
The installation, production, factor and emission data you enter belongs to you. It is processed solely to deliver the service; never used for marketing or sold.
Each tenant's data is separated with row-level security; one tenant's query cannot reach another's records.
Writes are logged with who, when and what changed. This exists for regulatory traceability and cannot be deleted.
Encryption in transit, authorised access, least-privilege and regular backups. No system can promise absolute security; breaches are notified under Art. 12/5.
On termination your data remains available for export for a reasonable period, then is deleted.
Policy
Last updated: —
Only strictly necessary cookies are used: session management, security and language preference. No advertising, tracking or profiling cookies.
| Cookie | Purpose | Duration |
|---|---|---|
| session | Maintaining the session | Session |
| csrf | Form security | Session |
| lang | Language preference | 12 months |
| cookie_ack | Remembering the notice was dismissed | 12 months |
Strictly necessary cookies cannot be disabled; blocking all cookies will break sign-in and language preference.
Agreement
Last updated: —
Carbonix is a regulation-based calculation and reporting tool. It is not a legal, financial or advisory service and does not substitute for a verifier.
The user is responsible for the accuracy and currency of data entered. Faulty input yields faulty output.
The operator is solely responsible for the content, timeliness and compliance of declarations submitted to authorities.
Reverse engineering, unauthorised access, automated bulk querying and resale are prohibited.
Planned maintenance is announced in advance. Liability for indirect damages is limited to the extent permitted by law.
Governed by the laws of the Republic of Türkiye; the courts of — have jurisdiction.
Agreement annex
Last updated: —
The tenant acts as controller, Carbonix as processor. Processing occurs solely on the tenant's documented instructions.
Hosting and infrastructure providers may act as sub-processors; changes are notified in advance and the tenant may object.
Personnel are bound by confidentiality; technical and organisational measures are applied under Art. 12.
On a breach the processor informs the controller without undue delay and supports the investigation.
On termination data is returned or destroyed, save where retention is legally required.
How it works
Your site data goes in; a declaration your verifier will accept comes out. Every step in between stays on record: which figure came from which document, which rule it rests on, when it was locked. You never have to go looking afterwards — the system writes it as it works.
Scope CBAM + corporate carbon footprint Output TR / EN document Decimal Decimal · 1E-10
The panel below shows that path live. It follows a single consumption record as an example; the system takes the same path for every input type — fuel, electricity, purchased precursors, process. The figures on screen are not stand-ins; they are the intermediates of a real run.
Installations, products, recipes and periods live here. Row-level security is
enabled and forced on every table — one tenant's query never sees another's row.
Because referential checks bypass that isolation, foreign keys are composite:
(id, tenant_id).
Exactly what the invoice says goes in: 32 m³ raw volume, correction
factor 1.006778, gross calorific value 11.050735 kWh/Sm³.
The user converts nothing — converting by hand means losing the record of the
intermediate. This is the only warm-coloured zone, because it is the only point
where data enters from outside.
The chain is visible: volume → standard volume → gross energy → net energy →
emission. All four intermediates are stored. The arithmetic is not floating point;
it is decimal, quantised to 1E-10. Not one coefficient is hardcoded —
every factor comes from a versioned catalogue.
Each factor carries its source and its status: 56.1 tCO₂/TJ from
IR 2025/2547 · regulatory_default, 0.90 from IPCC 2006 ·
scientific_default. The skipped default is recorded too — when a
row's actual heating value overrides the rule set's default, it does not happen
silently; it lands in the trace.
Direct and indirect embedded emissions on separate lines; the document is produced in TR and EN from the same run. A table alone is not enough — the source behind each row travels inside the document. Where there is no data it prints “—”, where the value is zero it prints “0”: those are not the same thing.
A period walks draft → data_entry → internal_approval → in_verification → LOCKED.
On lock the run freezes and the rule set it used becomes immutable. The same
calculation reproduces exactly years later — which is the answer to the verifier's
question, “why was this number this number that day”.
Two outputs from one run: a regulatory version for the verifier and a
commercial version for the customer. Both rest on the same frozen
calculation, so they cannot drift apart. Records are never deleted, they are
archived — deleting a supplier would delete the answer to “where did this
number come from”.
Plan request
The figure depends on how many sites and periods your organisation runs, which is why there is no fixed price on the site. Leave the details below and we will prepare a quotation that matches your scope.
Contact
Write to us about regulatory scope, data entry or the verification process. If you want a quotation, the plan request form moves faster.