From idea to verified software, websites and apps.
Describe what you want. Farbaek plans it, builds it with an agent, runs the real checks and waits for your approval before anything ships.
See what works today
Watch one build, start to finish.
A sample bakery site goes from one sentence to a checked, published and confirmed live address. Recorded from Farbaek's interface, with the waits shortened.
58 seconds, 6 chapters. Silent, with captions.
0:58
Read what happens
- Describe. Describe what you want in one sentence. Farbaek starts a project and drafts a plan.
- Plan. Read the plan: the goal, what must not change and the design. Approve it to start the build.
- Build. The agent works in the open. Every step shows as it happens, and the preview updates.
- Check. Before anything goes live, a security check reads exactly these files and scores them.
- Publish. Publish puts this exact version at its own address. Every version is kept.
- Live. Farbaek opens the address and confirms the live site serves exactly this version.
- Plan
- Code
- Tests
- Approval
- Proof
Farbaekisadevelopmentplatformwhereeverychangeisplanned,checked,approvedandprovenbeforeitreachesyourusers.
What it does for you.
Four moments from the same build, up close. Each clip is recorded from Farbaek with a sample project.
The plan card for a sample bakery site: goal, limits, design and skills, then Approve and build.
A plan you approve before any code.
- The goal, what must not change and the design, in plain words.
- Skills picked for this build, and an estimate of how much of your AI usage it will take.
- Nothing is built until you approve it.
The agent's steps stream in while the sample bakery site takes shape in the preview.
An agent that works in the open.
- Every step shows as it happens: reading, writing and checking.
- The preview updates while the site takes shape.
- Message the agent while it runs, or stop the run.
A security check of the sample site's files scores an A with nothing critical.
Checked before it can go live.
- Farbaek's security rules read every file.
- Packages are checked for known vulnerabilities, and an AI reviews the riskiest files.
- Publishing needs a check of exactly these files that found nothing critical.
The sample site is published and Farbaek's live check confirms its address serves exactly this version.
Published, then confirmed live.
- Publish puts this exact version at its own address.
- Every version is kept, and any earlier one can be made live again.
- Farbaek opens the address and confirms it serves exactly this version.
The plan card for a sample bakery site: goal, limits, design and skills, then Approve and build.
The agent's steps stream in while the sample bakery site takes shape in the preview.
A security check of the sample site's files scores an A with nothing critical.
The sample site is published and Farbaek's live check confirms its address serves exactly this version.
Start from something like these.
Eight concepts, each with its own look, motion and purpose, the way Farbaek designs every build. Pick one and start a build like it.
A type foundry website: a huge specimen of the word Kestrel in three weights, a weight slider, a glyph grid, and a floating type tester card.
Concept mockupTypeset Foundry
Type foundry · Website
A type foundry's site where the letters are the interface.
It starts with a sentence:
“A website for my type foundry with a live type tester, a glyph grid and font licences people can buy”
You approve the plan before anything is built.
- Palette
- Proof paperPress inkSignal red(accent)Graphite
- Type
- Geist at its heaviest, set huge and tight, with Geist Mono for specimens.
- Signature
- Glyphs that shift weight like a breath, and a tester that sets your own words.
It would use the Brand identity and Motion and interaction skills.
A build writes its own design read like this one into DESIGN.md before any page.
Concept mockups drawn for this page. They show the kind of thing you can ask for; none of them is a live product.
What every build comes with.
See what works todayA plan before anything is built
WorkingDescribe it in plain words. Farbaek drafts a plan you edit and approve.
Design to a studio standard
WorkingEvery site builds on the Farbaek Studio kit: a design read, one 3D piece, motion that means something, and photos and video you can swap. Paid plans add Studio kit Pro.
Skills, including your own
WorkingTwelve built-in design skills and a library of open-licensed ones to add in a click. Add your own, or any from GitHub, in the open SKILL.md format.
An agent you can steer
WorkingIt builds in the cloud under the plan you approved. Message it while it works. Every action is checked against the plan before it runs.
Previews of real code
WorkingStatic sites preview instantly. Apps with a server run in an isolated test space.
Checks before it's done
WorkingThe agent reviews its own pages, security checks score the code, and the plan's checks run real commands.
Approval and proof
WorkingApprovals bind to the exact change, and a ProofPack records what ran and what it doesn't prove.
Publish to your own address
WorkingA static site goes live on its own address after a security check finds nothing critical.
Bring your project, take your code
WorkingImport a .zip of an app built elsewhere for a security report, and download your code at any time.
Image generation
Turning onDescribe a picture and Farbaek makes it straight into your project, counted against your AI usage. Or add your own images.
Not available yet.
Proof before anything ships.
A change is reviewed, approved exactly as you saw it, checked in a test space and sealed with what it proves and what it doesn't.
43 seconds, 6 chapters. Silent, with captions.
0:43
Read what happens
- Review. Review a change file by file. Keep what you want, reject the rest.
- Approve. Approval binds to a hash of exactly what you saw. Change one character and it stops matching.
- Checks. Checks run in a test space against the applied files. The real results decide, and a check that didn't run says so.
- ProofPack. A ProofPack records what ran, against which files, and what it doesn't prove.
- Before publishing. Publishing needs a clean check of these exact files, then the live check confirms them.
- Undo. An applied change can be undone, and the undo is recorded too.
Approvals bind to the exact change.
Approve the change, then edit it. The approval stops matching, because it was tied to a hash of exactly what you saw.
What the agent wants to do
An agent wants to run this against the sample storefront. Edit it.
The plan allows at most 100.
Exactly what you're approving, as Farbaek hashes it
{"fields":{"description":"Hand-finished walnut, oiled twice."},"operation":"products.update","target":{"collection":"products","count":100}}Plan version 3, rules version 12
Needs your approvalApprove an update to 100 product descriptions?
- The hash your approval is tied to
- computing…
Protected by the plan: price, stock, published.
Approve first, then run. Nothing really runs here.
Demo with sample data. It runs Farbaek's own hashing and plan-checking code in your browser. Nothing is executed, stored or sent.
Eight parts, one shared core.
Studio, the agent, moving projects and launching all use the same rules, proof and plan limits. Nothing is built twice.
Studio
A visual editor for static sites and a real code workspace on one source of truth. Every visual edit, and every change the agent suggests, is shown line by line for you to review.
content/products/descriptions.json+2 -2 {Removed: "walnut-board": "Walnut board.",Added: "walnut-board": "Hand-finished walnut, oiled twice.",Removed: "oak-tray": "Oak tray."Added: "oak-tray": "Quarter-sawn oak, waxed by hand."}Sample diff
Trust
Rules, approvals, what each agent may do, how much runs on its own, and a full history, all enforced on the server. Words in a prompt are never what keeps you safe.
Each change is allowed, allowed within limits, held for your approval, tried first in a test space, sent to an owner, or blocked.
Agent
Farbaek's own runtime. The model suggests; Farbaek checks every action against your plan before it runs.
Plans
A plan you approve for every task, what the agent needs to know first, and how it turned out: received, plan approved, building, checking, verified.
Core
Sign-in, workspaces, projects, tasks and what each plan includes.
Move projects
Send projects between your own devices: nearby, directly over the internet, or through Farbaek's relay, encrypted end to end and checked byte for byte.
Built and tested, being proven on real accounts and devices. What works today
Launch
Launch to your own Vercel or Netlify account, with what goes named first, your typed confirmation, and live checks after.
Built and tested, being proven on real accounts and devices. What works today
Mobile
Install Farbaek on your phone: approve work, get told when builds finish, and send files to your computer.
Built and tested, being proven on real accounts and devices. What works today
Proof you can check, not just read.
A ProofPack is a signed record of what changed, what ran, and what that does and doesn't prove. It uses an open format, so anyone can check it.
{
"_type": "https://in-toto.io/Statement/v1",
"subject": [
{
"name": "content/products/descriptions.json",
"digest": {
"sha256": "6130b4ebf731b7df1c92beba5fe97462664a05cd2417fa9ecaca01612607a385"
}
}
],
"predicateType": "https://farbaek.com/proofpack/v1",
"predicate": {
"sample": true,
"task": {
"id": "tsk_sample",
"outcome": "Rewrite the descriptions of 100 storefront products in the new house style."
},
"contract": {
"schema": "farbaek.intent-contract/v1",
"version": 3,
"sha256": "134a270752f5472171923553753e14d7980843a4be08c4734b887e11ef251ac8"
},
"policy": {
"version": "12",
"decision": "REQUIRE_APPROVAL"
},
"approval": {
"state": "approved",
"bindingSha256": "cd6a57f6174ba7e31f817549360f8294f42e97fc21e19840393052da4d5891fe"
},
"checks": [
{
"name": "typecheck",
"command": "pnpm typecheck",
"exitCode": 0
},
{
"name": "unit tests",
"command": "pnpm test",
"exitCode": 0
}
],
"postconditions": [
{
"id": "inv-1",
"method": "read_back",
"result": "passed"
},
{
"id": "ac-2",
"method": "read_back",
"result": "passed"
}
],
"verification": {
"status": "verified",
"notVerified": [
"Storefront rendering on real devices"
],
"limits": "Shows these commands ran against this exact state with these results. It does not prove the absence of other defects."
}
}
}{
"schema": "farbaek.intent-contract/v1",
"version": 3,
"outcome": "Rewrite the descriptions of 100 storefront products in the new house style.",
"scope": {
"organizationId": "org_sample",
"projectId": "prj_sample_storefront",
"resources": [
"products"
]
},
"allowedOperations": [
"products.update"
],
"forbiddenOperations": [
"products.delete",
"products.publish"
],
"protectedFields": [
"price",
"stock",
"published"
],
"protectedInvariants": [
{
"id": "inv-1",
"statement": "Prices, stock and publication state are unchanged."
},
{
"id": "inv-2",
"statement": "No orders are created, edited or cancelled."
}
],
"assumptions": [
"The house style guide in docs/style.md is current."
],
"openQuestions": [],
"acceptanceCriteria": [
{
"id": "ac-1",
"statement": "All 100 products have a description under 160 characters.",
"verification": "test"
},
{
"id": "ac-2",
"statement": "Saved descriptions read back exactly as approved.",
"verification": "read_back"
}
],
"approvals": [
{
"gate": "before_execution",
"role": "catalog_owner"
}
],
"limits": {
"maxRecords": 100,
"maxRetries": 2
},
"requiredChecks": [
"pnpm typecheck",
"pnpm test"
],
"recovery": "Restore the previous descriptions from the pre-change snapshot."
}Sample written to show the format. This seal is drawn from the sample's own JSON.
Check a ProofPack yourselfWhat it proves
- Which exact files and commit were checked
- Which commands ran, and their results
- Which plan and approval it ran under
What it doesn't
- That the software has no other defects
- Anything a check didn't cover
- Claims from systems Farbaek can't read back
What works today, and what doesn't yet.
New workspaces start a 14-day trial with no card, one per email address. After it, stay on Free or choose a plan from $0.99 a month.
Built and working
Live at www.farbaek.com, tested and used end to end.
- Sign-in by email link, and workspaces kept strictly apart
- One sentence to a plan: Farbaek drafts it, and you read and approve it
- The cloud agent builds under that plan, and you can message it while it works
- Projects with versioned files, import, search and the Studio editor
- Previews of static sites
- Security checks, site checks in an isolated test space with real results, and undo
- Signed ProofPacks anyone can check, in the browser or with OpenSSL
- Publishing static sites to their own address
- 14-day trial, and plan limits enforced on Farbaek's side
- Paid plans from $0.99 a month, through Dodo Payments
- Farbaek Agent for Windows, Mac and Linux
Being proven
Built and tested, being proven on real accounts and devices.
- Moving projects between your own devices, nearby or over the internet
- Launches to your own Vercel or Netlify account
- Farbaek installed on your phone, with notifications
- Previews of running apps in isolated test spaces
- Your own domain for a published site
- Image generation from a description, and your own images in projects
Next
Planned next, in no fixed order.
- The Android app on Google Play
- Farbaek for iPhone on the App Store, approving changes with Face ID or Touch ID (Farbaek installs from Safari today)
- Launches from a repository (Render, Railway, Fly.io)
One subscription. The models, test spaces and checks are included.
No API keys to bring. New workspaces get a 14-day Pro trial with no card, one per email address. When it ends you move to Free, and nothing is charged.
- Free
- $0forever
- About 1 agent session a month1 test space hour, 1 seat
- Lite
- $0.99a month
- About 1 agent session a month1 test space hour, 1 seat
- Maker
- $1.99a month
- About 1 agent session a month2 test space hours, 1 seat
- Starter
- $9.99a month
- About 4 agent sessions a month5 test space hours, 1 seat
- Plus
- $19.99a month
- About 11 agent sessions a month10 test space hours, 1 seat
- ProRecommended
- $50a month
- About 32 agent sessions a month25 test space hours, 2 seats
- Studio
- $79.99a month
- About 53 agent sessions a month40 test space hours, 3 seats
- Max
- $100a month
- About 68 agent sessions a month50 test space hours, 5 seats
- Max 2x
- $200a month
- About 138 agent sessions a month100 test space hours, 10 seats
- Max 3x
- $300a month
- About 209 agent sessions a month150 test space hours, 20 seats
Common questions
Can I sign up today?
Yes. Sign in with your email and your workspace starts a 14-day Pro trial, with no card. When the trial ends you move to Free, and nothing is charged unless you choose a paid plan.
Does Farbaek run my code safely?
Builds, tests and checks run in isolated test spaces with time and memory limits, away from Farbaek's own servers. Where isolation can't be verified, Farbaek drops to Review Only instead of pretending.
What does a ProofPack prove?
That specific commands ran against a specific state with specific results, under stated assumptions. It does not prove your software is free of defects.
Which AI models does it use?
Claude models from Anthropic for plans and code, and Google's Gemini for images. Farbaek records which model worked on each task and never switches quietly.
Is there lock-in?
No. Projects are plain files. Export everything gives you the code, plans, ProofPacks and history, and you can carry on without Farbaek.





