Open Access
FREE
No login required
For occasional public use and demonstration of the web calculator.
- Web calculation without account
- Heavy rate limiting
- No exports, no saved history, no logs
- Connector libraries remain freely inspectable
Start with open web access, evaluate the API and connector approach in a pilot, and scale towards organization-wide or framework-level deployment.
The free tiers help users understand the system. The paid packages make CO₂ calculation usable in real administrative and software processes.
FREE
No login required
For occasional public use and demonstration of the web calculator.
FREE
For testing workflows
For users who want saved examples, exports and a less restricted web experience before integration.
from
€3,900
Pilot package or annual entry
For testing the API and connector approach with one organization or one specialist system.
from
€12,000 / year
For institutional integration
For institutions integrating CO₂ calculation into internal systems and administrative workflows.
Custom
For multi-organization deployment
For ministries, umbrella organizations, shared services, or state-level rollouts.
The tiers are organized around practical use: web calculation, API access, connector integration, governance, auditability and support.
| Capability | Open Access | Registered Account | Pilot / Evaluation | Organization License | Framework License |
|---|---|---|---|---|---|
| Web calculation | |||||
| Web calculator | Included | Included | Included | Included | Included |
| Saved history | No | Basic history | Pilot history | Organization history | Configurable |
| Exports | No | Basic exports | Pilot exports | Administrative exports | Custom |
| API access | |||||
| Production API key | No | No | 1 production key | Multiple keys | Many or contractually unlimited keys |
| Test API key | No | No | 1 test key | Included | Included |
| Request volume | Rate limiting | Moderate limits | Capped volume | Generous fair use | Contractual high-volume model |
| Connector and integration | |||||
| Connector libraries | Included | Included | Included | Included | Included |
| Integration review | No | No | Basic review | Included allowance | Custom rollout support |
| Vendor-neutral integration strategy | Documentation only | Documentation only | Pilot guidance | Included | Strategic rollout support |
| Organization and governance | |||||
| Organization model | No | Personal account | One organization | Organization with sub-units | Full organization tree |
| User and role management | No | No | Limited | Included | Included |
| API key ownership | No | No | Simple | Included | Included |
| Auditability and replayability | |||||
| Replayable API responses | No API access | No API access | Included | Included | Included |
| Versioned API behavior | No API access | No API access | Pilot version | Stable versioning | Contractual versioning model |
| Long-term verification options | No | No | On request | Available | Custom |
| Support | |||||
| Support channel | No individual support | No individual support | Email support | Email and integration support | Custom support model |
| Procurement and rollout support | No | No | Pilot documentation | Available | Included |
For vendors, internal IT teams, and public-sector projects that need help connecting existing systems to the provider-neutral library and API.
Support for understanding the connector model, adapting request mappings, and defining reliable test cases.
Assistance for evaluating providers, switching integrations, or running systems side by side during verification.
Help preparing technical, procurement, and governance documentation for institutional use.
Workshops for product owners, administrators, vendors, and internal IT teams.
For public-sector use, the main value is not only the calculation endpoint. The package includes integration help, sensible software architecture, governance, auditability, replayability, API-key management, and a clear path from pilot to organizational rollout.
Request volumes should be predictable and fair, but they should not become the main design principle for administrative infrastructure.
Short answers for evaluation, procurement and rollout planning.
Tell us whether you are evaluating the API, integrating a specialist system, or planning an organization-wide rollout. We can help map the right package and next steps.