Software factories you control

Zeeli turns a goal into tasks and runs them through a planner, workers and reviewers on your own machines and cloud servers. The agents do the work; you keep the decisions that matter, from any browser or phone.

Start a factoryDownload the desktop app

Bring your own agent subscriptions and machines. Twelve coding agents built in.

StorefrontAutopilot1 decision is waiting on you

Goal One-click reorder for returning customers

Plan1

Spec the reorder button

Plannerzeeli-cloud-01

Build2

Reorder endpoint and tests

Buildermac-studio

Reorder button on past orders

Builderbuild-02

Review1

Reorder confirmation email

QAbuild-01

Ship1

Merge #481 into main?

Saved carts survive sign-in

2 reviewers approved this commit. Checks passed.

This factory is live. Approve the merge and the next task moves up.

A factory is a file you can read

Write a blueprint in YAML: the seats, what each stage does, who has to review, and how work ships. Start from Coding, Content studio, Research desk or Support triage, and keep it in your repository like any other code.

  • Stages, not job titles

    Planners, workers, reviewers and advisors. A seat’s instructions are its personality; its skills and MCP servers are its tools.

  • Local and cloud agents in one crew

    Put the builder on your Mac and the reviewers on an Ubuntu server. One blueprint, any machines.

  • Every handoff is a commit

    Code, articles and reports land as commits on a task branch, so review, history and undo work the same way.

blueprints/coding.yaml
# Coding: a planner, a builder, and two reviewers.blueprint: 1id: codingname: Codingdescription: Plan, build, review, and merge code changes.autonomy: autopilotagents:  - id: planner    stage: planner    name: Planner  - id: builder    stage: worker    name: Builder  - id: qa    stage: reviewer    name: QA  - id: security    stage: reviewer    name: Security reviewreview:  required: [qa, security]

Decide where the line stops

Choose how much a factory does on its own. Every gate you keep lands in your inbox in blue; everything else moves without you.

  • SpecYou approve
  • Task breakdownYou approve
  • Start buildingAutomatic
  • ReviewAutomatic
  • MergeAutomatic
  • Risky mergeYou approve
  • Add a seatYou approve

Nothing merges until every reviewer has approved the same commit, the checks are green and nothing conflicts. Changes to migrations, auth, CI or infrastructure count as risky.

Your machines. Any agent.

A node is a computer that runs your agents: your Mac with the desktop app, or an Ubuntu server you add with one command. Repositories and agent workspaces stay on those machines; zeeli.dev only coordinates the work.

zeeli.dev· Factory

  • mac-studioOnline

    macOS · desktop app

    • Claude Code
    • Codex
    • Cursor
  • build-01Online

    Ubuntu 24.04 · node

    • Codex
    • Gemini CLI
    • OpenCode
  • build-02Online

    Ubuntu 22.04 · node

    • Claude Code
    • Qwen Code
  • Claude Code
  • Codex
  • Gemini CLI
  • Cursor
  • Copilot
  • OpenCode
  • Grok
  • Factory Droid
  • Kimi Code
  • Qwen Code
  • Pi
  • Qoder

Twelve agents built in, each on its own structured runtime. Your Claude, ChatGPT and Gemini plans keep working.

Work starts on its own and stays in budget

  • On a schedule

    Run a goal every night or every Monday with a cron schedule.

  • From GitHub

    Start work when an issue opens or a pull request changes.

  • From any webhook

    Point your error tracker, CI or an internal tool at a factory’s webhook.

  • A daily token budget

    The factory stops taking work at its budget and warns you at 85%.

  • Take over any task

    Stop the agent, work in its thread yourself, then hand it back.

  • A read-only link

    Share a factory’s seats, goals and runs with someone who has no access to anything else.

When you want to drive, open the desktop app

The same agents in a native window on macOS, Windows and Linux. Every thread is kept, each one can get its own worktree, diffs and pull requests stay in the app, and the only blue on screen is work waiting on you.

Download for macOSOther platforms
Needs you 1Running 4
Fix flaky checkout test

The checkout test fails about one run in five on CI. Find out why and fix it.

  • Read 4 files
  • Edited checkout.test.ts+12−4

Codex wants to run a command

pnpm vitest run checkout --repeat 20
Ask Codex anything
This window is live. Answer the blue request and the next agent will ask.

Answer from your phone

The inbox comes with you. Approve a merge or answer an agent from the web app or a paired phone, and the work keeps moving on your machines.

Open the web app ↗

Questions teams ask first

What is a node?
A computer that runs agents for your account: your Mac or PC with the desktop app, or an Ubuntu 22.04 or 24.04 server you add with a one-use install command.
Does my code leave my machine?
Agents run on your computer or on nodes you own and talk to their providers directly. Repositories and agent workspaces stay on those machines; your account and Factory state live at zeeli.dev.
Which agents does it support?
Claude Code, Codex, Gemini CLI, Cursor, Copilot, OpenCode, Grok, Factory Droid, Kimi Code, Qwen Code, Pi and Qoder are built in. Any other agent that speaks the Agent Client Protocol can be added from the ACP Registry or by its command.
Can we host the control plane ourselves?
Yes. The website, accounts, Factory and the relay run from one Docker Compose stack on servers you control.

Start your first factory

Create an account, connect a machine and pick a blueprint. The desktop app connects your computer from its Factory view.

Start a factory

Desktop app downloads