SFab · open-source software factory

An opinionated
software factory.

It learns how your business runs, builds your software, and shows you proof it works. You never read the code.

01The thesis

Your business shouldn't bend to its software.

Off-the-shelf tools make you work their way. Custom software was always the answer, and always too expensive to build, too risky to keep alive. SFab changes both: a factory that learns how your business runs, builds your software around it, AI-native with an agent of its own inside, and keeps it healthy long after it ships. It all starts with business context:

01
What you give it

A conversation about how your business runs. The spreadsheets you run it on. Connections to the tools you already use.

02
What it becomes

Versioned ground truth, kept in the repo like code. Every change is built from it, and checked against it before you ever see it.

03
How it learns

Say “that's not how my business works” and the correction flows back in. Every approval, and every no, makes the context sharper.

scope

Built for the proven shapes of business software: CRMs, ERPs, the systems a business runs on. Ask for something outside that line and it will push back and tell you why. But the call stays yours. You can build anything.

02How the factory works

Watch an idea become software.

One opinionated process, run the same way every time. Your business context goes in, agents work the stations, and the line always ends at you. And the line is a loop: the factory owns CI, CD, and continuous monitoring. It watches every app it ships, what breaks re-enters the line as a task, and the loop never stops.

SFab · line 01 RUNNING

The SFab factory line drawn as a straight engineering schematic: context, task, build, checks, proof, live, monitor. An accent pulse traces each module in sequence, then rides a return trace from monitor back to context. The line is a closed loop, and the loop never stops.

03Proof & guardrails

You check the business. The factory checks the code.

When a change is ready, you don't get a pull request. You get proof: a video of it working the way your business works, and a live preview you can try yourself. Approve it and it goes live. Say “that's not how my business works” and the factory reworks it, and remembers why. Underneath, the factory holds its side of the deal:

MECH·01Template-lockAgents build inside one stack; drift is impossible by construction.
MECH·02Acceptance-criteria gateEvery change answers to a task with verifiable criteria. No silent scope.
MECH·03AI review on every PRAn independent agent challenges the approach and posts a verdict before anything merges.
MECH·04An evidence trailStructured logs, token/cost ledgers, and a transcript. Nothing happens in the dark.
How trust works →

Nothing is hidden. Every transcript, every PR, every diff is one click away when you want it.

04For the engineers

Anyone can generate code now. That was never the hard part.

The models got good. What they still need is constraint. Hand an agent a blank repo and infinite freedom and you get a demo that rots by Friday. Give it one battle-tested, type-safe stack, chosen once so agents never have to, and generation becomes engineering.

01
TanStack Start + TypeScript
type-safe app frame
02
Cloudflare Workers + D1
zero-ops edge runtime
03
Drizzle
typed data
04
Better Auth
typed identity
05
shadcn/ui + registry
the interface kit
06
Agents SDK + Think
the built-in brain
.sfab/template.jsonsfab-starter · version-pinned

Every app is fabricated from one versioned template, with docs, skills, and UI blocks included. Fix something once and it propagates everywhere.

05Open, in public

Your factory. Your keys. Your edge.

Open source, end to end: fork it, self-host it, read every line. No black box, no hostage data. The whole machine runs on Cloudflare, on one edge, so deploy is a single command, not a project. And it's all being built in the open.

ready
Self-host

One deploy to your own Cloudflare account. Own every key.

soon
Hosted

A managed factory, when it's ready. No waitlist theater.

Star the repo, follow the build, and when you're ready, your agent deploys it for you.