Features

Rebuild the legacy app. Prove it behaves the same. Never fall behind again.

Fabrica learns how your system really behaves from its traffic, data, instrumentation and code. An agent team your engineers direct rebuilds it, and users and data move across only when the evidence says it is safe.

CommandProductBuildCodeGraphTrafficLogsDataReleaseAgentsReports
Projects › Acme Billing › CommandLive · 00:00
Foremanrunning · auto modePipeline
DomainCaptureLockEngineerAttestReleaseDataDone
billing
customers
reports
Talk to Foreman
BoardnowOpen board
Agents0 running
Metrics
$0.00Spend today
Datalegacy → new
Snapshot pendingWrites: legacy
Attestation
—
waiting for Attest
Trafficobserve proxyTraffic map
0
Legacy requests
0
New requests
0 %
Served by new
legacynew stack

Evidence from production, not guesses from code

Behaviour is recorded from the running system, so the specification covers what your users actually do.

Proof before anyone switches

Old and new run on the same workload, and every difference is traced to the request, record and field.

A way back at every step

Users and data move gradually. Switching back is a routing change, not a redeploy.

Your estate

Built for the monoliths that run your business

Web and app monoliths and core systems for mid-market and enterprise teams. Fabrica learns each system from its traffic, jobs, data and source code, so an old framework or thin documentation doesn't hold it back.

.NETJavaRubyPHPC++COBOLAssemblyMore on request

Capture

Learn what the system really does

Fabrica sits beside the running application and records requests, logs, background jobs, queries and errors. Routes are ranked by real use, and paths nobody has exercised show up as gaps, not assumptions.

  • An observe proxy on live traffic, tagged by release
  • Read-only schema analysis and report and ETL lineage
  • Logs joined to the request that caused them
  • Coverage measured against a threshold you agree
CommandProductBuildCodeGraphTrafficLogsDataReleaseAgentsReports
Projects › Attest Demo 2 › Traffic › Map
24 routes, 5 carry 80 % of traffic
404,983 requests over the last 7 days
Requests per hourUTC, every route
Routesranked by requests
RouteShareRequests ↓Errorsp95DomainParity
GET /todos46.3 %187,464<0.1 %28 msTodosnot attested
GET /todos/:id24.2 %98,1860 %4 msTodosnot attested
POST /todos/:id4.6 %18,546<0.1 %4 msTodosnot attested
GET /login4.1 %16,5080.2 %2 msAccountsofferable
GET /todos/new3.6 %14,6200 %3 msTodosnot attested
POST /todos3.6 %14,6170 %5 msTodosnot attested
POST /todos/:id/done2.8 %11,234<0.1 %23 msTodosnot attested
POST /login2.7 %10,8060.3 %428 msAccountsfailing
POST /logout2.6 %10,7030 %2 msAccountsofferable
GET /stats2.2 %8,7190 %3 msStats & reportsnot attested
Foremanrunning · auto modePipeline
DomainCaptureLockEngineerAttestReleaseDataDone
todos
reporting
accounts
▣ fab-q18f · Created by the business analyst agent
Todos
Proposed by business analyst
Creating, editing, completing, reopening, deleting and exporting a user's todos, including the rules and the completion side effects.
DomainMedium confidenceReady to build
CoveredMetAll routes with traffic (~96% of requests) and its tables are members.
ObservedMetBaseline lines flow and write counts confirm todos writes.
BoundedMetWrites only todos; notifications is owned by the notifications domain.
No blocking questionsPartlyPOST /todos/:id is likely the Rack method override of PATCH/DELETE; it does not change what gets built.
StableMetMembers unchanged across the last runs.

Domains

Split into domains, the Domain-Driven Design way

Fabrica divides the application into domains, each a bounded context with its own routes, tables and code.

  • Boundaries proposed by the business analyst from the evidence
  • A confidence rating for every domain
  • Checked covered, observed, bounded and stable before it is built
  • Dependencies between domains become explicit interfaces

Logs by request

Map out system behaviour from the user action to the database

Every log line tied to the request that caused it. Follow one click from the route, through the SQL it ran, to the email it sent.

  • Every request gets an id from the observe proxy
  • Passed on in the X-Request-Id header
  • App, database and job logs joined to the request that caused them
CommandProductBuildCodeGraphTrafficLogsDataReleaseAgentsReports
Projects › Attest Demo 2 › Traffic › Requests
TimeMethodPathStatusDurationStack
› 16:10:25POST/todos3023 mslegacy
› 16:10:25GET/todos/new2002 mslegacy
› 16:10:24GET/todos/512/edit2003 mslegacy
▾ 16:10:24POST/todos/15383/done30288 mslegacy
Request id b654f8549f53ac1e · 4 log lines from 2 sources carry it
16:10:24.310legacy-appINFOrequest POST /todos/:id/done controller=TodosController action=done
16:10:24.318legacy-dbLOGUPDATE "todos" SET "completed_at" = $1 WHERE "todos"."id" = $2
16:10:24.341legacy-dbLOGINSERT INTO "notifications" ("todo_id", "kind") VALUES ($1, $2)
16:10:24.398legacy-appINFOCompleted 302 Found in 88ms · smtp TodoMailer
› 16:10:24GET/todos20028 mslegacy
› 16:10:23POST/logout3022 mslegacy
› 16:10:22GET/todos/37982003 mslegacy
› 16:10:21GET/stats2003 mslegacy
CommandProductBuildCodeGraphTrafficLogsDataReleaseAgentsReports
Projects › Billing Portal › Product › Requirements & coverage
Requirements & coverage7 accepted · 3 uncovered · 2 implemented
REQ-4k2pWhen an admin exports an invoice, the system shall produce one CSV row per invoice line.fab-9k2p · in progress
REQ-9m1dIf an invoice has no lines, then the system shall export the header row only.fab-9k2p · in progress
REQ-c3d4The system shall include unbillable lines in every export with a zero total.✓ implemented
REQ-p5r3While an invoice is awaiting approval, the system shall prevent edits to its lines.no story yet
REQ-u2k6The system shall record who approved each invoice and when.✓ implemented
REQ-a7e2When an admin approves an invoice, the system shall email the client a payment link.no story yet
TraceabilityREQ-4k2p
SOURCE^blk-2m9x“Finance reconciles every invoice line by line.”
REQUIREMENTREQ-4k2pone CSV row per invoice line
STORYfab-9k2pExport invoice lines as CSV
DOC PAGE▤ Exportdocuments ← fab-9k2p

Lock

A specification you can sign off

Observed behaviour and reviews with the system's owners become testable requirements with stable IDs. Approved versions are locked, and a change makes a new version.

  • Requirements in plain, testable sentences
  • Each one linked to its evidence, stories, pull requests and pages
  • Coverage shows what nothing implements yet
  • Living documentation that stays in step with the code

Engineer

An agent team your engineers direct

Foreman plans each domain and runs workers, verifiers and a business analyst. Your engineers approve plans, decisions, merges and configuration, and anything that needs a person lands in their inbox.

  • Every change arrives as a pull request in your repository
  • A verifier checks each story before it is done
  • Work the agents discover is logged for review, never slipped in
  • Assign any story to Fabrica or to a person
CommandProductBuildCodeGraphTrafficLogsDataReleaseAgentsReports
Projects › Billing Portal › Board
Backlog 2
fab-t6y3
Currency rounding on multi-line invoices
fab-r4d9
Document GET /invoices/:periodProposed by analyst
Selected 1
fab-n5cf
Saved payment methodsQueued · #2
In progress 2
fab-9k2p
Export invoice lines as CSVWorker: running the tests$12.40 / $40
fab-m7v4
Webhook retries double-chargeNeeds human
Verify 1
fab-x3t1
Invoice approval flowVerifier running · PR #482
Done 2
fab-a1b2
Show unbillable linesVerifier passed
fab-k3m1
Document GET /users/:idVerifier passed
CommandProductBuildCodeGraphTrafficLogsDataReleaseAgentsReports
Projects › Todo Modernization › Data › Range checksums
Range checksums · todosFailedOpen a story for the agent
490 ranges›1 range differs›3 keys›4 fields
1. Key rangesonly the differing range is red
2. Keys and differing fieldsnames and hashes, no values
Legacy idDiffering fieldsWritten by
41,237priority updated_atdirect write, not the sync
41,251completed_atdirect write, not the sync
41,288prioritydirect write, not the sync
What the evidence says: these rows were written by PATCH /todos/:id on the new app, not by the sync. That is a second writer, not a mapping bug.

Attest

Proof, not promises

The rebuilt system is tested against the same specification as the old one, on replayed or shadowed live workloads with side effects under control. When something differs, Fabrica narrows it down and shows why.

  • Old and new compared request by request
  • Data reconciled range by range, down to the field
  • Permissions checked for every role
  • Open differences become stories with an owner

Release

Move users route by route, with a way back

A routing layer in front of both systems decides who gets the new one. Start with people who opt in, then a small share of traffic, and raise it as the evidence comes in.

  • Beta opt-in, with a switch back to the old experience
  • Rollout by route and by cohort
  • Each step gated on evidence, not on a date
CommandProductBuildCodeGraphTrafficLogsDataReleaseAgentsReports
Projects › Legacy CRM Rewrite › Release › Beta opt-in
Beta opt-inVisitors who opt in are served by the new stack on the routes below. Every other route stays on legacy.On
Opt-in URL/__fabrica/beta/onOpt-out URL/__fabrica/beta/off
Save beta opt-in
CommandProductBuildCodeGraphTrafficLogsDataReleaseAgentsReports
Projects › Todo Modernization › Data › todos + notifications
todos + notificationsWrites flipped · reverse sync
✓Configured
✓Snapshotting
✓Streaming
✓Reads moved
5Writes flipped
6Retired
SyncReverse: new → legacy
Captured into the change log
Applied to legacy
Gap: 9 changes · under 1 s
Cutover gatePassed
✓ 3 of 3 days green✓ Lag 2 s < 30 s✓ No unexplained mismatches✓ Transform v3 approved
Write ownership
Writes go to the new database. Reverse sync keeps legacy current for the routes that still read it.Rollback window2 d 14 h left
↶ Roll back to legacy

Data migration

Migrate the data without a big bang

Fabrica streams every change from the legacy database into the new one, and the new schema can be redesigned, not just copied. Reads move first. Writes flip only when the checks have stayed green, and a rollback window keeps the way back open.

  • A cutover gate written as code, not a meeting
  • Reverse sync keeps legacy current for what still reads it
  • Replay from any point when a mapping changes
  • Legacy tables retire only when nothing reads them

Stay current

Never fall behind again

Legacy is what happens when a system stops being looked after. Fabrica stays connected after cutover, like a utility. Its project graph joins the code, the live traffic, the data and every agent run into one view of the system, so upgrades and new features go through the same proof as the rebuild.

  • One graph links each requirement to code, routes, data and proof
  • Every change shows its blast radius before it ships
  • New work runs through the same board and verifier
  • Documentation that never drifts from what runs
Shells · centre outIntent34Work38Execution115Change150Code281Runtime33Data15666 nodes · 1063 edges1 agent live
worker · fab-lm3c
Parity: POST /login

The most complete view of your system

Fabrica joins seven sources that usually live apart. The code shows what could happen, traffic and logs show what does happen, the data shows what changes, and agent runs show what was done about it.

Intent

Requirements and documentation pages from the locked specification.

Work

Epics and stories created by the business analyst and the planner.

Execution

Every worker and verifier run, with its attempts and what it touched.

Change

Commits and pull requests in your repository.

Code

Files and symbols, linked by the code's call graph.

Runtime

Routes seen by the observe proxy, and the log lines tied to each request.

Data

Tables, and the routes that read and write them.

Every link says how it is known

Declared, observed in traffic, found in the code, or inferred and waiting for a person to confirm.

Data handling

Your data and your code stay yours

Fabrica is built to observe a production system without putting it at risk.

100% in your environment

Fabrica runs inside your own infrastructure. Your code, your traffic and your data never leave it.

Read-only access

Fabrica reads your systems. It doesn't change them.

Redacted before analysis

Sensitive payloads are redacted before anything is analysed.

Off the request path

Collection runs beside your traffic, so a failure on our side can't reach your customers.

Code in your repository

Every change is a pull request in your repository, under your review.

Read about security →

What plans are your legacy systems holding up?

Tell us about it on a 30-minute call. We'll suggest a first scope and what a technical review would need to confirm.

Book a 30-minute call