Always-on agents that get smarter over time. Open source, MIT.
SERVICES AGENT OPERATIONS
We run a product studio on a roster of agents. One person does the deciding and the agents do a great deal of the work. Agent Operations is that same setup, built inside your company and handed over to your people.
The work written down before any of it is automated.
We sit with the people doing the job and write down how the work actually happens, not how the handbook says it does. That document is the thing an agent can be given. A fair amount of the value lands here, before a single agent is running.
Named agents with a job each.
Every agent is one file: a name, a model, the tools it may call, and the instructions it works from. You can read it, edit it, and hand it to someone new on their first day. There is no console to log into and no copy of your work on anyone else’s servers.
Running, watched, and kept current.
The gateway on a machine you control, provider keys wherever you already keep secrets, and sessions that survive a restart. We stand it up, we keep it patched, and we are the ones paged when it stops.
Handover, not dependency.
Your people learn to write an agent, widen a policy, and read back what an agent did and why. The engagement is built to end. If you keep us on afterwards it should be because you want to, not because nobody else can touch it.
01
Time with the people doing the job. We come out with the processes written down and a short list of what is worth handing over first, which is rarely the thing you expected.
02
We write the agents, wire up the tools they need, and set the policy. You watch the first runs and approve what each one may touch before it touches anything.
03
Your team drives, we stay reachable while it beds in. Then we are done, unless you want us on a retainer.
One engagement, with an end date.
Processes documented, roster built, infrastructure running, team trained. Priced as a project, because that is what it is.
A retainer afterwards, if you want one.
New agents as the work changes, upgrades, policy reviews, and someone to call the first time an agent does something surprising. Month to month.
A consultancy you cannot fire is not a consultancy. Everything we build lives on your side of the line.
Plain markdown in your own repository. Every agent we write is yours to read, change, or delete.
Your hardware, your provider account, your keys. Nothing routes through us and there is no bill from us to keep it running.
Stratus Agent is MIT licensed and public. If we stopped existing tomorrow, your roster would not notice.
That conversation is the first half of the work, and it is free.