PXNT

PXNT · the operations platform

One platform for every operation.

PXNT is built once and runs the daily work of very different businesses: who does what, where and when, live. Each business gets its own product on top, with its own name, look and data.

See what's insideFor investors
Security: every way in is checked
AVGVSTVSthe engine
MERCVRIVSservice network
01020304050607010203040506Your structure, read by bothOrganizationSitesAreasPostsPeoplePlatform servicesSign-inAlertsMapsBillingAI assistConsolethe next productCustomersProviders
1Platform, built once
3Products on PXNT
4Languages
0Shared customer data

Inside PXNT

An engine for the daily work. A network for the services.

The engine

PXNT — AVGVSTVS

  1. 01Who works where
  2. 02Every task, step by step
  3. 03Live risk
  4. 04Problems and alarms
  5. 05Handover between shifts
Inside Augustus

The service network

PXNT — MERCVRIVS

  1. 01Storefronts
  2. 02Providers and offers
  3. 03Dispatch on the map
  4. 04Proof at the door
  5. 05Billing
Inside Mercurius

Platform services

Under every product, built once.

Security, providers, billing, notifications, rotas, profiles, paper, AI assist and the console: what every product needs, kept once.

01

Part 01 · Security and permissions

Who you are, and what you may do.

One sign-in system with passkeys, two-factor and step-up checks; organizations, roles that stack and a permissions grid down to the site; every refusal written down, and an audit trail of everything that happens.

  • Passwords, two-factor and passkeys
  • Step-up checks before sensitive actions
  • Organizations, members and roles that stack
  • A permissions grid down to the area and the site
  • Sessions, devices and new-device alerts
  • Rate limiting, and every blocked attempt audited
AVGVSTVSMERCVRIVSYour organizationSite 1Site 2AreaAreaAreaAreaOperatorallowedrefused, and written downEach person sees what their role allows, down to the site and the area.
02

Part 02 · Billing

From signed work to paid invoice.

Work signed in the cockpit becomes a billable line by itself. Invoices are grouped per customer and period, issued in the provider's own name, reminded when late and marked paid — plus the plans and subscriptions every app sells.

  • Billable lines straight from signed work
  • Invoices per customer and period, in the provider's name
  • Reminders and payment status
  • Plans and subscriptions
ECPKRecorded in ECPK · The bill, as the customer gets it
03

Part 03 · Notifications and background work

The right people hear. The work runs on time.

Email, text and in-app alerts from one sender, in each person's own language, in four alert levels — and scheduled and queued work that runs without anyone waiting for it.

  • Email, text and in-app from one sender
  • Each person's own language
  • Four alert levels
  • Scheduled rounds, reports and reminders

Email, text and in-app from one sender

Each person's own language

Four alert levels

Scheduled rounds, reports and reminders

04

Part 04 · Rota and presence

Who works when, and who is actually there.

Shift templates and coverage needs per site or zone, open seats that qualified people claim or apply for, availability and time-off, clock-in presence — and the working-time rules that check every plan.

  • Shift templates and coverage needs per site or zone
  • Open seats claimed or applied for by qualified people
  • Availability and time-off
  • Clock-in presence: who is actually on site
  • Working-time rules: rest, overlap, overtime
  • Timesheets built from the recorded times
MonTueWedThuFriSatSunEarlyLateNight◌ open seat● claimed◉ present
05

Part 05 · Profiles and directory

Every person and company gets a page.

A public page for every professional, structure and company, behind a shield that says who may see what; registry numbers checked; a directory that searches all of it — and the image library the pages and the platform draw from.

  • A public page per person, structure and company
  • A privacy shield: owner, followers, everyone
  • Registry numbers checked and verified
  • Follow, block, and who visited
  • Directory search with filters and highlighting
  • Image library and platform branding
Anna Kellerregistry no. · checkedverifiedwho may see whatEveryone: name and roleFollowers: contactOwner: everythinganna kel…Anna Keller · nurse · verified
06

Part 06 · Paper and exports

Every bill and report prints as it looks.

A document is printed from the real page by a headless browser, so the PDF is the screen, line for line: invoices with their payment slip, quotes, job receipts, customer statements, letterhead — and the books exported as CSV.

  • PDF printed from the real page
  • Invoices with a payment slip (Swiss QR-bill where used)
  • Quotes, job receipts, customer statements, letterhead
  • CSV exports of the books
  • A profile exported as a PDF
on screenthe pagePDFCSV export
07

Part 07 · AI assist

The AI does the typing. A person decides.

A roster or a manual arrives as a PDF and comes out as structured data; invoice texts are drafted; catalogs and content are translated into four languages; and an MCP server lets AI tools read what the apps know — always with a person approving.

  • Reads a PDF roster or manual into structured data
  • Drafts invoice texts
  • Translates catalogs and content into four languages
  • An MCP server for AI tools to read tickets and buildings
  • A person approves before anything is saved
roster.pdfreads the PDFKeller · early · ward BRossi · late · ward BMeier · night · ward AEN · DE · FR · IT
08

Part 08 · Platform console and app

Run the whole platform. Installed on any phone.

One console for tenants, packages, media, appearance and security; an install page that explains and then installs the app on any device; a kill-switch that clears broken old installs; web push and an offline outbox; four languages.

  • Super-admin console: tenants, packages, media, security
  • Install page with the steps for each device
  • Kill-switch service worker for old installs
  • Web push and an offline outbox
  • Four languages per person
consoleTenantsPackagesMediaSecurityany phoneinstallinginstalledEN · DE · FR · IT

The products

What each product proves.

Three products on one platform. MDXT and BBGI run on Augustus, the engine; ECPK runs on Mercurius, the service network.

  • MDXTMDXTCare operationsPXNT Augustus

    PXNT applied to people-centred healthcare operations: dossiers, care plans, visits, clinical work, qualifications, evidence and longitudinal follow-up.

    MDXT · On PXNT
  • BBGIBBGISite operationsPXNT Augustus

    PXNT applied to physical operations: staffing, rounds, alarms, incidents, risk, duties, evidence, escalation and handover.

    BBGI · On PXNT
  • ECPKECPKService operationsPXNT Mercurius

    A service-network product for customers, storefronts, providers, subscriptions, dispatch, location-aware delivery and billing.

    ECPK · On PXNT

The whole map

Everything, connected

The engine in the middle; around it, everything the platform does.

Point at a word to read it. Pick a heading to see it written out below.

The next app

The next app starts with all of this.

A new business doesn't rebuild accounts, security or billing, and doesn't invent its own way of running work. It plugs into the platform on day one and spends its time on its own trade.

  1. 01

    Its name and its look

    Its own brand, its own sign-in page, its own design.

  2. 02

    Its own field

    The screens and the words of its industry.

  3. 03

    Everything else, from PXNT

    The platform services, Augustus to run the daily work, and Mercurius to sell and dispatch.

For investorsThe platform
ProductsInvestors