About Q360

Quality,
unfragmented.

We build Q360 because we were tired of clicking through twelve tools to close a CAPA. Tired of a sticky note reminding us about a document in Dropbox that should have been signed off in the QMS. Tired of spreadsheets that weren't the source of truth for anything except confusion.

Founded 2024 · Australia

Built by Quality + engineering

Operating Contract-first, dark mode

Standards live 5 · 7 in roadmap

Chapter 01 / 04

Standard-agnostic
by design.

Most QMS tools are built around a single framework — ISO 9001, or QSPP, or 13485 — and everything else is a bolt-on. Q360 starts from the opposite premise: that a modern operation runs against multiple standards simultaneously, and that evidence collected for one should satisfy clauses in every other it applies to.

One CAPA. One document. One audit finding. Mapped, cross-walked, and defensible across every standard you operate under.

Chapter 02 / 04

What we hold.

Four principles that decide how we build — when a tradeoff comes up, these are the things we don't negotiate.

Contract-first engineering

The OpenAPI spec is the source of truth. UI, API, MCP, docs — all derived. No drift, no "that's how the old endpoint works."

openapi.yaml → everything

II.

Evidence over assertion

Every status, every approval, every decision is a record — signed, timestamped, queryable. "Trust me" is not a valid audit response.

signed · timestamped · exportable

III.

Depth, not pretty

A QMS is the backbone of an operation. We build for the auditor, the line lead, and the ops director — not for a hero screenshot.

38+ modules · no fluff

IV.

Programmable by default

Everything the UI can do, a program can do. AI agents are just programs with opinions. We built the MCP surface so they can work on your quality system, not around it.

REST · Webhooks · MCP

Chapter 03 / 04

By the numbers.

How deep the system actually goes. Not a tagline — counted.

38+

Modules shipped

Documents, CAPA, NCR, audits, risk, SPC, training, suppliers — end to end.

Standards live

ISO 9001, ISO 27001, SOC 2, ISO 45001, QSPP 2026 (AS85000:2024). Seven more in the roadmap.

25+

MCP tool groups

Every QMS domain exposed to Claude and other agents, org-scoped by API key.

100%

UI via API

Every capability in the product is available programmatically. Not a subset — all of it.

The thesis

A QMS should feel closer to a Bosch technical manual
than to a consumer app.

— on why Q360 looks the way it does

Chapter 04 / 04

Industrial-editorial.

Three faces. One primary. One accent reserved for what's actually critical. The aesthetic is load-bearing, not decoration.

Display

Instrument
Serif.

Face: Instrument Serif
Weight: 400 · italic allowed
Used for: h1 · h2 · hero · editorial moments

UI body

Geist, for everything you click.

Face: Geist
Weight: 400 / 500 / 600
Used for: body · labels · forms · tables · nav

Numerics / IDs

IBM Plex Mono
CAPA-231 · v3.2

Face: IBM Plex Mono
Weight: 400 / 500 / 600
Used for: IDs · clauses · versions · counts · timestamps

Palette

Oxide#1F3A3D · anchor Signal#E15A3C · critical only Techoklch(0.86 0.11 200) · data Graphite#12161C · surface Paper#FBFAF7 · light mode

Ready to run your QMS

Let's get you audit-ready.

Start a free trial, bring your standards, and see how much a connected system changes the day-to-day.

Start free trial → See features