Quality managers
See what needs attention across every area on the home page. Approve dispositions, documents and supplier decisions.
Sheet 02 · About
Quality software usually records what happened after the fact. Fortress is built so the record is the work itself: exact, traceable and signed off as it goes.
General notes
Every drawing has a block of notes that apply to the whole sheet. These are ours.
A failed reading asks to be acknowledged or raised. A step that cannot finish says exactly what is still needed. The system suggests; people decide.
Pass or fail, scores, stage rules and permissions are decided in the data layer, so every screen, import and integration gets the same answer.
Limits, checklists and scoring models are copied into the record when it is used. Change the plan tomorrow and yesterday’s inspection still shows what applied that day.
History only grows. A correction is a new record with a reason beside the old one. Closed things stay closed until someone reopens them, on the record.
Instead of a red error after you press Save, each step shows a short “still needed” list up front.
Each organisation is walled off from every other, and registers export to CSV, so you can take your records with you.
Who it is for
See what needs attention across every area on the home page. Approve dispositions, documents and supplier decisions.
Run investigations, write control plans, tune sampling and read the charts that show a process drifting.
Start a job in a few taps, record readings against the right limits and raise a problem where it happens.
Open one page and follow a record from the lot to the corrective action, with names, times and reasons.
How it is built
Fortress QMS is a web application and an API on top of a PostgreSQL database. Every table carries the organisation it belongs to, and the database enforces who can read or change each row. The application cannot forget to check, because the check is not in the application.
Modules share one canonical set of parts, suppliers, machines, people and records rather than each keeping its own copy. A background worker handles the things that happen on a schedule: reminders, expiry, imports and notifications.
Your data, your files and the API that serves them run in London. You can see how we handle personal data in the privacy policy.
Sheet 07 · Release
Start a 14-day trial, set up your sites and invite the team. If you would like to see it first, tell us what you make and we will show you.
A card is needed to start the trial. You can manage or cancel it from the billing page at any time.