Docs · How PXNT works
The platform
The services every product needs and none should build twice: signing in, people and their roles, places, resources, mail and the rest.
What the platform does
The platform holds what every product needs, written once and kept in one place. A product does not copy it: it installs it, chooses a version, and decides when to take the next one.
The services
| Service | What it does | Today |
|---|---|---|
| Signing in | Passwords, a second step, passkeys, asking again before something sensitive, sessions and devices, too many tries slowed down and blocked. | Built |
| The sign-in's mails (codes, the reset link, security notices) in four languages, in the product's brand. | Built | |
| The sign-in screens | Signing in, registering, a forgotten password, each in the product's own look and in four languages. | Built |
| People and roles | Who belongs to an organization, in which role, where; invitations, asking to join, asking for more; who may appoint whom. | Rules built, screens next |
| Resources | Which physical things and supplies exist, where they are, how many, who holds them, and whether the work has what it needs. | Rules built |
| Shared screens | The frame of the app, settings, notifications, search, documents, toasts, the media library, in each product's look. | Built |
| Notifications, profiles, appearance | Telling people what changed, who they are, how the product looks for their organization. | Next |
| Billing, documents, AI assist, the console | Invoices and payments, papers, help from AI that a person confirms, running every organization from one place. | Planned |
Shared, but never the same look
A shared screen takes each product's colours, fonts and corners, and inside an organization's own pages its brand. A difference between products becomes a setting, never a second copy of the screen.