Build on Odal
Write rules and integrations that run on other people's nodes.
Product-group rules and integrations written by someone else can run on Odal Node, on infrastructure we never touch. A node runs a plugin because its operator accepts the plugin's signature, not because we approved it.
Nobody has built on it yet. This page describes what is possible today, not an ecosystem that already exists.
Three ways in
What you can build today.
Embed the open library
The regulatory core is a set of Apache-2.0 libraries anyone can use: the passport model, signing, credentials, GS1 Digital Link, the industrial export and the regulatory rules.
Write product-group rules
A product group's checks can ship as a plugin that runs in an isolated sandbox. A node refuses a plugin that is not signed by a key its operator trusts, unless the operator deliberately switches that check off for development. A new version can be installed on a running node without a restart.
Connect industrial systems
A node can serve a published passport in the Asset Administration Shell format that Industry 4.0 systems read. The structure follows the standard, but the field meanings use Odal's own identifiers for now, so a receiving system still has to map them.
The licence line
What is free, and where the line is.
The core library is Apache-2.0. Use it, adapt it and build on it freely.
The node is source-available under BSL-1.1. Running it for your own organisation's passports is free. Offering it to others as a hosted service, or shipping it inside a competing product, needs a commercial licence. Each release converts to Apache-2.0 four years after it is published.
The licensing page has the detail, and the licence texts in each repository are the ones that bind.
No lock-in
No central service to depend on.
Every node belongs to its operator, and every passport verifies without us. Nothing you build depends on a service we run.