We build agent systems that do real work, then we run them.

NimbleCo is the consulting practice inside Cyborg Garden. The research and the open source live there. This is where it gets built for someone in particular.

What gets installed

Your own instance, on your keys and your infrastructure. We run our own ventures on the same tooling, so you can read it before you hire us.

Control plane

Swarm Map

Decides which agent can do what, and where.

Operator

ASG

Runs a unit of work from framing to handoff, then stops, because the call at the end is a human's.

Both are public. So is the science we run on them.

Then we operate it

Agents handle the requests and surface only the decisions.

  1. Requests come in

    Agents pick them up.

  2. Most stop there

    Most inbound work never reaches a person.

  3. The rest arrives framed

    With the options and the recommendation attached.

  4. You decide

    The agents stop here.

That is the product: your attention, spent on the calls only you can make. You are not buying meetings.

How it is priced

Hourly billing has a bug in it. Make the harness twice as good and the work takes half as long, so doing the job well costs us money. We price four things separately instead.

Installation
Fixed project price
The work has an end, so the price does too.
Operation
Monthly retainer on surface area
Surface area means how many agents, integrations, scheduled jobs, repositories and hosts we keep alive. Working faster cannot game it, which makes it the honest measure.
Escalations
Monthly budget measured in decisions, not hours
You buy access to a judgment queue that a machine has already filtered, and you can see how full it is before the month ends.
Tokens and infrastructure
Passed through at cost
We do not absorb them, and we do not bury them inside a rate where you cannot see them.

What we leave with

Every consultant leaves with something. Usually nobody writes down what.

You keep the substance. We leave with the shape.

Yours. Your data, your names and your particulars never travel.

Ours. Patterns we learn get generalised into our own templates.

The gate

That boundary is a gate, not a promise. It reads every file in the repository before anything leaves, and it fails closed: a check that cannot finish blocks the release instead of waving it through. You can watch it run on one of our public repositories.

If you want nothing generalised at all, that is a priced option.

Where this does not work

If your bottleneck is a decision only one person can make, a fleet of agents moves that bottleneck around and never removes it. You will hear that at the scoping call, not three months in.

If we stop working together, you keep the instance and it keeps running, on your keys and your infrastructure. It runs with or without us.

Bring the work you gave up on automating.

Watch the gate run.