The Production Safety Framework (PSF) defines what safe production AI deployment looks like across eight domains. That text is published openly and free to cite. What was missing was a working artifact - something teams could open, model a real workflow in, stress-test against PSF controls, and export as evidence.
WorkflowOS (PSF Workflow Studio) fills that gap. In June 2026 we released it under the MIT licence at github.com/troygamble/workflowOS. Use the hosted edition at /studio, or fork and self-host for client engagements.
Why open source strengthens WorkflowOS
Three reasons drove the decision:
- Credibility. An standards body that hides its reference tooling behind a paywall invites scepticism. Open source lets auditors, procurement teams, and practitioners verify that PSF language maps to real controls.
- Reusable evidence work. Delivery teams need a tool they can self-host, export from, and ship without licence friction. MIT removes that friction.
- Adoption without lock-in. WorkflowOS gives teams a practical way to apply PSF controls first. Formal credentials and organisation programmes then give teams a path to prove capability when they need public recognition, review, or procurement confidence.
What you get
Hosted vs self-hosted
Hosted Studio at productionai.institute/studio requires a free sign-in. Non-AI features work immediately. AI features use bring-your-own-key OpenAI credentials - add your key once in the Studio ⋯ menu. We do not supply a shared institute API key in production.
Self-hosted clones the public repo only. You supply your own Clerk application for auth and optionally a server-side OpenAI key. The extract does not include institute admin, billing, certification backends, or private automation - see /workflowos for the boundary summary.
Who it helps
- Practitioners designing a deployment before writing code - map human gates, integrations, and observability early.
- Delivery teams packaging discovery and design phases with exportable client artefacts.
- Delivery leads building review evidence from real workflow exports.
- Researchers and auditors who need a concrete PSF mapping, not slides.
Quick start
git clone https://github.com/troygamble/workflowOS.git cd workflowOS npm install cp .env.example .env.local npm run dev
Read the full README on GitHub for Clerk setup and AI route configuration. For institute context, see the Production Safety Framework and WorkflowOS.
This record is maintained by PAI and free to cite. If something is wrong or missing, tell us. Corrections and source suggestions keep the record honest.