LightworksBETA
THE QMS FOR AI/ML SAMD QUALITY MANAGERS

Walk into the audit knowing exactly what they'll find.

Because you put it there. Lightworks is the QMS for the people on the regulatory hook for AI/ML SaMD — every requirement, change and signature hash-chained to a 21 CFR Part 11 audit trail and one click from a submission-ready Design History File.

Free pilot for pre-submission · No procurement cycle
qms/Releases/New Release
Publish
Design History File
demo
Version v1.4.0
Lightworks-Labs
Effective Date: April 25, 2026
Release
Title
Post-market update Q4 2026
Version
v1.4.0
Patch
Minor
Major
Draft
Pre-release
Published
qms/Requirements
Save

Requirements

≡↕New
Covered2
MDR output shall be cryptographically signed
3 linked tests
Wellness session records shall not persist beyond device session
2 linked tests
+New record
Partial1
Severed floor access shall require biometric verification
1 linked test
+New record
Uncovered1
Cold Harbor
0 linked tests
+New record
No status0
+New record
eSign to Merge
4
7
3
0
9
2
I agree that this electronic signature is the legally binding equivalent of my handwritten signature, per 21 CFR Part 11 §11.100.
Harmony Cobel
§ 01 · WHAT YOU DO

Your job isn't paperwork.
It's defensible evidence.

You're the one who has to stand in front of a notified body, a 510(k) reviewer, or an internal exec and prove the AI you're shipping is safe, controlled, and traceable. Lightworks gives you the receipts before anyone has to ask.

01

Regulatory interface

ISO 13485, IEC 62304, 21 CFR Part 11, FDA PCCP guidance — pre-mapped to artefacts.

02

Audit clearance

Signed audit log per release. Every commit, comment, and approval, immutable and exportable.

03

Data quality

Drift monitors, training-data lineage, and validation reports tied to specific model versions.

04

Traceability

Requirements, tests and SOPs linked end-to-end — a coverage gap fails CI before it ships.

§ 02HOW IT WORKS

From Quality Manual to clearance, in five steps.

01

Set the system

Author your Quality Manual and SOPs in a clean editor. Start from ISO 13485 templates, or import what you have.

qms/sop/SOP-014.md · v3 · draft
02

Gate the work

Every change flows through a Change Request. You approve with an MFA eSignature — nothing merges without you.

CR-218 · awaiting QM signature
03

Capture the evidence

Engineering work is tied back to requirements and tests automatically. A coverage gap fails CI before it ships.

✓ 248/248 reqs ✓ 14/14 SOPs
04

Publish and Submit the DHF PDF

Tag a release. Lightworks compiles a 300-page Design History File with audit log, traceability matrix and SBOM — ready to submit.

release v1.4.0 → DHF.pdf · 312 pp
05›_

Question, Answer, Repeat, Clearance

The LQL console queries your QMS at any point in time — branch-aware, version-aware, SQL-style. An auditor asks what REQ-44 looked like at v1.2.0. You run a query.

SELECT * FROM requirements AT TAG 'v1.2.0'
QUALITY MANUAL

Markdown that feels like Notion. Signed like a medical device.

Author your Quality Manual, SOPs, and controlled documents in a clean editor with /commands, @mentions, and inline databases. Everything is stored as plain markdown in your repo — no proprietary format, no vendor lock-in.

  • · ISO 13485 templates pre-installed
  • · eSignature on every controlled document
  • · Version history is your git log
  • · Full-text search across branches
app.lightworks.md/qms
Commit
⌂ qms

Quality Manual

StatusPublished
✎ esignHarmony CobelApr 2, 2026

Scope and Field of Application

This Quality Manual establishes the QMS for Lightworks Labs, Inc. (the “Company”) Lumen Industries. It encompasses the full life cycle — design, development, cloud deployment, and post-market surveillance — of our AI-based Software as a Medical Device (SaMD), in compliance with ISO 13485:2016 and FDA 21 CFR 820.

@
CHANGE CONTROL

Nothing reaches production without your signature.

Every change to a controlled artefact — an SOP, a requirement, a cleared model — opens a Change Request. Reviewers add their context. You add the signature. The system blocks the merge until you do.

  • · Side-by-side diff of the controlled document
  • · Required reviewers per artefact class
  • · MFA eSignature with stated intent at merge
  • · Automatic impact analysis on linked reqs and tests
app.lightworks.md/qms/cr/CR-218
eSign & Approve
CHANGE REQUEST
CR-218
Update SOP-014
Model Retraining Procedure
STATUS
In Review
AUDITOR
Harmony Cobel
Mr. Milchick
Mark S.

Update model retraining cadence

Number218
StatusIn Review
DateApril 25, 2026
Branchesmainfix/drift-threshold
Comments
SOP-014
Retraining cadence: every 180 days
+Retraining cadence: every 90 days, drift ≥ 0.04 KS triggers ad-hoc retrain
BLOCKINGMerge requires QM eSignature · 21 CFR Part 11 §11.200(a)
eSign to Merge
2
2
0
4
1
6
I agree this signature is legally binding per 21 CFR Part 11.
Harmony Cobel
app.lightworks.md/qms/releases/v1.4.0
Compile DHF
⌂ qms / releases / v1.4.0
Pre-flight checks
All requirements traced to tests
248/248
All SOPs eSigned by QM
14/14
SBOM CVE scan clean
0 critical
Predetermined Change Control Plan
v2.1 active
Open change requests
1 in review
SUBMISSION-READY
Design History File
Lumen Industries · v1.4.0
1.Design Plan
2.SRS
3.V&V Reports
4.Traceability · auto
5.SBOM
6.Cybersecurity
7.Labelling
8.Audit Log
8 SECTIONS · 312 PAGES
DESIGN HISTORY FILE

The PDF that used to take three weeks. Compiled in seconds.

Tag a release. Lightworks bundles the SRS, the V&V reports, the traceability matrix, the SBOM, the cybersecurity documentation, the labelling and the signed audit trail into one paginated PDF — pre-flight checked, locked to the release tag, and ready to drop into a 510(k) eSTAR.

BUILD TIME 4.2s · 312 PAGES · ZERO SHAREPOINT

FOR YOUR QUALITY TEAM

Speak Git. Or don't.

Quality managers think in revisions and drafts. Quality engineers think in commits and branches. Lightworks lets each person pick their own vocabulary — the underlying file, the audit trail, the regulatory artifact stay identical.

One QMS. Two languages. Zero retraining for the auditor.

app.lightworks.md/settings/language
×

Language

Choose labels for Git and workflow concepts. Changes apply only to you.

Terminology preset
Quality / regulatory wording (revision, draft, change request…)
TechnicalNon-Technical
VERSION CONTROL
Technical (canonical)Your term
CommitSave
BranchDraft
Merge
Incorporate
Pull RequestChange Request
DiffComparison
RepositoryProject
§ 06WHY QUALITY MANAGERS CHOOSE LIGHTWORKS

Less paperwork. More control.

Stop sprinting before audits. Live in a permanent state of ready.

When your evidence is captured at the moment work happens, there is no "audit prep." Run a query, hit export, hand over the PDF. The notified body sees exactly what your team was doing yesterday.

WHY THIS, WHY NOW

FDA cleared 1,100+ AI/ML-enabled devices through 2024. None of the QMS tools their Quality Managers used were built for AI.

?
How long does audit prep take when evidence lives in Word, SharePoint, and email?
?
What happens when test results drift out of sync with your QMS because engineers are copying and pasting from their terminal?
1 export
to hand a notified body the full Design History File
0 weeks
the new audit prep window with Lightworks
FROM A QUALITY MANAGER
“The first audit I ran with Lightworks I didn't lose a weekend. The reviewer asked for our change history on REQ-44 and I had a signed PDF on her desk in ninety seconds. That used to be three days of archaeology.”
›_
FOR YOUR ENGINEERS
You get receipts. They get Git.
Under the hood, your QMS lives as markdown in your engineering team's repos, with branch-aware databases, CI checks, and an SQL-style query console. Your engineers will love it. You don't have to think about any of it.
Engineering page
§ 08PRICING

Per product line, not per seat. Bring everyone.

Loading pricing…
§ 09QUESTIONS

What Quality Managers ask first.

Lightworks is a tool you operate yourself. Your QMS — the Quality Manual, SOPs, controlled artefacts — lives in your control. Lightworks adds the editor, the change-control gates, and the audit trail. Your auditor reviews artefacts directly, the same way they do today.

Our SOP and DHF templates map to FDA's Predetermined Change Control Plan guidance, the Good Machine Learning Practice principles, IEC 62304 and IEC 82304-1. You can swap in your own templates at any time without losing audit history.

Every change is a hash-chained, signed event with user, timestamp, intent, and MFA assertion. Per release, Lightworks exports an immutable audit-log PDF — the kind a notified body or 510(k) reviewer can verify against the source artefacts in minutes, not days.

Yes. Under the hood it's Git-native and lives in their repository, with branch-aware databases and CI checks. They get the workflow they want; you get the controls you need. Same QMS, two languages.

Roadmapped for Q3, with built-in CAPA workflows, complaint intake, and adverse event tracking — all on the same audit-trail spine.

Yes. The QMS lives in plain markdown in your team's repository. Uninstall Lightworks and you keep every artefact, every signature, forever.

BUILT WITH QUALITY MANAGERS · NOT FOR THEM

The next audit is on your terms.

Twenty minutes with our team. We'll show you what your audit trail looks like on day one — and what your DHF looks like the day you tag a release.

Sign Up Free →See how it works