LightworksBETA
← PRODUCT
PLATFORM

Sign in with GitHub. Your QMS is already there.

Lightworks is built on top of GitHub. Your team signs in with their GitHub accounts, your QMS lives in your GitHub repos, your PRs are your change requests, and your Actions are your compliance pipeline. No separate system. No seat counting.

.github/workflows/lightworks-sync.yml
on: pull_request
types: [opened, synchronize, closed]
jobs:
stage-records:
if: github.event.action != 'closed'
- name: Create or resume submission
run: curl -sf -X POST "$LW_API_URL/api/v1/prs"
- name: Sync SBOM record
run: curl -sf -X POST "$LW_API_URL/api/v1/records"
PR #84 · Checks
lightworks / traceability
248/248 requirements covered
lightworks / esignature-gate
QM eSignature present
lightworks / sbom-scan
0 critical CVEs · 142 deps
lightworks / submission-staged
pr-84 → lw/api/pr-84
01

Sign in with GitHub

Authentication is GitHub OAuth. No separate user accounts, no password management. Everyone on your GitHub org gets access — repo collaborators are your QMS team, not a separate seat tier.

02

Pull requests are change requests

Edit a document and a PR opens in your repo automatically. Reviewers, approvals, and eSignature gates all live on the PR. Your GitHub workflow is your QMS change control workflow.

03

GitHub Actions for CI compliance

Traceability coverage, eSignature gates, and SBOM generation run as status checks on every PR — alongside your existing tests. Quality in the pipeline, not bolted on after the fact.

04

Releases and Change Log

Tag a GitHub release and Lightworks compiles the Design History File. The Change Log renders your full commit history as a branch graph with per-commit metadata — same data, purpose-built QMS view.