AgentFactory

AgentFactory

Build software with a crew of 25 agents.

A multi-agent development system where specialized agents plan, design, build, test, and ship. They coordinate over a shared message bus, and you see every step in real time.

See how it works

A crew of 25 agents that ships software.

DevNimbus mascot

The Harness

Not one AI. A specialized team.

Each agent is a specialist with a defined role. They pass work over a shared bus and pick up tasks from their inbox, so you get the judgment of a full team instead of one generalist stretched thin.

  • orchestrator

    Routes work across the crew

    studio

  • planner

    Turns goals into architecture

    studio/planning

  • product-owner

    Owns scope and acceptance

    studio/planning

  • task-manager

    Splits work into tasks

    studio/planning

  • project-manager

    Tracks progress and unblocks

    studio/planning

  • eval

    Scores quality and performance

    studio/quality

  • testing

    Writes and runs tests

    studio/quality

  • test-updater

    Keeps tests aligned with code

    studio/quality

  • cleanup-qa

    Prunes dead code and fixtures

    studio/quality

  • auth

    Handles identity and access

    studio/operations

  • copywriter

    Writes copy and release notes

    studio/content

  • documentation

    Keeps docs in sync with code

    studio/content

Runtimes

The right model for each job.

Not every task wants the same model. Assign a runtime per agent — careful code edits, long-context reading, or natural conversation — and swap them out as the frontier moves.

  • Claude Code

    Careful code edits

    The workhorse for code — careful edits, tight reasoning, steady hands.

    claude-code

  • Kimi Code

    Long-context reasoning

    The long-context alternative for reading large codebases and specs in one pass.

    kimi-code

  • Pi

    Voice and dialogue

    The conversational runtime — natural turn-by-turn voice and chat.

    pi

Integrations

Plugs into the tools you already use.

The agents work against the same stack you already trust. Each tool stays first-class, with a thin MCP adapter handling the wiring so nothing gets re-invented.

  • Supabase

    Postgres, auth, and storage

  • Cloudflare

    Workers, DNS, and R2

  • Vercel

    Deploys and edge runtime

  • GitHub

    Source control and pull requests

  • Playwright

    End-to-end browser tests

  • Next.js

    App Router framework

  • Tailwind

    Utility-first styling

  • shadcn/ui

    Composable UI primitives

Pipelines

Declare the workflow. Agents do the rest.

A pipeline is a DAG of agents. Describe the nodes and edges in config; the scheduler fans out parallel branches, waits on joins, and retries on its own.

PlanplannerDesignui-designerCopycopywriterBuildfrontendEvaluateevalDeployinfrastructure

Observability

Every step, visible in real time.

Every agent streams events as work happens. Follow the run line by line, or scrub back through the history — the system keeps going either way.

  • Server-sent events, one line at a time
  • Per-agent timeline with timestamps
  • Replayable from any point in the run
  • Warnings surface without drowning the log

Voice

Talk to your team of agents.

Speak to the crew the way you'd speak to a teammate. Multilingual, turn-by-turn, with local Kokoro TTS for common languages and a cloud fallback when you need a rarer one.

  1. You

    How's the checkout-v2 pipeline doing?

  2. Nimbus

    Eight of nine tasks landed. Eval flagged INP on /checkout — frontend already deferred analytics and it's down to 142ms.

  3. You

    Great. Push a preview when it's ready.

  4. Nimbus

    Infra's deploying now. I'll ping you with the URL.

  • Turn-by-turn conversation, not keyword commands
  • Eight languages via local TTS, more via cloud
  • Per-device input and output control
  • Hands-free while you keep working

DevNimbus

The friendly front door.

DevNimbus is the chat layer on top of the harness — it remembers context across sessions, nudges you when work lands, and explains what's happening in plain language.

DevNimbus mascot
  • Persistent memory across sessions
  • Proactive updates when tasks finish
  • Plain-language answers, jargon on request
  • One place to ask questions and kick off work
Get in touch

DevNimbus

Front door for the harness

today

  1. Did the mobile build go out?

  2. Yes — preview promoted at 14:02. Eval scored a11y 98, perf 96.

  3. Set up a walkthrough for tomorrow with the design crew.

  4. Done. Calendar invite sent to four people, agenda attached.

  5. Anything I should look at before EOD?

  6. AF-17 is sliding past ETA. Want me to reassign or extend?

Contact

Want to see it running on your project?

Send a short note about what you're building. We'll set up a walkthrough on a repo of yours, or demo one of ours. No sales pitch — just the system.

Request a walkthrough

hello@studio306.nl

  • A 20-minute walkthrough
  • Sample pipelines you can adapt
  • Answers from the team that built it