Can each client have their own account and domain?

Yes. Each project publishes to its own custom domain, and the client can subscribe on their own account so the invoice never passes through you.

How do we control who on the team can publish?

Roles and permissions: 24 of them across 5 roles, including publishing rights. A junior can build all week and still not push to production.

Is there anything in it for us commercially?

Yes. 25% of every invoice for the client's first 12 months, then 10% for as long as they stay subscribed, on top of whatever you charged for the delivery. The partner programme has the full terms.

Do we have to white-label it, or does it say Fabapp?

The published app carries your client's own domain and brand. The "Made with Fabapp" badge only shows on a free-plan app, and it disappears the moment the project moves to a paid plan.

If we stop actively managing the account, do we lose the commission?

No. As long as the client keeps paying and your referral is on record, the commission keeps coming. You don't have to keep delivering work for that client to keep earning from it.

Who it is for

Ship client work in days, and get paid twice

The scope that used to take a sprint takes an afternoon, for you and for any freelancer on the team. Present a working app instead of a slide deck, hand over code the client actually owns, and keep a share of the invoice for as long as they stay subscribed.

Build my app for free

painel.suaagencia.com

Client projects

4 Live

Clínica Alvorada

clinicaalvorada.com.br

Live

Escola Vértice

In review

Draft

Padaria do Bairro

padariadobairro.app

Live

Brands already built on Fabapp

SodexoVivoBraskemSescTicketWhirlpoolNissan

Customers of Fábrica de Aplicativos, the platform Fabapp AI grew out of.

25%

commission on every invoice, the client's first year

10%

residual commission after that, for as long as they stay

permissions across 5 roles, so publishing stays yours to grant

lock-in (the code exports to the client's GitHub, any time)

The proposal, the prototype and the delivery are the same artifact

Presenting a working app instead of a slide deck closes the sale, and the app you presented is the one you ship, with no rebuild between the demo and the delivery.

Present something that runs

Walk into the meeting with the client's app open on your laptop. Nobody has ever approved a wireframe faster than a working screen.

One account, every project

24 permissions across 5 roles decide who on the team can publish. A junior can build all week and still not touch production.

Hand over the code, not a black box

Export the whole project to the client's GitHub, any time. No lock-in to explain in the contract, and no argument at the end of the engagement.

Get paid twice

25% of every invoice in the client's first year, then 10% for as long as they stay subscribed, on top of what you charged for the delivery itself.

White-label, client by client

Each project publishes to its own custom domain under the client's brand. Nothing on the live app says Fabapp unless you want it to.

Same-afternoon revisions

A change requested at 2pm can be live by 4. Version history means a junior can experiment without risking what is already in production.

Dream it. Build it. Ship it.

Not a list of templates — the kinds of product this platform actually produces, and the piece of it that is already built for you.

Subscription SaaS

Sign-in, plans, recurring billing and a customer dashboard. The tedious half of a SaaS ships with the app; you write the half that is yours.

Store and marketplace

Catalogue, cart, checkout with cards and local methods, orders and coupons. Sellers, commission and payouts when the model needs them.

Community app

Profiles, feed, groups, comments and access levels. Native push to bring people back without buying reach from an algorithm.

Site and landing page

Your own domain, SEO written into the build, and a form that saves to your own database instead of somebody else's inbox.

Internal tool

Records, approvals, role-based permission and a dashboard. What is a shared spreadsheet with three owners today.

Native app in the stores

The same project becomes an iOS and Android binary under your own developer account, with push and in-app purchase.

What changes when the build stops being the bottleneck

Same client work. A very different week.

Taking on a client project today

A sprint of design and dev before the client sees anything real
Auth, database and payments rebuilt from scratch, project after project
You keep footing the hosting bill long after the invoice is paid
Every small change goes back through you, even the ones the client could make alone

Delivering it on Fabapp

A working prototype in the same meeting where you scope the project
Auth, database, payments and roles come with the platform, every time
The client subscribes on their own account and covers their own hosting
The client or a junior can ask the AI for a small change without opening a ticket

The fastest way to find out is to describe it

One paragraph, and you are looking at a working app in a few minutes. Free, and no card.