01Onboard
What happensThe product declares itself in a manifest and is registered against an owning domain
ResultA route exists; nobody can reach it yet
An Axiarium platform · Access layer
One console for every product we build.
Axordium is the layer that sits in front of Axiarium's products: a single sign-in, a tree scoped to exactly what each person is allowed to open, and a record of who saw what.
Access is granted by Axiarium, not by signup. There is no self-service tier today.
One loginSSO, no per-product account
Scoped by roleYou see only what you are granted
RevocableAccess ends without a redeploy
Signed in as reviewerScoped session
01
Chargeback win probabilityGranted · read and run
Open02
Contract renewal trackerGranted · read only
Open03
Everything else in the estateNot granted — not listed
HiddenEvery open is written to the audit logAccess on record
What it is
An access layer, not another product.
Axordium does not analyse anything. It decides who may open what, and keeps the record.
What Axordium does
Holds one sign-in for the whole portfolio, renders a tree scoped to each person's grants, proxies each product behind one authenticated address, and records every launch. Adding a product is a registry entry and a reviewed change — not a new auth decision taken from scratch.
What Axordium does not do
It does not build use cases, route between them with a model, or reach into their data. Each product keeps its own logic and its own database; to Axordium they are opaque. There is no cross-product data sharing and no shared data model.
How it works
Onboard. Grant. Open.
Three steps, each one reviewable, none of them requiring a product's code to change.
A product that someone needs to see
02Grant
What happensA named person is given a role scoped to that product, or to a whole domain
ResultIt appears in their tree, and in nobody else's
03Open
What happensThey sign in once and launch it from the console
ResultA scoped, time-limited session — and an audit entry
Revoking reverses step 2 alone. No redeploy, no change to the product.
Access & control
Built so that access can be proven, not asserted.
The same standard Axiarium applies to its numbers, applied to its permissions.
Least privilege by default
Nothing is visible until it is granted. A role is scoped to a product or to a domain, never global by accident, and the console tree is pruned to match before it is ever rendered.
- Seven fixed roles, including a view-only auditor
- A product still in draft is not listed, even to an admin's grantees
- Grants are revocable in place
An audit trail that is the record
Every launch, grant and revocation is written down. The auditor role can read that trail and change nothing — the point is that someone can check without being able to alter what they are checking.
- Who opened what, and when
- Read-only access is a real role, not an honour system
- Sessions are short-lived and re-issued, not permanent
Status
In build. Stated plainly.
Axordium is an Axiarium platform under active construction. The console runs, the access model is implemented and tested, and it is being used to front Axiarium's own products first. It is not open for self-service signup, and access today is granted directly by Axiarium.
Ask about access →Already have access?
Sign in to the console. If you were expecting access and do not have it, ask the person at Axiarium who set it up.
Sign in