Describe the process
Explain a repetitive process in chat, in plain words, and attach a few real examples. No code, no tickets.
Plain words, no code
By Hoplo
Scroll to explore
The factory for your company runs on.
Describe, Spec, Hidden tests, In use
[N.01/11]> Why Teriyaki
Build and validate
The Software Factory writes the software in minutes. A separate validator then checks it on test cases the builder never saw.
Minutes to build
Use it every day
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.
Reused by the team
[N.02/11]> By the numbers
[N.03/11]> The factory
Context in.Validated software out.
Inputs04
- Interviews
- Documents
- Spreadsheets
- Knowledge base
Context04
- Workflows
- Handoffs
- Exceptions
- Open questions
Opportunities
The right model, at the right cost
Frontier or open-weight models, chosen tool by tool. A model router sends each request to the model that handles it for less, so you don't pay for power you don't need.
- GPT-5.6 Sol
- Claude Opus 5.5
- Gemini 3.7 Flash
- DeepSeek V4 Pro
- GLM 5.3
- Claude Sonnet 5
- GPT-6 Luna
- Grok 4.6
- GPT-5.6 Luna
- Claude Haiku 4.5
Validated by default
Factory releases need independent validation and a human approval.
Built to compound
Released tools and tests can be reused by the next workflow.
On your cloud or on premises
Teriyaki runs on Hoplo's cloud, or we deploy it on your cloud or on your own servers, so your data stays where you decide.
- Hoplo cloud
- Your cloud
- On-premise
[N.04/11]> How it works
Describe
Anyone on the team explains the process in chat and attaches a few real examples.
Confirm
The factory asks what it needs, then proposes the spec and the test cases for you to confirm.
Build and validate
In minutes the Software Factory writes the code, then a separate validator checks it before release.
Use and improve
It runs in a sandbox with costs on the ledger, and every new version is tested before it replaces the old one.
[N.05/11]> What you get
Every release,in your hands.
[N.06/11]> Principles
What we hold to,release after release.
- Read more: Principle 01
Teriyaki
Principle 01
The model proposes, the program checks. Factory releases are judged by a validator the builder does not control.
Principles
- Read more: Principle 02
Teriyaki
Principle 02
A person approves every Factory release. The tests say it works, a person says it is ready.
Principles
Bring one repetitive process. In minutes it is software, and the code stays yours.
Teriyaki
Teriyaki by Hoplo
- Read more: Principle 03
Teriyaki
Principle 03
Every workflow can leave tools, tests and context behind for the next one.
Principles
- Read more: Principle 04
Teriyaki
Principle 04
Your code, your tests, your spec, ready to download whenever your team needs them.
Principles
[N.07/11]> Engagement
Includes:
- Describe the process in chat
- Spec and test cases proposed for you
- Built and validated in minutes
- Use it as a form, an API, a chat tool or via MCP
Everything in Start, plus:
- A shared catalog of tools and agents
- Reuse across workflows and teams
- A human sign-off before each release
- Costs per run on a ledger
- Roles and permissions for your team
Everything in Start and Team, plus:
- Forward deployed engineers with your teams
- Tools chained in sequence, with approvals between steps
- Changes checked by regression tests
- Run logs, optional tracing and alerts
- An append-only audit trail
[N.08/11]> Updates
Real updates,not roadmaps.
- Sep 26, 2026
Visual compositions
A new visual editor connects tools into compositions, without writing glue code.
- Sep 23, 2026
Agent generator by default
The Factory now builds with a coding agent on the Claude Agent SDK by default, with package checks and tests.
- Sep 22, 2026
Release 2.2.1
Teriyaki 2.2.1 brings the Software Factory, the Software Lab and SDK 1.x to production, with guided questions and package approval.
DocumentsAccessibility
Accessibility checks before you publish
Automated EPUB checks against EPUB Accessibility 1.1 and WCAG 2.2 AA, with the issues to review and fix.
FinanceE-invoicing
Invoices and financial statements, read from XML
Two catalog tools extract data from FatturaPA e-invoices and XBRL financial statements, ready for your checks.
OperationsAutomations
A deadline register with a summary at seven
Deadlines in one place and, once enabled, a summary at 7 on weekdays and after every new entry.
[N.11/11]> FAQ
Questions beforeyou start.
A system, and a team behind it, that turns everyday work into software: anyone describes a process 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 process, 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.