PXNT · the platform
How it fits together.
PXNT is the platform: sign-in, people, places, security, billing, notifications and the rest, built once. On it sit Augustus, the engine that runs the daily work, and Mercurius, the network that connects customers and providers. Every product plugs in with its own name, look and data.
Code shared, data never
Shared code underneath. Every product apart.
What PXNT shares is code, and only code. Every product keeps its own look, its own work and its own database. A care home's records never sit next to a depot's duties.
PXNT platform
Sign-in · Roles · Audit · Notifications · Billing · Background work · The engine · Rota · Profiles · Maps · Paper · AI · Console
Before and after
Where a fix goes
The platform services are where a shared fix pays off first. Before: a copy of sign-in, roles and notifications in every product, and a fix lands in one. With PXNT: kept once, and the fix reaches them all.
Four rules
What the platform always keeps
Code is shared, data never is
The platform is code. Every product keeps its own database, so one product's customers are never stored beside another's.
Every product keeps its own door
Customers sign in to the product they use, never to PXNT: the same sign-in system underneath, separate accounts on top.
Each product upgrades when it is ready
A product takes a new version of the platform on purpose. One goes first; the others follow once it has proven itself.
Differences become settings
Where products differ on purpose — how long a session lasts, which alerts exist — the platform supports both, and each chooses.
Signing in
One sign-in system. Three separate doors.
People never see PXNT. They sign in where they work.
Its own sign-in page
Each product's sign-in page wears its own name and look.
Its own accounts
A care team's account lives in its care app; a site operator's in its own.
The same protection
Passwords, two-factor, passkeys, step-up checks and alerts for a new device — in every platform, from one system.