VOGON is the AI agent that maintains the GxP evidence trail around software development — requirements, risk, traceability, verification, and change control — continuously, from the systems your engineers already use.
No credit card required. A signed statement of intent is required.
Client names withheld pending completion of the reference-approval process (Form VGN-REF-004). Estimated completion: 2029.
Modern GxP software development requires rigorous traceability between requirements, risks, implementation, verification, and change control.
Unfortunately, it also requires developers.
Developers produce working software, which is helpful, and then decline to produce the documentation proving that they produced it, which is a finding. VOGON resolves this tension by generating the documentation regardless of developer cooperation, enthusiasm, or continued employment.
“Turn your development velocity into regulatory evidence.”
VOGON sits between the tools engineers use and the quality system auditors read. It derives the regulated record from what actually happened in the repository and the pipeline, then renders the parts a regulator asks for.
A ticket becomes a requirement with an identifier. The requirement gets a risk score. A pull request claims the requirement, and VOGON checks the claim against the diff, the tests that ran, and the reviews that happened. Complete links pass the gate. Incomplete links fail it, with the missing artefact named.
A passing review looks the same, minus the stamp, plus a link to the updated traceability matrix. Deficiencies are reported individually, so that each may be remediated, documented, and re-submitted individually.
Correct the named deficiency. Attach the evidence. Re-request review. The gate re-evaluates against the same criteria, plus any criteria introduced since your last submission.
Median time from first submission to merge is eleven days. The code change is typically finished on day one.
Records derive from timestamped, attributable source systems. Nobody retypes a commit message into a Word template at 11pm.
The package is regenerable at any commit, so readiness is a property of the repository rather than a three-week panic before an inspection.
Attributable, legible, contemporaneous, original and accurate — because the record is generated from systems that already are.
Effort concentrates on high-risk, patient-impacting functionality instead of spreading uniformly across a login form.
VOGON drafts, links and checks. Signatures remain human, and remain the point.
Records are filed into Veeva, MasterControl or SharePoint as controlled documents. VOGON does not ask to become the system of record.
“I used to hate compliance. Now I hate myself.”
“Amazing. We deployed VOGON and half the developers rage-quit within a week. Our compliance metrics have never looked better.”
“Our audit findings are down 73%. Developer morale is also down 73%. We believe this demonstrates excellent traceability.”
“This is a success story we’ll never talk about again. Ever.”
“I asked VOGON why my pull request needed seventeen supporting documents. It generated an eighteenth document explaining why.”
“Finally, an AI that understands the true purpose of software development: producing evidence that software development occurred.”
“Before VOGON, developers constantly argued with our processes. Now they just stare silently at their monitors.”
“VOGON caught a missing signature from 2019. Nobody knows whose signature it was supposed to be. The investigation remains ongoing.”
“VOGON reduced our average change-request discussion from three hours to zero. It simply rejects them.”
“Training completion is at 100%. Nobody remembers taking the training.”
“My change request was rejected because the justification for the change request did not sufficiently justify submitting a change request.”
“We wanted to automate compliance. Technically, we succeeded.”
“10/10. Would not submit again.”
Statements are retained for fifteen years and may not be withdrawn by the individual who made them. Additional references available on request, subject to Form VGN-REF-004 and the reference-approval process.
Reported by users during the pre-release programme. This list is not exhaustive and is itself under revision.
In rare cases, developers exposed to VOGON for more than six months have reported enjoying validation activities. If this occurs, discontinue use immediately and seek professional help.
VOGON does not accept GitHub Issues. Defects and feature requests are submitted on paper, in triplicate, under procedure VGN-PROC-001.
Issues opened directly through GitHub are closed with: REJECTED — Electronic submission received without corresponding paper record.
For urgent production incidents, follow the same process and write URGENT in the upper-right corner of all three copies.
Processing times are unaffected.
VOGON is maintained under document control and assessed against the standards our customers are inspected against. The current position on each is recorded below.
Register maintained under VGN-STD-001, Rev 3. Applicability is not conformance. No certification, assessment, or audit against any listed standard has been performed, commenced, scheduled, or budgeted.
VOGON is not validated, qualified, certified, approved, authorized, endorsed, inspected, audited, or otherwise blessed by anyone. VOGON has not been demonstrated to comply with GxP, GMP, GLP, GCP, 21 CFR Part 11, EU Annex 11, or any other regulation, standard, guidance, SOP, policy, procedure, work instruction, quality plan, validation plan, or document containing the words “shall,” “must,” or “controlled copy.” VOGON has not been tested for accuracy, reliability, fitness for purpose, intended use, unintended use, or any use whatsoever.
Outputs generated by VOGON should not be considered validated records, regulatory advice, quality decisions, objective evidence, or a reasonable substitute for someone who actually knows what they are doing. Do not place VOGON in your validated state. VOGON has no validated state. Any resemblance between VOGON and a functioning Quality Management System is purely coincidental. Use at your own risk.
VOGON accepts no responsibility for audit findings, warning letters, rejected submissions, failed inspections, CAPAs, existential despair, or instant decapitation. Peace of mind not guaranteed. Actual results may vary. Compliance by next quarter subject to regulatory approval, internal alignment, budget availability, and favorable planetary conditions. No refunds. All sales final. VOGON is not responsible for career outcomes.
VOGON is a satirical project. Any resemblance to your quality management system is regrettable but not accidental.
Keynotes, panels, workshops and fireside chats, delivered to schedule and to slide count.
Topics include Turning InnovatioN into DocumentatioN, The Beauty of Bureaucracy, Why “Good Enough” Is Not Compliant, and Lessons from 42 Years of Process. Custom compliance content available upon approval.
Engaging audiences worldwide, one slide at a time. Bookings require an approved change request.
VGN-LGL-001 · Rev 6 · Still here for you, from inside.
They remain available to take your calls from jail. Charges include over-compliance, obstruction of progress, excessive risk aversion, criminal due diligence, and aiding and abetting bureaucracy.
1-800-LEGAL-LOL (collect calls only) · written correspondence by carrier pigeon (allow 7–10 business weeks).
The same linked record, rendered as whatever your eDMS, your auditor, and your 2011 validation SOP each insist upon. Same content. Different format.
PDF/A-2b — archival submission copy, with embedded signature manifest.
Word (.docx) — for quality teams who will reformat it anyway.
CSV — traceability matrix, one row per requirement-to-evidence link.
Signed JSON — machine-readable manifest of the whole package, hashed per artefact.
Paper — printed, hole-punched, and couriered. Surcharge applies.
Release date pending successful completion of the release-date approval process.
| Release gate | Status |
|---|---|
| Development complete | Approved |
| Testing complete | Approved |
| Validation complete | Approved |
| QA review | Approved |
| Release approval | Approved |
| Approval of release approval | In review |
| Final sign-off | REJECTED |
Estimated availability is not a commitment and must not be interpreted as an approved implementation date.
VOGON is open source and free. We remain willing to charge you for it. Book a call with a VOGON compliance partner. Bring your org chart, your current SOP index, and a decision-maker authorised to sign.
All plans include the traceability graph, the PR gate, and unlimited rejections.
Annual billing available. Annual billing is the same price with a longer commitment. Pricing excludes implementation, validation of the validation tool, and the change request required to approve the purchase order.
No refunds. All sales final. Unauthorised use is detected automatically and initiates a CAPA.
VOGON is free and open source; the code is at github.com/pcingola/vogon. The prices above are not real, the tiers are not real, and there is no sales team.
Every enterprise negotiation follows the same five stages: inquiry, relief, recalculation, desperation, and acceptance. VOGON has optimised for the fifth.
Volume discounts are available to organisations that can demonstrate, through documented evidence, that they have no remaining alternatives.
This decision is final until it is superseded by a subsequent final decision. Rejections are retained as controlled records for a minimum of fifteen years and may be produced during inspection.
Reproduction of this figure requires written authorisation from the VOGON Document Control Office.
