Rails

Purpose

Soon you'll hire an agent the way you hire a contractor. You'll pick one built for your job, by someone who knows that job, and it will work inside the AI you already use. That market doesn't exist yet, and Rails is building toward it.

The gap

Someone who uses agents to the full gets thousands of times more done than someone who doesn't. It's the widest gap I've seen between two people doing the same job.

Engineers got there first because coding agents come with what sits around the model. They read the codebase and follow the team's written rules, and a person reviews what they ship. Everyone else got a chat box that knows nothing about their job.

The new IT department

Every job IT ever did has an agent version now: accounts, access, budgets, upgrades and outages. Today those jobs are scattered. Finance watches token spend and security watches identity, and nobody holds the whole picture. It's one job, and no company has a department for it yet.

IT owns the laptops because it hands them out. Rails provides the software and agents a team works in, so it can own the setup the same way. The company issues the agent with what it knows and the systems it connects to. Each person shapes the workflows on top, and those stay theirs. Nobody should have to learn what sits underneath.

The company what it knows, and connections to every system it runs on

Each person their own workflows: how they get their job done, theirs to keep

one agent one agent one agent
The company issues the agent with what it knows. Each person shapes the workflows on top.

Shared connective tissue

Every team gets a setup tailored to how it works. Underneath, the good ones share the same connective tissue: memory, connections, permissions and approvals. Putting a setup together is closer to a craft than a science.

We build what each team needs, custom software and screens included, on the best parts that already exist. As better parts ship, we swap them in, so every agent gets better each time the models do.

Your intelligence, in any home

Everyone is pitching a version of this. You'll hear it called company intelligence, an ontology, a context layer, a knowledge graph or a company brain. The idea underneath is the same: a business should own what it knows, in a form its agents can use, instead of renting it from whichever AI app it uses this year.

We agree, and we build the part that does the work. An ontology describes the business. An agent has to run it. So Rails keeps what each agent needs to do its job, its playbook, memory, tools and approval rules, in one place the company owns, and none of it depends on any one AI app.

Everyone will pick a preferred home, often an AI app they already pay for. A Rails agent runs in whichever home you pick, and Rails can be the most malleable home of them all. When your team changes apps or a stronger model arrives, the agent keeps everything.

Many agents, one of you

Agents work in parallel, and a person works in series. Past a handful of agents, attention becomes the limit, and each new agent only lengthens the line of things waiting on you.

So Rails keeps you in focus by default. What needs you lands in one inbox with a recommended answer on each item, and you work it when you choose. A short rule decides what may break in. A chief of staff agent fields everything else.

A managed agents department

No company has an agents department yet, so we become theirs.

  1. Teams that just grew

    We start with teams that recently raised or grew and aren't technical, in go-to-market and recruiting first, where results are easy to count.

  2. Built in weeks

    We find the jobs worth handing over and build the agents and the software around them in weeks.

  3. At your side

    We stay on a retainer tied to goals agreed up front, until each agent does its job better than the company's best person did.

  4. Open to anyone

    Later, anyone who knows a job well enough to teach it builds on Rails, and people hire the agent that fits their job.

Every build becomes a building block, so the next team gets there faster.

Built by running it

I run Rails on agents I built with Rails. A chief of staff agent knows every area of my work and life, and each area has an agent of its own. They've worked every day for six months, and each time they hit a gap, the fix becomes part of the platform.

BotKeeps my inbox and calendar under control, and sends every other request to the agent that owns it.
RailsBuilds Rails with me. It turns an idea into a shipped feature, and each morning tells me what moved.
FactoryKeeps the machines and model routing running so every project ships, and I never touch the infrastructure.
SenecaTurns my calls and voice notes into posts and long pieces in my own words.
RecruiterMy recruiting agency. It finds candidates and runs the outreach I approve.
HomeKeeps the apartment running, from the lights and media server to chores and household orders.
FrankMy personal CFO and the CFO for Rails. Bills and what's coming due sit in one place.
My agents and what each one does.

Agents can carry one person much further than before. Running the company this way holds me to building the best agent platform there is.

Why I'm building it

I learned to build with no mentor, from YouTube and my own trial and error. Coding agents closed the rest of that gap and made me feel like a superhero. I want every person to get that lift in their own work.

Agents will automate a lot of work. The fair version is the one where every person can carry what they know into an agent of their own, on tools they can trust. That's the version Rails is built for.

We're betting that every business will run on agents, and we're building the platform they run on.

Talk to us: alex@rails.so