Product
Six surfaces, one contract
Every part of Nitentia is one of four things. They share a single typed contract, which is why a patient captured on the website is the same record the practice answers in the portal — with no export, no sync and no integration to buy.
The six
In production
The clinic website
Generated from a config file under the practice’s own brand. Static, fast, and impossible to publish incomplete.
In production
The patient inbox
One place for every enquiry, with its source and its consent record attached.
In production
Discovery
Eight weighted checks adding to 100, the searches that lead to the practice, and a file for AI tools to read.
Screens and review in production; writing waits on the server
The agents
Five assistants that produce drafts, with an authorship mark, the same advertising ruler and a mandatory human step.
In production
The clinic portal
Read the inbox, move a patient forward, edit the site. The owner’s side of the same contract.
In production, closed for unverified markets
The compliance gate
A build that refuses to publish what the rules do not allow — and stays closed where it cannot judge.
What is not here, and will not be soon
A product page that lists only what exists is a product page you can trust. Here is the other half.
The clinical agenda
Designed in detail — single-column by default, the missed appointment as a first-class state — and not shipped. When it is, this line changes.
The odontogram
Specified with FDI notation and five surfaces per tooth. It exists as a specification and a demo drawing, not as a product.
A clinical record
Not planned. The record belongs in the practice-management system the clinic already runs, and moving it is not a project anyone should take on lightly.
The shortest way to judge this is to see it
Thirty minutes, the working software, and an honest list of what is not finished.