Portaliq
One shared external portal for clients and suppliers, on . No separate login and no separate UI per app — one white-label front door, built on OpenRegister.
One portal, not one portal per app.
Every app that wants an external-facing surface used to build its own login, its own UI, its own auth model. Portaliq replaces all of that with one contribution registry: an app declares what a client or supplier may see and do in a small manifest, and Portaliq renders it, reads it through OpenRegister, and enforces the boundary.
Fail-closed auth edge.
A bearer-token portal session today, resolved server-side and never trusted from the client. Real DigiD (citizens) and eHerkenning (companies) federation is planned behind the same interface, pending an OpenConnector broker.
Declarative contribution registry.
Any app plugs in with one dependency-free class — no import of Portaliq, no info.xml dependency, inert if Portaliq isn't installed. procest, PipelinQ, and Scholiq already contribute in the current beta.
Subject-scoped, re-verified reads.
Portaliq reads each app's data through OpenRegister and re-verifies every row against the authenticated subject — a supplier only ever sees its own tenders, contracts, and invoices.
Whitelisted create actions.
Apps declare which fields an external subject may submit; the server stamps ownership, so a spoofed identifier in the request never survives.
Unified inbox.
Every contributing app's notifications land in one message list per subject, fed by OpenRegister's notification engine.
Partners shipping portaliq
Implementation, hosting, and integration partners that deliver portaliq to their customers. Pick the partner you already work with, or one whose stack matches yours.