What changed in the product
Every change you can see, with a date. No round-ups saying “various improvements”, but what is actually different.
2026
Public operating state and a security page
The status page measures database, authentication, file storage, mail delivery, the public passport site and every background job live instead of asserting them. Alongside it, a security page setting out hosting, tenant separation, every sub-processor and the Art. 32 GDPR measures, including what we do not have.
REST API 1.1: suppliers, audit trail and a Node SDK
New read endpoints for suppliers, data requests and the audit trail, plus separate access to telemetry time series. Node integrations now get a package with generated types instead of hand-written calls.
Public REST API for ERP and MES
Models, passports, events and telemetry can now be read and written straight from your own system. With separate test and live keys, fine-grained permissions, a dry-run mode, idempotency keys and a console in the dashboard to try calls out.
Request an intro call directly
A form instead of an email address: category, passport volume, timeline and topics are captured up front, so the call does not start by collecting basics.
Second-life exemption and declared non-applicability
The mandatory-field score now has four axes: category, cut-off date, second life, and fields that demonstrably do not apply to your model. Exempt fields do not vanish silently - they stay visible with a reason.
Disassembly instructions as a file
Disassembly and maintenance instructions can now be uploaded directly instead of only linked. Recyclers see exactly this document once granted access; authorities see all of them.
Short code per passport for the future EU registry
The registry entry will require an identifier of at most 50 characters. Every passport therefore already gets an immutable short code that also resolves to it.
Field suggestions from evidence documents
Data sheets and UN 38.3 reports are read and propose field values, each with the source passage and page number. Nothing is applied automatically: every suggestion needs your approval.
Per-field data provenance and a derived battery state
Every field value now carries where it came from: entered manually, from a supplier, from a document, from telemetry or via the API. The regulatory battery state is no longer typed in but derived from the event history.
Supplier catalogue with file evidence
The questionnaire grows from six to 29 fields across three catalogues for cell, material and BMS suppliers. For each field the supplier can upload a file as evidence.
Mandatory-field rules as data instead of code
Which field is mandatory from when and for which category now lives in a versioned rules table. A change in the legal situation is therefore a data change, not a rebuild of the software.
GTIN in the QR code normalised to 14 digits
The GS1 Digital Link specification requires the 14-digit form. Shorter input is now padded correctly so the QR code reads everywhere.
Complete field catalogue per Annex XIII
The data set now covers the full scope, including fields that only become mandatory later. Every choice field uses the same component with filtering, multi-select and free text.
Faster passport lists for large inventories
Passports load in chunks and are paginated, and the dashboard figures come from a single query. At tens of thousands of passports that is the difference between waiting and working.
Sign in with your own identity provider
Enterprise customers sign in via SAML through their existing identity provider. New users from the company domain join automatically with a preset role, never as an administrator.
Individual passport quotas
Different volumes can be set per company without inventing a separate plan for it. Usage is visible in the dashboard at any time.
Multi-select and status changes in one go
Passports can be selected in the list and moved to a new status together. For a batch of a thousand that removes the detour through individual calls.
BMS telemetry: state of charge and performance
Battery management systems report readings straight into the passport. The time series is shown as a graph and feeds the fields the regulation expects to reflect current condition.
Professional access for recyclers and authorities, plus an integrity chain
Recyclers and authorities get access to the extended fields after individual approval, and every lookup is logged. At the same time every stored version receives a SHA-256 fingerprint that includes the previous one - later alterations break the chain visibly.
Rate limiting, anonymisation and orderly offboarding
Public endpoints are capped, deleting an employee account replaces the plain-text name in the audit log with a placeholder, and ending a customer relationship follows a documented path with a grace period.
Outgoing webhooks
Events such as an expiring certificate or a status change are pushed to your systems signed, with retries on failure.
Public passport page behind every QR code
The QR code on the battery leads to a page showing exactly the fields intended for the general public. No account, no app, in several languages.
Supplier self-service, certificates and team
Suppliers answer data requests through a link, without an account with us. Certificates are stored with an expiry date and warn in time, and colleagues can be invited with a graded role.
Models and serialised passports
The core: maintain a model once, then generate thousands of individual passports from it, each with its own serial number and QR code.
Seen something you need?
The fastest route to a new feature is a concrete example from your day-to-day work.