Update 1November 2026
Launching Agent Rails
Rails is now a managed agents platform, and it sells a fractional managed agents department first.
What launched
Rails is a managed agents platform. Rails doesn't decide how work splits into agents. A company or a person does: one agent for a whole job, or one job split across several agents to lighten the mental load. Each agent has its own playbook, memory, tools and app, and Rails keeps it working as the models underneath change. When a new model gets better, every agent on Rails gets better with it.
On day one you get one place for everything that needs you: every agent, what it costs to run, what it's allowed to do and who it works for. Each one has a budget that pauses it at the limit, tools it has to be granted, keys it never sees and a record of every call it makes.
People keep working where they already are. The agent shows up inside Claude, ChatGPT or Grok with its playbook, memory, tools and app intact.
Why running agents is becoming a department of its own is in Agent management is the new IT department. What Rails commits to is in Our purpose.
How I run my own work on it
Rails is built with Rails, and I use it across my whole life. I align each day with a chief of staff agent that knows every area of my life, and each area has its own agent. They hand work to each other, and when something needs me it comes to one place.
My recruiting agent finds candidates and runs the outreach I approve. On a busy day, work is open across many agents at once.
Running this many agents has a cost, and I feel it. I call the goal agent zero: inbox zero for agent work, where nothing waits on me and what does need me sits at the top. Rails is learning to do that for everyone. More on both in Many agents, one of you and Agent zero.
The team
I'm full time on Rails, and a small team already wants in. I'd welcome the right cofounder, and I'm not waiting on one to move.
The start is people heavy. Each client takes real engineering up front, so early on the team grows at about three engineers to every seller, and the two converge as the building blocks settle into a platform. The first two hires are a strong engineer and a strong salesperson, and everyone who joins runs their own agents to move faster.
The cofounder I want is a deep technical owner who's bought into the mission: someone who knows how to make agents secure and how to turn them into reliable building blocks that work the same way every time. I want someone deeper on the engineering so my own days go to customers, learning their problems, turning them into the business and sharpening the pitch.
The business
Rails sells a service first: a fractional managed agents department. It starts with a free consult to find the problems a company most wants solved, then a lump-sum payment for the implementation, which includes building the custom software and UI each job needs, then a fractional retainer tied to goals, the way companies already hire a fractional CFO or CTO.
The retainer is tied to goals we agree with the company up front, like time to hire or pipeline. Rails never requires its own models. A company brings its own model keys and subscriptions, and Rails also runs agents on the labs' hosted runtimes and passes that runtime through at cost. That keeps out the headaches of the past year, from surprise token bills to pilots that never ship.
The wedge is teams that recently raised or expanded and aren't technical. We start with go-to-market and recruiting, because their outcomes are the easiest to measure, refine the building blocks for each vertical, and expand from there. The full model is in Rails sells a managed agents department first.
What's next
The first clients come through my own connections. It starts with people and moves to product, with technical people setting up the workspace until most people can do it themselves.
Further out: a marketplace where the best agents get listed and anyone can hire one, and a roll-up that buys small agencies to learn their businesses from the inside.
The next update comes in about a month.