Try it
Not a video and not a guided tour — the real application, already populated with a fictional organization so there's something to look at. Open the Modules menu and work through them — 40 in the aerospace demos, 37 in the ISO 9001 one, because three of them exist to serve clauses ISO 9001 doesn't have. These demos run the quality system with the Production / Operations option switched off, so you're counting the 40-module QMS, not the 46-module full build. Open a nonconformance, read a PEAR, change a due date. It's yours for as long as the browser tab is open.
Pick the one that looks like you
Each demo is a different business with its own process map, its own people, and its own scope. The differences aren't cosmetic: a distributor excludes clauses a machine shop can't, a design house carries a whole clause the others legitimately scope out, and the ISO 9001 shop sees three fewer modules than the aerospace ones because those clauses aren't in its standard.
Prefer to read first?
The Demo Roadmap is a 23-page PDF guide to evaluating JBird: which of the four demos below to open, the ten minutes worth spending in each, and the seven-step path to setting up your own organization — whether it's your first quality system or you're bringing an existing one in. Every screenshot in it is taken from these demos.
Machines and assembles precision parts to the customer's drawing. Takes no design responsibility, so clause 8.3 is excluded with its justification on file. Purchasing is an activity inside Operations, because there's no purchasing manager.
Buys, stores and resells without altering the product. Purchasing is its own process with its own owner and metrics. Design and development is excluded from scope with a written justification, and everything else AS9120B asks of a distributor stays in.
Designs and builds flight-control actuation components. Employs engineers, so Design & Development is a process of its own — and clause 8.3 is fully exercised, down to a released project with a fracture-critical output and a post-release change the customer was notified of.
Machines and fabricates to the customer's drawing for industrial and commercial customers, one of whom sells on into an aerospace programme. Holds no sector standard, so it sees a 37-module menu rather than 40 and a Quality Manual with ISO 9001 clauses only. Big enough to employ a supply chain coordinator, so Purchasing is its own process — the opposite call from Fairhaven, on the same rule.
What you're looking at
The application stores nothing in your browser — no accounts, no cookies, no local storage. Change whatever you like; a refresh puts it all back exactly as it was, and nothing you type is ever sent anywhere.
We do count visits, and which modules get opened, using Plausible — cookieless, anonymous, no personal data, no cross-site tracking. It tells us that somebody looked at First Article Inspection, never who.
The organizations, people, part numbers, suppliers and findings are all made up. No real customer's data appears anywhere on this site, and none ever will.
You're seeing the build as it stands, not a curated slice. Two clause areas aren't built yet and the product page names both. If you find anything else missing, that's a real hole — tell us and it goes on the list.
Each demo is a single file of about 1.8 MB and runs entirely in your browser, so it may take a moment on a slow connection — and works fine with no connection at all once it has loaded. That is literal for the application itself: it loads no third-party code, so everything in it, including building an Excel file, runs on a machine with the network unplugged. The one external request the page makes is the analytics tag described above.
Where to start
Most evaluators go looking for the same records, so here's where they are. These are the ones that tend to separate a real aerospace QMS from a generic tool with the word aerospace in its name.
Where the app opens, and the map every other module hangs off. Open a process and take its turtle diagram and SIPOC — a standing view, not an audit snapshot.
A Form 3 PEAR, with inputs, activities, outputs, interfaces and KPIs pre-filled from the process map rather than retyped, and effectiveness scored on the standard's own grid.
On First Article Inspection: one accepted, and one rejected after a tooling change with reverification required — two hole positions out of true position, each linked to the nonconformance raised against it. Print its AS9102 Forms 1, 2 and 3. The rejected one is what an auditor asks to see.
On Organizational Context: the clauses a distributor doesn't perform, each one excluded against a justification that gets written into the scope statement.
On Design & Development: planning against the standard's a–j list, categorised inputs, a critical design review authorizing progression, a fracture-critical output, and a change the customer was notified of.
On Organizational Context: 22 clause-8 applicability rows, not 33. The eleven missing ones are AS91xx clauses — product safety, counterfeit parts, special processes — and an ISO 9001 organization is never asked to justify excluding a clause that was never in its standard.
Every register has one, and it downloads an actual .xlsx workbook to your machine, not a preview. Try it on NCR/CAPA or Suppliers. It's the answer to the question worth asking of anything that will hold records you get audited against: can I get my data back out?
On NCR / CAPA: containment, root cause, corrective action and the effectiveness check afterwards — the step most systems quietly skip.
Pilot program
46 modules are already built and working. Pilot organizations get the system at no cost during development, direct input on what gets built next — there is a Report a Problem button on every screen, and it goes to a register we work through — and a migration path when the IA9100 revision lands.