Features · Built beyond the calculation
The calculation is the easy part. The real challenge is everything around it — collecting reliable data, preserving methodology and evidence, governing processes and turning environmental information into decisions.
Cleture was built as more than a calculator. From operational data to environmental impact. From environmental impact to continuous management.
Explore the capabilitiesCapability catalog · Three operating layers
Sustainability doesn't begin with a calculation and it doesn't end with a report. Cleture connects the data, environmental and management layers organizations need to operate it continuously.
Data & automation
100 capabilities
Connect the systems, people and processes where operational data originates. Turn fragmented information into structured, reliable and reusable data.
Selected capability
13 features
Automations consisting of nodes and connections can be created on a drag-and-drop canvas; adding, deleting, connecting, configuring nodes, assigning credentials, and using previous node outputs are managed from the visual editor.
Workflows can be kept in draft, active, or deactivated states; creation, editing, deletion, cloning, folder organization, visibility change, and manual execution are supported.
Workflow versions can be created, past versions can be listed and restored; annotations can be added to the canvas, and workflows can be imported/exported as JSON.
Workflows can be started manually, via a cron-based schedule, a webhook, or an external Workflow API call.
Scheduling can be done with cron statements and timezones; settings include active, paused, and closed states, next/last run time, total/successful/failed run counts, retry, timeout, and allowing conflicting runs.
A workflow can be opened as a GET, POST, PUT, PATCH, or DELETE endpoint; authentication-free, API Key, Bearer Token, Basic Auth, or HMAC can be used. Rate limits, CORS origins, request/response scheme, timeouts, activity, key renewal, and call logs can be managed.
Incoming webhooks are subject to constant-time token comparison, HMAC verification, per-request/IP-based database rate limiting, rigorous header redaction, body size limit, and log retention period.
Previous node outputs, workflow inputs, variables, and ENV values can be used with expressions in the form {{NodeAlias.data.field}}; thanks to the alias map, data can be carried using meaningful names instead of node IDs.
For each node, you can choose to stop the workflow, ignore the error and continue, redirect to error output, or retry; fixed/exponential waits, jitter, retryable error codes, timeout retry, and node timeout can be configured.
Each run is stored as a FlowRun, each node step as a NodeRun; input, output, error, duration, span/trace information, and status history are recorded. Background operations are processed by the worker using lease, idempotency key, and retry counters.
Unwanted parallel operation of the same workflow is prevented by a PostgreSQL-based heartbeat lock; locks left by a crashing worker can be cleared by the scheduler.
The workflow can be run in its entirety or up to a specific node, ongoing execution can be stopped, and stuck executions can be detected and closed as failed.
Executions can be filtered by workflow, status, and date; node tree, node input/output, error code, durations, workflow input/output, and trace information can be examined in detail.
The difference is what happens around the number
Activity data
×
Emission factor
=
CO₂e
Sustainability does not end with the result. It depends on the data, methodology, evidence, processes and decisions around it.
Connect
Get the data.
NetZero
Understand the impact.
Control Tower
Manage what happens next.
From operational data to sustainable decisions.
