LightworksBETA
Lightworks · Blog

Donuts.

Loops, layers, and the craft of shipping regulated AI. Notes on quality engineering, FDA clearance, and building the QMS your engineers actually use.

June 8, 2026
Lightworks

Why Your Engineers Hate Your QMS (And Why They'll Love Lightworks)

Engineers don't hate Quality—they hate being forced out of their tools. Lightworks meets developers where they already live, turning compliance from a bottleneck into a collaborative feature.

June 4, 2026
Lightworks

Continuous Compliance is Not a Buzzword, It’s a GitHub Action

Legacy providers treat Continuous Compliance as a buzzword. For AI SaMD, Lightworks defines it as GitHub Actions running automatically on every merge to prevent drift and upsert QMS records directly from your source code.

May 22, 2026
Lightworks

Connect Lightworks to Linear and Jira

Lightworks now connects to Linear and Jira. Link a requirement to the issue that implements it, a risk to the ticket that mitigates it, a complaint to the bug that resolves it — and let the status flow back into your QMS without anyone copy-pasting a key.

May 18, 2026
Lightworks

MCP Integrates AI with Your QMS

Lightworks launched a Model Context Protocol (MCP) server. AI agents like Claude, OpenAI, and Copilot can read your QMS records directly, and propose writes through the same Git-backed audit trail you already trust for regulatory submissions.

February 11, 2026
Lightworks

Git-Native Quality Management

If you're building an AI-powered medical device, you already live in Git. Your source code, your model training pipelines, your CI/CD — it all runs through repositories, branches, and pull requests. So why does your Quality Management System live in a completely separate universe of PDFs, Word docs, and folder structures that nobody trusts?

February 11, 2026
Lightworks

Markdown that Feels Like Notion

Let's be honest, nobody wants to write quality management documents. And nobody wants to write them in raw Markdown, staring at asterisks and bracket syntax in a monospace editor like it's 2009. But Markdown is the right format for regulated documents. It's plain text, so it diffs cleanly in Git. It's human-readable even without rendering. It's not locked into any vendor's proprietary format. And it plays perfectly with the Git-native compliance workflow that makes Lightworks possible.

February 11, 2026
Lightworks

No Vendor Lock-In

Here's a question nobody asks during the eQMS sales demo, What happens when you want to leave? Not because you're planning to leave. But because the answer tells you everything about the power dynamic you're entering. And in the medical device QMS market, that power dynamic is almost always tilted against you.