Docs · How PXNT works
What PXNT is
One platform built once, one engine for the daily work, one service orchestrator between organizations, and the products that run on them.
Built once, for many products
Every product that runs real operations needs the same things underneath: people who sign in safely, organizations with their sites and areas, a record of who did what, and the daily work itself. PXNT builds those once, so a fix made in one place reaches every product that uses it.
PXNT is not something a customer signs in to. People use the products; the products run on PXNT.
The four parts
Products
MDXT, BBGI and ECPK: their own users, their own data, their own look and words.
AVGVSTVS
The engine. Runs the daily work inside an organization.
MERCVRIVS
The service orchestrator. Connects organizations, customers and providers.
The platform
Signing in, people and roles, places, resources, mail, notifications, billing, the console.
- The platform is what every product needs and none should build twice. Read about the platform.
- AVGVSTVS is the engine: who works where, every task step by step, risk as it changes, problems and alarms, handover. MDXT and BBGI run on it. Read about AVGVSTVS.
- MERCVRIVS is the service orchestrator: storefronts, providers and offers, sending the right person on the map, proof on site, billing. ECPK runs on it. Read about MERCVRIVS.
- The products are what people use. Each is a configuration of what PXNT builds: its look, its words, its own parts. Read about the products.
Two places for the code
What a product installs lives in one place, pxnt-kernel: the platform's services, the shared screens, AVGVSTVS and MERCVRIVS. What PXNT shows lives in another: this site, its drawings, its demo. The site never holds a customer's data and is never installed by a product.