Skip to content
A note from the creator

Why I built
FlowRail.

I love what coding agents make possible. I wanted a way to keep building while knowing whether the code still respects the plan.

Anshuman Bhartiya, creator of FlowRail
Anshuman BhartiyaSecurity engineer. Builder. FlowRail’s creator.More about me
01 / The shift

The way I build changed.

I’m Anshuman. I’ve spent more than a decade working in security, and more than a year experimenting with AI. Claude Code and Codex have become a big part of how I build.

More and more, building starts with a conversation. I describe an idea, work through the design with an agent, and agree on what the result should do. Those decisions often become a design specification: the plan we build from.

As the models improve, I can make more with them. But I’m also further from writing and reviewing every line myself. The volume of generated code makes one question harder to ignore.

Does the code actually respect what we agreed to build?

02 / The gap

A working app isn’t the whole story.

A plan might say that customers can only see their own invoices, or that a private report must stay inside an organization. An app can appear to work while the code misses one of those boundaries.

Coding agents have useful built-in safeguards. I wanted an additional check tied to my application’s security requirements, with evidence I could follow as the implementation changed.

03 / The idea

Put the guardrails where the work happens.

Agentic development gives us new ways to do that: skills to guide the agent, MCP tools to connect it to services, and hooks to check an action before it happens.

FlowRail uses those building blocks to connect the design to the code. It reviews your specification, turns supported security requirements into rules, and checks proposed file writes against them.

When a supported write violates a rule, FlowRail can block it before the code is saved. The agent gets the finding and can make a correction. The dashboard connects the requirement, the finding and the next check, so you can see what changed and what still needs attention.

That’s the kind of tool I wanted: one that works with the agent and gives the person building something a way to verify its work.

04 / The name

Flow state meets guardrails.

FlowRail brings the two together. Stay absorbed in creating, with security decisions still being checked as your idea becomes software.

Our weaver bird gives that idea a shape. The thread connects what you decided to what gets built. FlowRail helps keep that connection visible through the checks and their evidence.

I’m starting with a small invited pilot for individual builders. Their real projects will help me learn what FlowRail catches, what it misses, and how to make the experience smoother.

Keep building,Anshumananshuman.ai
From the idea to the product

See FlowRail at work.

Follow a design requirement into a blocked write, a correction and the evidence behind it.

Watch the walkthroughs Request pilot access