Scroll to explore

The factory for your company runs on.

A product ofHoplo30 minutes to your first tool

Teriyaki is the AI software factory by Hoplo. Anyone on your team describes a repetitive task in plain words, and the factory builds, tests and runs the tool or agent that handles it, in minutes.

Describe, Spec, Hidden tests, In use

[N.01/11]> Why Teriyaki

No more AI pilots.Software that ships.

//001

Describe the task

Explain a repetitive task in chat, in plain words, and attach a few real examples. No code, no tickets.

Plain words, no code
//002

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
//003

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

Built to ship.Checked before release.

From one sentence to a working tool
30 min
Tools and apps ready in the catalog
59
Independent validation, then release approval
2 gates
Form, API, chat tool and MCP
4 channels
Without Teriyaki
With Teriyaki

Workload without and with Teriyaki, day by day (illustrative)

[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, per task

Models from OpenAI, Anthropic, Google, DeepSeek and more, chosen tool by tool.

  • 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.

[N.04/11]> How it works

From a sentenceto working software.

  1. Describe

    Anyone on the team explains the task in chat and attaches a few real examples.

  2. Confirm

    The factory asks what it needs, then proposes the spec and the test cases for you to confirm.

  3. Build and validate

    In minutes the Software Factory writes the code, then a separate validator checks it before release.

  4. 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]> Under the hood

Plain code.Yours to keep.

Create, validate, test and package a tool from the terminal.

Teriyaki
# create a tool and check it
teriyaki tool new invoice-check --runtime python
teriyaki tool validate invoice-check
teriyaki tool test invoice-check

# run it on sample inputs
teriyaki tool run invoice-check \
  --inputs invoice-check/inputs.json --detailed

# package the tool for the runtime
teriyaki tool pack invoice-check --output invoice-check.zip

[N.06/11]> What you get

Every release,in your hands.

Factory releases come as a package you can download.

Source code, tests and the spec it was built from, with the validation evidence as a separate file. Catalog tools also come with a Word manual and slides.

[N.07/11]> Principles

What we hold to,release after release.

  • 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 01
  • Teriyaki

    Principle 02

    A person approves every Factory release. The tests say it works, a person says it is ready.

    Principles

    Read more: Principle 02
  • Hoplo

    Bring one repetitive task. In minutes it is software, and the code stays yours.

    Teriyaki

    Teriyaki by Hoplo

  • Teriyaki

    Principle 03

    Every workflow can leave tools, tests and context behind for the next one.

    Principles

    Read more: Principle 03
  • Teriyaki

    Principle 04

    Your code, your tests, your spec, ready to download whenever your team needs them.

    Principles

    Read more: Principle 04

[N.08/11]> Engagement

Start with one task.Scale what works.

Start

Your first tool, built from a sentence.

Minutesto your first tool

Includes:

  • Describe the task 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

Team

Tools and agents for everyone's daily work.

Everyonebuilds their own tools

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

Company

One software factory across the company.

Every teamon one factory

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.09/11]> Updates

Real updates,not roadmaps.

Recent releases of the platform behind Teriyaki.

Every entry is already in the product, with its release date.

  1. Sep 26, 2026

    Visual compositions

    A new visual editor connects tools into compositions, without writing glue code.

  2. 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.

  3. 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.

[N.11/11]> FAQ

Questions beforeyou start.

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.

One task to start