Describe the task
Explain a repetitive task in chat, in plain words, and attach a few real examples. No code, no tickets.
Scroll to explore
Describe, Spec, Hidden tests, In use
Explain a repetitive task in chat, in plain words, and attach a few real examples. No code, no tickets.
The Software Factory writes the software in minutes. A separate validator then checks it on test cases the builder never saw.
Your tool runs as a form, an API, a chat tool or via MCP, with costs on a ledger, and the next person can reuse it.
Models from OpenAI, Anthropic, Google, DeepSeek and more, chosen tool by tool.
Factory releases need independent validation and a human approval.
Released tools and tests can be reused by the next workflow.
Anyone on the team explains the task in chat and attaches a few real examples.
The factory asks what it needs, then proposes the spec and the test cases for you to confirm.
In minutes the Software Factory writes the code, then a separate validator checks it before release.
It runs in a sandbox with costs on the ledger, and every new version is tested before it replaces the old one.
Includes:
Everything in Start, plus:
Everything in Start and Team, plus:
A new visual editor connects tools into compositions, without writing glue code.
The Factory now builds with a coding agent on the Claude Agent SDK by default, with package checks and tests.
Teriyaki 2.2.1 brings the Software Factory, the Software Lab and SDK 1.x to production, with guided questions and package approval.

Automated EPUB checks against EPUB Accessibility 1.1 and WCAG 2.2 AA, with the issues to review and fix.

Two catalog tools extract data from FatturaPA e-invoices and XBRL financial statements, ready for your checks.

Deadlines in one place and, once enabled, a summary at 7 on weekdays and after every new entry.
A system, and a team behind it, that turns everyday work into software: anyone describes a task in plain words, and the factory builds, validates and runs the tool or agent that handles it. Every release leaves tools and tests the next one can reuse.
Minutes for a first tool: you describe the task, confirm the test cases, and the factory builds and validates it, usually in well under an hour. Bigger agents grow from there, one release at a time.
Both. The Software Factory writes the code, a separate validator checks it, also on cases hidden from the builder, and a person approves each Factory release. Forward deployed engineers help on the bigger workflows.
The right one for each task, from GPT, Claude, Gemini, DeepSeek, GLM and more. Tools use a registered model or the platform default, and a change of model can be checked against the tool's tests.
You do. Factory releases can be downloaded with their code, tests and spec, and admins can export tool data as CSV or JSON.
No. You describe what you need in plain words and confirm the test cases; the factory writes the code. Your developers can still open it, change it and keep it.