AI software factory

Software built by AI.Checked by someone else.

Describe in chat the app your team needs. Teriyaki builds it, an independent validator tests it, a person approves it. Then it stays online for your colleagues, and IT keeps control.

  • No coding needed
  • Tested before every release
  • Approved by a person
  • The code stays yours
> Pick a request
Release reportExample

> Request

Expense approvals for the admin team

  1. 01Requirements confirmedOK
  2. 02Software and tests writtenOK
  3. 03Validator, separate from the builder
    Visible cases12/12
    Hidden cases8/8

    the builder never saw them

    Security scanPassed
  4. 04Approved by a personnot the one who built itOK
Published · Version 1expense-reports
expense-reports.app

Illustrative example: the screens are real catalog templates, in Italian, with test data.

Teams build: CRM, Customer portal, Supplier portal, Expense reports, Leave requests, Purchase requests, Non-conformities, New hires, Stock and inventory, Dashboards and reports, Intranet.

> How it works

Who builds itdoesn't grade it.

Four steps, from a sentence to an app your team uses. The step everyone else skips is the third.

  1. 01

    Describe

    Tell the process in your own words, with a few real documents. Teriyaki asks for what is missing and you confirm the requirements.

  2. 02

    Build

    It first proposes what already exists, then writes the software and its tests. You watch it grow in the preview and change it in words.

  3. 03

    Verify

    A separate validator tries it, also on cases hidden from the builder, and tells you what it checked.

  4. 04

    Approve

    A person approves it, and if you want, not the one who built it. Then you decide who uses it. Every change is a version.

> Built with Teriyaki

Real apps,born from a request in chat.

Three templates from the catalog: start there, say what to change, and you have your own version.

app.your-company.com
Expense reports

Real screens of catalog templates, in Italian, with test data. Examples, not customers.

The model proposes.The program checks.A person decides.

> What's inside

Everything already inside.And we run the apps.

No server to buy, no database to set up, no services to stitch together. You publish, and the app is online for those who need it.

You talk, it builds, you watch.

Chat on the left, the live preview on the right. Every change is a version you can undo.

teriyaki.hoplo.ai
Teriyaki: the chat with the builder on the left and the live preview of the app on the right

It connects to what you already use.

And to your internal systems through their APIs. Every app is also an MCP server for your assistants.

Google Workspace, Microsoft 365, Stripe, HubSpot, Slack, REST API, MCP

Real code, yours to keep.

Download it whenever you want and run it where you prefer.

your-app.zip
  • React
  • TypeScript
  • PostgreSQL

> In every app

  • 01

    Database

  • 02

    Access and roles

  • 03

    Files

  • 04

    Email

  • 05

    Your domain

  • 06

    A copy of the data every night

  • 07

    Versions, and you can go back

  • 08

    A check of the app every night

> For IT

Everyone builds.IT keeps control.

People who know the work build what they need. The rules are set by IT, once for everyone.

teriyaki.hoplo.ai
Teriyaki IT console, Permissions: the three levels (Free, Balanced, Controlled) and where Business Builders publish on their own
3
roles: User, Business Builder, IT Admin
DE
servers in Germany, backups in Finland
CSV
and JSON: the activity log can be exported
> Enterprise

Teriyaki in your company.We stay with you.

Departments build the software they need, IT sets the rules, and Hoplo's people stay with you, from onboarding to the integrations with your systems.

Tell us about your company.

A person from Hoplo answers you. The price is prepared with you, on your people and the services you need.

or write to info@hoplo.com

> What it includes

  • 01Onboarding

    We set Teriyaki up on your people, your departments and your rules.

  • 02Training

    Those who build learn to do it well, those who use know where to find the apps.

  • 03Consulting

    We choose together the first jobs to turn into software.

  • 04Integrations

    We connect Teriyaki to the systems you use every day.

  • 05Company sign-in

    Google Workspace, Microsoft Entra ID, Okta or SAML 2.0: no extra password.

  • 06Your brand

    Logo, colours and name are your company's.

  • 07Yaki

    Each person's assistant, on mail, calendar and documents. An action starts only with your yes.

  • 08Where you want

    On our servers in Germany, on a dedicated instance or in your data center.

> Five steps, until the team builds on its own

  • 1Discovery callFree. We see whether Teriyaki is right for you.
  • 2Mapping the workOn a video call the team shows how it works.
  • 3The first softwareTeriyaki builds it and tries it on your real documents.
  • 4HandoverThe team learns the platform and builds the last one itself.
  • 5AutonomyThe team builds on its own, with Teriyaki at its side.
> FAQ

The questions of thosewho decide for the company.

A system that turns a plain-language description of a business process into working software, and keeps that software under control after release. An AI builds it, an independent validator checks it on tests the builder never saw, a person approves the release.

Companies where several departments have repetitive work to turn into software, and where IT wants to set the rules once for everyone. People who know the work build, IT governs, Hoplo stays with you from onboarding.

With single sign-on (SSO) over OpenID Connect or SAML 2.0: Google Workspace, Microsoft Entra ID, Okta, Keycloak. It applies to the domains you have verified, and you can make it mandatory. With SCIM, people are created and disabled from your identity system.

IT. From the console it chooses how free departments are, where they can publish and when an IT Admin has to approve. No app goes online without testing and the security check, and every action stays in a log that cannot be edited or deleted.

On servers in Germany, with backups in Finland; every app has its own database and a copy every night. Hoplo's support gets in only if you allow it from the console, and that access closes by itself. The console also holds the documentation for GDPR and the AI Act.

The ones IT allows: models from several providers, local models too. Each app uses the model that fits its task, with spending limits per person and per department and an alert before the credits run out.

Yes: Google Workspace, Microsoft 365, Stripe, HubSpot, Slack and your internal systems through their APIs. Every app has its own API and is also an MCP server for assistants. With Enterprise, we build the integrations.

You take everything with you. Every app is real code, React, TypeScript and PostgreSQL, with its tests and spec: download it whenever you want and run it where you prefer.

With a free discovery call. Then we map the work of one department, build the first software with you on your real documents, and prepare the price together: on your people, your departments and the services you need.

One task to start

Start from one task that weighs on you.Watch it become software.

> What happens next

  1. 1You fill in one short form.
  2. 2An AI interview maps your work.
  3. 3You book a demo, or we call you.