I Ran an Open Source AI App Builder Locally (2026 Log)

Quick Answer (2026): ai-app-builder-open is a free, MIT-licensed, open source AI app builder you clone from GitHub and run on your own machine with npm run dev. You give it a prompt, it generates a full-stack Next.js 16 app with hosting, a database, and auth wired in. The honest catch, and the reason I wrote this log: the code is open, but the engine that actually writes your app is a hosted API (Totalum VCaaS) that you plug in with one key. So it is open source, but it is not local-first the way Dyad is. Here is my weekend actually running it.

I spent Saturday morning with a repo I had bookmarked for two weeks.

The pitch grabbed me: an open source AI app builder I could clone and own, instead of renting a tab on someone's website.

By lunch I had it running on localhost:3000. By the afternoon I had a real opinion. This is that opinion.

What is this thing, in plain English?

Skip this section if you already ship code. If you don't, read it first.

An "AI app builder" is a tool where you describe an app in words, and the tool writes the whole thing for you. The frontend, the backend, the database, the login screen. Think of it as a very fast junior developer who never sleeps.

"Open source" means the code for the tool itself is public. Anyone can read it, copy it, change it, and run their own copy. That is different from a website like a normal builder, where the code lives on the company's servers and you just borrow it.

ai-app-builder-open is that second kind. It lives on GitHub. You download it and run it on your computer.

Here is the part the marketing pages skip. The tool has two halves. The half you download is a clean control panel: the chat box, the code editor, the preview window. The half that does the real thinking, actually generating your app, runs on a company's servers. That company is Totalum, and you connect to it with an account and a key.

So who is this for? Developers who want to own and self-host the builder itself, tinkerers who like taking things apart, and agencies who want a white-label base they can rebrand. Who is it not for? Anyone who wants a 100 percent free, offline, no-account tool. That person wants Dyad, and I will get to why.

The weekend setup: clone, key, run

This part took about fifteen minutes, most of it waiting on npm install.

You need Node.js 20 or newer. Then:

git clone https://github.com/totalumlabs/ai-app-builder-open.git
cd ai-app-builder-open
npm install

Now the one piece of config that matters. An "environment variable" is just a secret setting your app reads at startup, kept in a file so it never lands in your code. Create a .env.local file in the project root:

TOTALUM_VCAAS_API_KEY=your_key_here

Where does the key come from? You make an account at totalum.app, pick the "Use the Totalum API" option, and copy the key it hands you. The first 50 AI credits are free, which was plenty to kick the tires all weekend. I followed the Totalum VCaaS quickstart to get the key and confirm the format before pasting it in. One nice detail: the key stays server-side. It is not a NEXT_PUBLIC_ variable, so it never ships to the browser. The repo proxies every call through src/lib/vcaas.ts, so your key is not sitting in someone's devtools.

Then:

npm run dev

Open http://localhost:3000. That is it. No Docker, no separate database to stand up, no cloud account to configure first.

There is no npm SDK to install, by the way. I went looking for a @totalum/sdk package out of habit. There isn't one. It is a plain REST proxy, and honestly that made the whole thing easier to read.

First prompt to first app

This is the moment I actually cared about.

I typed a boring but real prompt: a small CRM with contacts, a notes field, and a login. Then I watched.

The build is not instant. The agent runs on the hosted side and takes somewhere between ten and thirty minutes, which is normal for this class of tool. When it finished, I had a preview URL, a working login, a contacts table I could click through, and a Monaco code editor showing the actual generated source.

The output is a real Next.js 16 app on React 19, not a throwaway single-page demo. There is a managed database with a UI to browse rows, a git-diff viewer so you can see exactly what each prompt changed, version history with rollback, and live server logs. The bones are genuinely nice.

Here is the mental model that clicked for me: the repo is a clean, ownable shell, and Totalum is the engine bolted into it. You own the shell. You rent the engine. If that trade sounds fine, keep reading, because there is a real cost to it.

The honest part: this is not Dyad

I have to be straight, because this is the whole point of a field log.

Dyad is the reigning champ for "open source AI app builder," and it wins that title honestly. It runs entirely on your desktop. You bring your own model keys. No subscription, no paywall, no company in the loop. If the vendor vanished tomorrow, your Dyad keeps working.

ai-app-builder-open cannot say that. After those 50 free credits, the engine is a paid, hosted dependency. If the API is down, or you stop paying, your builder stops building. The code is yours forever; the thing that makes the code is not. "Open source" and "free to run forever" are not the same sentence here, and anyone who tells you otherwise is selling something.

It is also young. Nineteen stars and three forks the weekend I cloned it. That is not a knock, every repo starts there, but you should know you are early, not late.

So why would you pick it over the local-first option? Because you get a production-grade Next.js app with hosting, a database, auth, and custom domains already wired together, without you standing up Supabase and Vercel and an email provider yourself. And because the whole frontend is yours to rebrand and embed, which matters if you are an agency and not a hobbyist.

If you want a second truly local-first option to compare, bolt.diy from the StackBlitz crew is bring-your-own-key and worth a look. And if you want the full head-to-head across the open source field, Builderdex ran a proper open source Lovable alternative comparison covering Dyad, Open Lovable, Reflex, and this repo, with the trade-offs laid out axis by axis.

My short version: choose Dyad if you want local-first, bring-your-own-model, and zero ongoing cost. Choose ai-app-builder-open if you want an ownable, embeddable, multitenant shell and you do not mind paying for the engine that fills it.

Would I keep it running?

For a throwaway prototype, no. I would open a local tool and stay offline.

For a base I planned to rebrand and hand to a client, yes, and this is where it got interesting. I spent a whole weekend last month pitting three hosted builders against each other, and none of them gave me the source in a shape I would actually ship. This one did, because the shell is just a Next.js repo I can read. When I rebuilt an old side project in a weekend with an AI builder earlier this year, the thing I kept wishing for was ownership of the tool, not just the output. This repo is the first one that scratched that itch.

The one concrete takeaway: treat "open source" as a claim about the code, not about the cost. Read the .env before you get excited. If the only variable is a hosted API key, you are looking at an open shell around a paid engine. Sometimes that is exactly the trade you want. Just make it on purpose.

FAQ

Answers below are also collected in the structured FAQ.