Who can run what
Every member gets an account and uses the hosted services; running the software yourself is a Member State entitlement, and bodies operate under theirs. One matrix, per service, per member category — quoted by every page that answers the entitlement question.
The short answer
Using is for everyone. Member States, Corresponding Members, their Issuing Authorities and Test Laboratories, Utilizers and Associates, applicants — everyone gets an account and everyone uses the hosted OIML-CS SMART Platform; the hosted path never requires running anything yourself.
Running is a Member State entitlement. Self-deploying the SMART Platform (on-prem or cloud, with streaming updates on the rolling channel) attaches to the Member State category — an Issuing Authority or Test Laboratory operates its own instance under its proposing Member State's entitlement. The identity service software is the one piece any member may run on its own domain.
The matrix
Per service, per member category. Cells badged proposed are the programme coordinator's extrapolation, not yet confirmed policy.
- Use — hosted, on the official services
- Self-host — on-prem/cloud, under the category’s own entitlement
- Streaming updates — the rolling channel the deployment runbook names
- The upsell note — see the narratives below the matrix
- proposed the coordinator’s extrapolation — not yet confirmed policy
| Service | Member State | Corresponding Member | Issuing Authority / Test Laboratory (of a Member State) | Utilizer / Associate | Applicant / public |
|---|---|---|---|---|---|
| OIML SMART account (the identity service) | ✅ | ✅ | ✅ | ✅ | ✅ join flow |
| Identity service software | ✅ 🏠 🔄 | ✅ 🏠 | operates under its Member State | — | source available — license pending |
| OIML-CS SMART Platform (cloud) | ✅ | ✅ | ✅ their consoles | ✅ designated access | ✅ applicant portal |
| SMART Platform software (self-host) | 🏠 🔄 | ⬆️ available on ratification | operates under its Member State’s 🏠 | — | — |
| The demo instance | ✅ | ✅ | ✅ | ✅ | ✅ public sandbox |
| The Studio viewer | ✅ | ✅ | ✅ | ✅ | ✅ public |
| The Vocabulary | ✅ | ✅ | ✅ | ✅ | ✅ public |
| The status service | ✅ | ✅ | ✅ | ✅ | ✅ public |
| Ommisa, the AI service | ✅ member tier | ✅ member tier | ✅ | ✅ per designation | — |
| SMART Recommendations content | ✅ | ✅ | ✅ | ✅ | ✅ published |
| The trust registry (organization keys) | ✅ registers | ✅ | ✅ their organization keys | ✅ | — |
| The SMI Simulation | ✅ 🏠proposed | ✅ hostedproposed | ✅ | — | — |
| The SMART Twin (SMART+) | roadmap | roadmap | roadmap | roadmap | roadmap |
SMART today, SMART+ next
SMART · LIVE TODAY
Every row of the matrix above the twin line is the live SMART program: the account, the platform (hosted and self-host), the demo, the studio viewer, the vocabulary, the status service, the AI service, the Recommendations content, the trust registry, the SST pilot cells.
SMART+ · THE ROADMAP TIER
The matrix's last row, the SMART Twin, reads roadmap across every member category, and it means it: the SMART+ services have no entitlement cells yet because they are not yet services anyone can use or run. When the tier ships, the row fills in; the honest cell today is the empty one.
The paths upward
Three honest answers to the questions the matrix raises — never pushy, and the platform never sells what the OIML Convention governs.
Corresponding Member → Member State
Ratifying the OIML Convention unlocks the self-host entitlement (your own platform, your own data residency, the streaming update channel), the right to propose Issuing Authorities (a Corresponding Member designates Associates; a Member State proposes the bodies that issue), and voting participation. Membership is governed by the OIML Convention itself — the platform never sells what the Convention governs.
OIML membership →A body asks: can we self-host?
The honest answer: the entitlement is your Member State’s. An Issuing Authority or Test Laboratory operates its own instance under its proposing Member State’s entitlement — the Member State is the entitled party; the body operates. The IA-only, TL-only, and IA+TL postures exist exactly for this, and the platform’s federation means your instance talks to the OIML-CS platform either way.
Utilizer / Associate → fuller participation
Designated-body access is real access: the evaluation-report and certificate surfaces open per the designation your designating member grants. Talk to your designating Member State or Corresponding Member about what your designation opens.
The software, honestly
Self-hosting runs on the program's own repositories. Their availability today, checked against each repository's license file:
- oimlsmart/identity — the identity service software; public repo — none yet — source available, open-source license pending
- oimlsmart/smart — the SMART Platform (workflow engine + certificate PKI); member repo — none — source available to members
- oimlsmart/platform-server — the shared server kernel; member repo — none — source available to members
- primmel/editor — the Studio authoring surface; public repo — none yet — source available, license pending
- oimlsmart/status — the status service; member repo — none — source available to members
- oimlsmart/site-shell — the shared site shell (header, footer, tokens); public repo — none yet — source available, license pending
Where a repository carries no open-source license yet, the honest wording is the one above — "source available", never "open source". The self-host runbooks are live: the identity service's self-host runbook walks a member from a stock checkout to its own OP on its own domain, config-only; the SMART Platform's deployment runbook (topologies A and B, rolling upgrades) ships with the member repository.
Where to go next
The hosted services in demo posture: the fictional cast signs in through the identity service, each seat assumed as a persona.
The join flow, the approval path, and the self-host exception, walked on the identity service page.
info@oimlsmart.org, the programme's front-door address. Entitlement and deployment questions land here.
Verified 2026-08-29: every linked service answered live (the identity service's discovery document, the demo instance, the AI service, the status service, the Studio, the Vocabulary, the Recommendations, the SST), the self-host runbooks exist, and each repository was checked for a license file. The determination rules are the programme owner's policy; cells badged "proposed" await confirmation.