ATAILA Newsroom · New reference · Budapest · 2026-08-19

A “fork” in a day — from OpenChef to OpenChem

We have added a new live product to our references: openchem.hu, a bilingual collection of classic chemistry demonstration experiments. It went from idea to production in hours, not weeks — because it started from OpenChef, our AI kitchen.

Strictly speaking, it is not even a fork

A fork usually means copying the code, watching the copy drift away from its parent, and doing double maintenance from that day on. That is not what happened here. OpenChef and OpenChem run from one codebase and the same container image; a brand toggle decides which of the two gets served. Not a single line had to be branched, and no code was copied.

What we actually wrote was only the delta: a new brand profile, the chemistry vocabulary, age and safety labels, the legal text, and ten experiments in two languages. Everything underneath — the application, the pipeline, the environments, the operations — already existed and stayed shared. That is exactly why it could be this fast, and why the second product does not become a second maintenance burden.

What it took — three pieces of the platform

1. Factory: the landing zone

ATAILA Factory provisioned the landing zone on our own hardware: separate dev, test and production environments, a database, object storage, secrets management, DNS, certificates, a container namespace and the network rules around it.

2. Coder: the application itself

The application, the API, the database schema, the admin portal and the website were written by ATAILA Coder — an on-prem agent running open-weight models on our own GPUs. No public AI service was involved at any point.

3. Release Manager: the road to production

ATAILA Release Manager versioned the container image and promoted it through the environments into production — the same governed, human-approved path every customer project uses.

Why this is the reference that matters

Any agency can show you one finished project. For a company with a roadmap, the right question is the second one: what does the next product cost, once the first one is live? On most stacks the answer is “roughly the same again” — a new repository, a new pipeline, new environments, new operations, one more thing to keep patched.

Here the answer was hours. If you have a second brand, a second market, a white-labelled version for a partner, or the same workflow needed by another department — that gap alone is the argument for putting the first product on a platform rather than in a project folder.

Labelled honestly, as always

The experiment descriptions were assembled by a language model from long-established classic demonstrations — it invented no new chemistry — and they have not been independently expert-reviewed. The illustrations are AI-generated, not laboratory photographs. Every experiment is presented for education, with age guidance, adult supervision and a clear disclaimer. No public AI service was touched, and nothing left our own racks.

The site says all of this itself, up front. A reference project that fibs about the small things is worthless as a reference — which is the same reason our AI kitchen tells you that none of its dishes ever existed.

See it live, then bring yours

OpenChem runs live at openchem.hu — and all our references are in one place. If there is a second product on your roadmap — or even the first one is still waiting — let’s talk about what this would mean for your workflow.

Bring us your workflow →