Ship AI workflows from your editor

Git-native, type-safe, production-ready

$ npm install -g @eai-tools/cli

Read the docs

eai workspace — no-code-builder

object-types.tstenants.ts

// src/eai.config/object-types.ts

export const Project = defineObjectType({

name: 'Project',

tenant: 'no-code-builder',

properties: [

{ name: 'name', type: 'text' },

{ name: 'status', type: 'select' },

})

Workflows/Procurement intake

Request

Approval

Sourcing

Submit

Vendor

Acme Pty Ltd

Amount

$48,000

Approver

Finance lead

BackPublish

Trusted by leading organisations

Building AI workflows from scratch is a tax.

You rebuild the same plumbing

Retrieval, validation, auth, rate limits, audit trails - every new workflow reimplements the same boilerplate from scratch.

Governance ships late

Guardrails and policy get retrofitted after launch. By then, the patterns are already wrong.

Workflows don’t leave engineering

Ops and analysts can’t touch what you built. Every change is a PR - even the trivial ones.

How CLI fixes it

Start on the platform

Use the EAI block library, design system, and data governance layer out of the box. All the primitives Builder uses — accessed from your editor.

Start on the platform

Use the EAI block library, design system, and data governance layer out of the box. All the primitives Builder uses — accessed from your editor.

How it works

Use our blocks

Declaratively compose EAI blocks - ingestion, retrieval, validation, approvals, AI steps - as type-safe TypeScript definitions.

eai — zsh

Bring your ERP

Connect SAP, NetSuite, Dynamics, Oracle, or any SaaS and database. Custom connectors authored in the CLI ship alongside your workflows.

eai — zsh

Inherit the design system

Workflow UIs inherit EAI styling by default. Override tokens or ship fully custom components when you need to.

eai — zsh

Govern by default, extend anywhere

Policies, PII handling, and audit are platform-level. Extend with custom guardrails via the SDK when the defaults aren’t enough.

eai — zsh

Measure and iterate

Every run emits traces, metrics, and eval hooks. Bring your own APM or use EAI dashboards. Iterate with confidence.

eai — zsh

A single plane of glass

DAISY integrates with your existing systems of record.

Planning Portal

Frequently asked questions

What languages does the CLI support?

Workflow definitions are declarative (TypeScript today, Python on the roadmap). Custom blocks can be authored in any language that targets the block ABI.

Can CLI workflows be edited in Builder?

Yes - anything you build in CLI shows up in Builder for business users to run, inspect, or extend within the guardrails you define.

How is this different from Temporal / Airflow / Dagster?

Configurator CLI is AI-native. Blocks carry data contracts, prompt versioning, and eval hooks as first-class primitives, not things you bolt on.

Is the CLI open source?

The block SDK and several core blocks are open source. The runtime and registry are managed by EAI. Ask us for the current licensing details.

Sign up for a CLI demo

Grab a slot and we’ll walk you through CLI live with a workflow from your domain.

Stay up to date

Launch news and product updates from EAI — straight to your inbox.

We’ll email you about EAI product updates and launches. Unsubscribe anytime.