Skip to main content
Maquina Currently in private beta

The harness already composed for Rails.

Fragua lets a team run, watch, and control many AI agents building Rails apps — with full visibility into the work, the cost, and how the agents behave. It begins with one developer turning an idea into a shipped app, and becomes indispensable when a team is shipping across many products at once.

BYOK · billed to your account · Rails 8.1 + Hotwire · Runs on your host · never proxied
Why Fragua

Everything a control plane promises — plus the two things that matter on your own budget.

Quality, control, and consistency are table stakes — the whole category claims them. What changes the math when agents run on your own keys is knowing what they cost and how they behaved. Fragua is opinionated, Rails-deep, and self-serve: you own the repo and the keys, and we never sit in the middle.

Table stakes — the whole category claims these
Quality

Agents fluent in the Rails 8.1 craft — Hotwire, Solid Queue, Minitest, the One Person Framework — so the code reads like your team wrote it.

Control

Your architect approves the plan in plain language before any agent touches the codebase. Agents don't make unreviewed architectural decisions.

Consistency

Every workspace runs the same opinionated lifecycle, so two products built months apart still look like one team built them.

Where Fragua is different — when agents run on your budget and keys
Cost control

Every token rolls up per run, workspace, account, and month. BYOK, billed straight to your provider — you always know what your agents cost, and we can't see your bill.

Agent observability

A durable audit trail of every run: what the agent touched, which model and reasoning effort it used, why it failed, whether it stayed in bounds.

The lifecycle

Four phases. One workspace. Zero context loss.

From a one-line product idea to a merged pull request. Each phase produces durable artifacts that become context for everything that follows.

01
Research

Tell Fragua a one-line idea. It studies similar apps and writes a synthesis you can edit and approve.

02
Plan

From the research, Fragua drafts the MVP plan that defines what to build first. Brand guide and technical guide ship as separate phases.

03
Spec

Define features as structured specs. Each one decomposes into a task list ready for an agent to execute.

04
Execute

Agents implement tasks on a feature branch and open a pull request. Watch the work happen live.

Every artifact persists. Every later phase has access to every earlier one.

Knowledge Base

Your references, in every agent's context.

Beyond the artifacts each phase produces, every workspace has a Knowledge Base. Upload your own reference material and the spec and execution agents read it as context — design docs, API contracts, house conventions. The agents build against your references, not just the generated plan.

PDF Markdown HTML Text Images

Up to 10 MB per file · 1 GB per workspace · staged into the agent's working directory at run time

Institutional memory

The Knowledge Base, the persisted phase artifacts, and the durable run history live in the workspace — not in someone's head. Onboarding, handoffs, and people leaving don't erase the context the agents work from.

Knowledge Base · acme-crm-rebuild
api-contract.md
Markdown 24 KB
design-system.pdf
PDF 1.2 MB
erd-diagram.png
Image 340 KB
house-conventions.md
Markdown 8 KB
4 documents · 1.6 MB of 1 GB
For Rails developers, by Rails developers

Generic agents don't know your codebase. Fragua does.

Fragua's agents ship pre-loaded with the Rails 8.1 vocabulary. Hotwire for the front end. Solid Queue for async work. Rich domain models with concerns. The One Person Framework philosophy from Rails as the default — building like one developer can ship the whole thing.

When the agent reads your code, it knows what a Stimulus controller is. When it writes a test, it writes Minitest with fixtures. When it opens a pull request, it follows the conventions your team already lives by.

  • Built-in awareness of maquina_components for views
  • Rails MCP Server integration for runtime context
  • Per-feature git worktrees for parallel work
  • Pull requests opened through your host's own GitHub access
Run #14 · live
42s · $0.18
system init · session 9c0…7e2 · model claude-sonnet-4-6
assistant Reading the Invoice model to understand the status enum structure.
assistant tool_use: Read(file_path: "app/models/invoice.rb")
user tool_result: 31 lines · enum :status with draft/sent/paid defined
assistant tool_use: Edit(file_path: "app/models/invoice.rb", …)
user tool_result: file edited · 5 lines added
assistant tool_use: Bash("bin/rails test test/models/invoice_test.rb")
user tool_result: 14 runs, 28 assertions, 0 failures
result subtype: success · 42s · $0.18 · 14.2k in · 9.6k out · 3.1k cache
One turn of a Fragua run · top-level event on the left, content below
Observability

One spine, three axes: the work, the cost, the behavior.

The deepest-built part of Fragua. For a solo dev watching one agent it's a nicety; for a team running many agents across many products, it's the whole job.

Work

Live timelines, durable resumable runs, every turn a row in the event log. Watch the work as the agent produces it.

Cost

Token usage rolled up per run, workspace, account, and month — BYOK, billed straight to your provider.

Behavior

A durable audit trail: run type, model and reasoning effort, failure reasons, watchdog and restart.

Observability · Work

Watch the work happen.

The durable events from each agent turn land in the database one row at a time — assistant text, mid-interview questions, terminal artifacts. The browser sees a live timeline as the agent produces it. Token usage and cost are written per turn into their own table. Cancel signals the runner and takes effect within five seconds.

fragua.app/workspaces/acme-crm-rebuild/agent_runs/14
A live Fragua agent run: streaming assistant text, mid-interview questions, and per-turn cost rendered as the agent produces them.
Streaming, not polling

Turbo Streams broadcasts each turn as the agent produces it. The browser never asks; the server pushes.

Durable, not chatty

The database keeps what matters — assistant text, questions, terminal artifacts, per-turn cost. Tool calls and intermediate state stay in the runner stream.

Resumable across sessions

Close the browser. Come back tomorrow. The run is still going. The event log is still complete.

Observability · Cost

You bring your AI key. We bring the receipts.

Fragua never proxies your AI calls. Every token your agents consume is billed directly to the provider your key belongs to. We can't see your billing or charge you for usage.

What we do is parse the usage events from every run and roll them up — per AgentRun, per Workspace, per Account, per month. Finance knows where every dollar went.

At launch Fragua runs on Anthropic Claude via Claude Code. Other AI services and platforms plug in as they ship.

Your key, your host
BYOK — never stored by Fragua
Never proxied
Direct to your provider
Roll-ups
Run · Workspace · Account · Month
Per-phase metering
Model + reasoning effort, every turn
This month · Brújula
April 2026
$0.00
vs $5.27 last month
0k input · 0k output · 0k cache
By workspace
acme-crm-rebuild
$1.42
bluebird-api-v3
$1.18
turesto
$0.94
haab
$0.78
The foundation

Rails 8.1. SQLite. Solid Queue. Hotwire.

Fragua is built on the Maquina stack — vanilla Rails with the One Person Framework philosophy. The same conventions you'd want in a project Fragua builds for you.

Rails 8.1

The framework, modern and complete.

SQLite + WAL

Five embedded databases, one server.

Solid Queue

Database-backed async jobs.

Hotwire

Turbo + Stimulus, server-driven UI.

Clave auth

Passwordless sign-in via email codes.

GitHub via gh

Pushes and PRs through your host's access.

Kamal 2

How we deploy Fragua to our infrastructure.

Litestream → R2

Continuous backup with ~1s RPO.

Pricing

Flat per-account. BYOK. No surprises.

You pay Fragua a flat monthly fee for the platform. You pay your AI provider for tokens. We never sit between the two.

Solo
$29 / month

For independent Rails developers and personal projects.

  • 1 user · unlimited workspaces
  • BYOK — your AI spend, billed to you
  • Full cost dashboard
  • Per-feature git worktrees
Request access

Currently free during private beta · Pricing begins 30 days after public launch with email notice

Waitlist open · private beta

Tell us what you're building.

Fragua is in private beta with a small group of teams and solo builders. We're not opening seats on a schedule — join the waitlist and we'll reach out when there's room for the work you're describing.

30 chars min

A human reads every entry. When a seat opens, the sign-in link arrives by email — no timeline yet.