Connect your PLCs to the product passport
Feed real production-line data — batch codes, serial numbers, measurements, timestamps, material lots — straight from the shop floor into each Digital Product Passport. CyfroPass ships no PLC driver: you connect through the open REST API and an edge gateway you run, or a partner connector.
Machine data becomes compliant provenance
Instead of typing production facts into a form, let the controllers that already measure them write straight to the passport.
Tamper-evident provenance
Values come from the machine, not a spreadsheet. Every published passport is an immutable snapshot — audit-ready by construction.
Per-batch & per-serial passports
Push a passport for each production batch or individual serial number, each with its own data, UID and QR code.
Less manual entry
Line speed, material lot and timestamps flow in automatically. Fewer transcription errors, fewer gaps in the completeness score.
Audit-ready traceability
Machine-sourced batch and serial records feed the passport's supply-chain trace — a clean data trail for authorities and customers.
From PLC tag to published passport
Five steps, all over open standards. CyfroPass stays a REST endpoint; the shop-floor logic lives in an edge gateway you control.
- 1
Expose PLC tags
Make the tags you care about readable over an industry-standard protocol — OPC-UA, MQTT, Modbus TCP or Siemens S7.
- 2
Run an edge gateway
A small on-site gateway or connector reads those tags and maps them to passport fields — the keys defined by your product template.
- 3
Authenticate
The gateway holds a CyfroPass API key and calls the REST API as a bearer token (Authorization: Bearer cp_live_…).
- 4
Push to the REST API
Create or patch products, then POST batches or serials with a data object keyed by the template's field keys — /v1/products/{id}/batches and /serials.
- 5
Publish
Publish the batch or serial and CyfroPass mints its passport: a unique UID plus a GS1 Digital Link QR code, live in seconds.
Protocols the gateway speaks
- OPC-UA
- MQTT
- Modbus TCP
- Siemens S7
- REST / Webhook
Bring your own gateway or a partner connector — CyfroPass speaks open REST, so anything that can make an HTTPS request can feed a passport.
One request pushes a batch, one publishes it
Your gateway sends production data as a batch, keyed by your template's field keys, then publishes it. This mirrors the public API exactly — see the API docs for the full reference.
# Push a production batch straight from the line, then publish its passport
curl -X POST \
https://app.passflow.example/v1/products/PRODUCT_ID/batches \
-H "Authorization: Bearer cp_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: line3-2026-07-30-0842" \
-d '{
"batch_code": "LOT-2026-07-30",
"data": {
"material_lot": "COT-IN-8841",
"line_speed": "48 m/min",
"measured_at": "2026-07-30T08:42:11Z"
}
}'
# Publish the batch → its own passport UID + QR
curl -X POST \
https://app.passflow.example/v1/products/PRODUCT_ID/batches/BATCH_ID/publish \
-H "Authorization: Bearer cp_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"Send an Idempotency-Key on writes so a flaky line connection can retry safely. PRODUCT_ID and the data keys come from your product's template.
Built for OT/IT separation
The edge gateway keeps your controllers off the public internet — only it talks outbound to CyfroPass, over TLS.
Hashed API keys
Keys are hashed at rest and shown in full only once. Scope and revoke them per workspace at any time.
TLS everywhere
Every request runs over TLS. Documents are encrypted at rest; secrets never live in the repository.
Hosted in the EU
Data is stored in the EU (Hetzner), GDPR-compliant, with a data processing agreement in place.
OT/IT isolation
PLCs are never exposed to the internet. The gateway makes outbound calls only, and requests are rate-limited.
Ready to feed the line into your passports?
Read the API reference to see every endpoint, or create a free account and generate your first API key.