Apps · Software Factory
Requests in. Reviewed releases out.
A bug report, an email or an ask in chat becomes a plan, a pull request, a QA verdict and a release. New work waits for a person to approve the build. By default, a person merges product code. The person who asked hears back in the thread where they asked.
- 01
Asked anywhere
From chat, Slack, email, a Jira issue or a Sentry incident.
- 02
People decide
A person approves the build. By default, a person merges it.
- 03
The asker hears back
Each step lands in the thread where they asked.
Intake
Approve the build from one card.
A request arrives as a card that says what is asked, by whom, and what the factory proposes. Approve the build, request changes or defer it.
- Fixes can start sooner
- A bug fix someone asks for in chat, with its acceptance written down, starts without the card.
Handoffs
A gate at every handoff.
Product, design, engineering, QA and release each hand off through a gate. Merges of product code wait for a person by default.
Request
A bug, an email, a Jira issue, a Sentry incident or an ask in chat.
Approved
The product owner approves the build from one card.
Change
A worker builds in its own checkout, runs your checks and opens a pull request.
QA verdict
The reviewer checks the diff and evidence against the contract and records a verdict on the commit.
Merge
The engineering owner merges from a card with the verdict and the rollback.
Release
Your own pipeline deploys. A live check confirms each acceptance line in production.
Told
The person who asked hears back in their thread.
After release
It checks the change in production.
Once a change ships, the factory checks it live against the acceptance lines it was built to, and records the result on the feature. Production Watch turns new Sentry errors into incidents, and a code bug can come back through the same gates.
Turn it on
Add it to any workspace.
Turn it on from the Marketplace, or list its plugins in workspace.yaml. It needs a GitHub App connection, a record for each product and repo, and a runner.
Connects to
- GitHub
- Claude Code
- Jira
- Sentry
- Slack
- All integrations
# workspace.yaml
plugins: [software-factory, production-watch]A person merges product code
Merges of product code wait for a person by default. Pipeline fixes and rollbacks can merge on their own.
Decide on your phone
Each gate is a card you can decide in the app on your phone.
Your repos, your runner
Needs a GitHub App connection and a runner that builds in its own checkout. Builds run Claude Code, so the repo goes to Anthropic.
Get started
See Vocion run your team's real work.
Bring one job your team does every week. In the demo we walk through it on sample data shaped like yours, with the record it keeps.
For your team: a demo built around your job, on sample data.
For your engineers
Run it yourself
The requirements, the AWS path and the repo.