> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tai42.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Babelfish

> The paid deterministic-flow product family built on the open platform: what it is and how it plugs in.

Babelfish is TAI42's paid product family for teams that need agent work to run
deterministically in production. It is built on the same open platform this site
documents, and it reaches a running server the same way any other plugin does.

<Note>
  Babelfish is proprietary and licensed commercially — it is not part of the
  Apache-2.0 platform and is not published to PyPI or listed in the
  [marketplace](/concepts/marketplace). Product details and pricing live at
  [tai42.ai/babelfish](https://tai42.ai/babelfish).
</Note>

## What it adds

Babelfish Flows ships as one installable plugin carrying two halves:

* **A flow engine.** Deterministic flows registered as ordinary
  [tools](/concepts/tools-and-extensions) through the public contract — run a
  flow, step it, read its state, and abort it. Because they are tools, everything
  the platform already does to a tool applies: access control, backends,
  schedules, and tracing.
* **A flow editor in the Studio.** A front-end bundle the runtime serves to the
  [Studio](/studio) through its integrity-pinned import map, contributing a
  top-level **Flows** page and its nav entry.

A saved flow is a versioned [preset](/concepts/presets) with the graph carried in
the preset's fixed arguments, so flows version, diff, and roll back through the
[versioning spine](/concepts/versioning-spine) like everything else.

## How it plugs in

It is wired like any other plugin — a tools entry for the engine, a
`studio_plugins` entry for the editor bundle, and the host routers the flow UI
rides:

```yaml manifest.yml theme={null}
tools:
  - title: babelfish-flows
    module: tai42_babelfish_flows.tools.tools
studio_plugins:
  - tai42_babelfish_flows
routers_modules:
  - tai42_skeleton.routers.tools
  - tai42_skeleton.routers.tool_runs
  - tai42_skeleton.routers.presets
  - tai42_skeleton.routers.plugins
```

The `routers_modules` order is load-bearing: `tai42_skeleton.routers.plugins`
must be last, because its SPA catch-all matches any path and routers register in
import order.

The bundle is committed inside the distribution, so installing it needs no
JavaScript toolchain on the server. The plugin adds no HTTP route of its own and
claims no backend — see [Studio plugins](/studio/plugins) for how the Studio
loads a plugin bundle and pins it.

## See also

* [Babelfish on tai42.ai](https://tai42.ai/babelfish) — the product, its pricing, and its terms.
* [Studio plugins](/studio/plugins) — how a plugin contributes a Studio page.
* [Presets](/concepts/presets) — the versioned wrap a saved flow becomes.