Assembly Line
Assembly Line is a method for running SOP-driven work, the repeatable procedures people do at a computer, as an assembly line: an AI agent designs the line once, and stations that are mostly plain code run it, with no person at any station. These docs cover its reference implementation.
The reference implementation runs work as lines of stations. Each station runs a few steps of your own Node.js code on your own worker. The Orchestrator schedules station runs and records every run as a work record. Work moves between stations as workpieces: folders that pass through input, doing, output and failed bins, so you can always see where each piece of work is.
It's for anyone who runs repeatable work through an AI agent: invoice intake, email capture, transcription, a sync between two systems.
Assembly Line is in Beta. Pricing is usage-based with no per-seat plans; rates aren't published yet. Running steps on your machine needs no account.
The pieces
| Piece | What it is | Where |
|---|---|---|
| Orchestrator | Stores your lines and stations, runs them on a schedule or on demand, and records every run | orchestrator.finopsbricks.com |
| Worker repo | Your Node.js project: steps under src/steps/, station files under .orchestrator/ | Start from worker-template (Apache-2.0) |
| lib-worker | The library a worker is built on: defineStep(), the polling loop, workpiece helpers | finopsbricks/lib-worker |
| fob-worker | CLI that runs a step locally, shows what's in each bin, and runs the worker under pm2 | npm install -g @finopsbricks/fob-worker (Apache-2.0) |
| fob-orc | CLI that pushes station and line definitions to the Orchestrator and triggers runs | npm install -g @finopsbricks/fob-orc (Apache-2.0) |
fob-worker reads and writes files in your worker repo only; it never calls the Orchestrator. fob-orc does that.
How a run works
- The Orchestrator starts a station run, on a schedule or when you trigger it, and creates a work record.
- Your worker polls the Orchestrator, receives the station's first step, and runs your code for it.
- The worker reports the step's output. The Orchestrator queues the next step. Each step can read the outputs of the steps before it.
- When the last step finishes, the work record is complete, with any report and documents your steps attached.
Your code, your data and your credentials for other systems stay on the worker. The Orchestrator never sees workpieces; it only records runs.
Next
- Quickstart: a step running on your machine in about 15 minutes, no account needed.
- Concepts: lines, stations, steps, work records, workpieces and bins.
- Use with AI agents: let a coding agent write, run and debug steps.
- Full reference: finopsbricks.com/docs/workers.