Ready-made apps
What will you build first?
Browse what other people have already shipped with Fabapp AI — every one of them is a finished app you can copy and make yours.
Start for freeDescribe your idea and Fabapp AI builds a complete app with login, payments and data, ready to publish. Without writing a single line of code.
Brands already built on Fabapp
Customers of Fábrica de Aplicativos, the platform Fabapp AI grew out of.
Ready-made apps
Browse what other people have already shipped with Fabapp AI — every one of them is a finished app you can copy and make yours.
Start for freeWork management with boards: a table view grouped by section, a drag-and-drop kanban, and analytics across every board.
4 screensDouble-entry accounting: chart of accounts, balanced journal entries, trial balance, balance sheet and income statement.
5 screensA slow-fashion label site: seasonal collections, timeless essentials, traceable materials and a newsletter.
6 screensAI chart analysis: upload a screenshot and get pattern, entry, targets and stop.
4 screensPersonal finance: income, spending, accounts, investments and goals in one place.
9 screensA retro platformer whose levels live in your database.
4 screensA burger rush game where the menu is a record in your database.
4 screensA staff portal that shows each person only what is addressed to them, and what is waiting on them.
14 screensA sales CRM whose coach reads the deal and tells you the next move.
12 screensA drafting room for legal work: nine assistants, each carrying its own jurisdiction layer.
12 screensClass booking for a studio with a hard capacity: credits, a waiting list that moves itself, and a door roster that records who came.
15 screensA full-bleed site for an architecture practice, with a small CMS behind it and an inbox that reads each enquiry against the criteria the studio itself wrote down.
15 screensThe hard part of an app is not the first pretty screen. It is what happens when it has to charge in each customer's own payment method, land on somebody's phone and still be standing next month.
An iOS and Android binary published on the App Store and Google Play under your own developer account, with native push, camera, location and biometric login. Not a browser shortcut wearing your icon.
See how store publishing worksStripe worldwide, plus the methods that only exist in your customer's country: Pix and boleto in Brazil, Mercado Pago across Latin America. Priced in the buyer's currency, with card data in a vault we host.
See the payment methodsSell subscriptions and products through the store itself, the way Apple and Google require. Every purchase is verified with the app owner's key, because the device never decides on its own what was paid.
How store purchases workAnd the usual is still here: real React code, editable and exportable to your GitHub, free npm, click-to-code visual editing and history with undo. None of it is optional in this house.
You do not choose between a site and an app, and you do not rebuild the app for each platform. It is the same project published three ways, and the second and third cost no new work.
Live with HTTPS and a CDN in seconds. Start on a fabapp.app address and swap in your own domain whenever you want.
It goes to the home screen straight from the browser, no store and no download. The shortest path from a link in a chat to an icon on your customer's phone.
The same project becomes a signed binary, submitted to the store under your account, with push, device permissions and in-app purchase.
No server to rent, no payment provider to wire, no database to model by hand. It is already there on the first build.
Data models with relations, permissions per record, file and video storage.
Sign-up, sign-in, Google login, profiles, roles and access levels for the people who use your app.
Stripe, Pagar.me and Mercado Pago — card, Pix and recurring billing, with the card data in a vault we host.
Transactional email, campaigns, push on the phone, SMS, Slack and Discord.
WhatsApp, Shopify, Notion, Airtable, Mailchimp, Telegram, Google Workspace, outgoing webhooks and any OpenAPI service.
Your published app can call a model at runtime: generate text and images, read a document, run an agent.
Custom domain, colors, logo, and the Fabapp badge removed from paid plans on.
Ship to the App Store and Play Store, or export the whole project as code to GitHub — it is yours.
Combined figures for Fábrica de Aplicativos and Fabapp AI since 2011. The platform is available in English, Portuguese, Spanish, French and German, and the AI builds your app in whatever language you write to it in.
Each category is a page with real examples, the templates you can start from today and a prompt ready to paste. Pick by what the app has to do.
See all 10 categoriesCatalog, cart, checkout, coupons and subscriptions. Card and Pix built in, with orders and customers in your own database.
Availability per professional, confirmation, reminders and check-in — the classic agenda, without the spreadsheet.
Lessons, modules, student progress and a paywall, with video and files hosted on the platform.
Profiles, feeds, posts, comments and directories, with ownership rules per record.
Pipelines, leads, proposals and follow-ups — a CRM shaped like your process instead of someone else's.
Onboarding, requests, approvals, documents and signatures — the internal flows that live in email today.
Ledgers, budgets, expense control and financial dashboards, with charts that read from your own records.
Quizzes, challenges, scoreboards and interactive experiences that run in the browser.
Service desks, internal back offices, order tracking, checklists and dashboards for your team.
If you can describe it, the AI builds it. Start from the prompt.
Tell us in one sentence the app you imagine.
Screens, data and content assembled automatically.
Edit colors, text and features without coding.
Publish on the web and share the link — installable as an app (PWA).
Publishing is the middle of the job, not the end. What comes next is already built in.
FeaturesTitle, description and social card per page, robots.txt, sitemap.xml and structured data written into the build — not a toggle that does nothing.
The published app can generate its own llms.txt and JSON-LD, so a language model describes your product correctly instead of guessing.
Google Analytics 4, Tag Manager, Clarity, Hotjar, AdSense and Consent Mode v2 — connected by filling in an ID, with a head-code escape hatch for the rest.
Anyone who publishes an app with customer data inside is taking on a risk. These are the six things the platform does underneath so that the risk is not yours.
Who reads each record is a Postgres rule. A badly written screen does not become a leak, because the database answers empty.
A secret written into the code and a broken access rule are blocked at publish time, not discovered later by your customer.
Every app is built in a container that is born and dies, without a single platform key inside it.
The AI inside your app runs under the permission of whoever called it. It has no back door to other people's data.
A second factor and passkeys on your account, and 24 permissions across 5 roles to decide who on the team can publish.
Cookie consent, a data processing agreement and six versioned legal documents, in each of the five languages.
In the media
No. You describe what you want in plain language and the AI creates the app — screens, data and content. Adjustments are visual, and from the Starter plan you can also edit the code.
Free to start, no credit card. You only pay when you want to publish under your own brand, and you take the code with you if you ever want to.