Nobody needs a second Adalo: a coding agent can write your one app directly, which beats rebuilding a drag-and-drop editor. What a prompt can reproduce is the data-driven core: collections with relations, list, detail and form screens described in a JSON file, end-user sign-in and a phone-sized runtime as an installable web app. A weekend gets you that. What stays behind is the visual canvas with its 200-plus components, push notifications, and the automated App Store and Google Play pipeline.
Before you buildAdalo's Free plan builds and previews apps with up to 500 records but publishes nothing. If you only need one specific app, asking your agent for that app directly is quicker than building a builder.
Build me a small no-code app generator to replace Adalo for one app of mine. Requirements: - Node.js 22 + TypeScript: a Fastify API and a React + Vite front end, installable as a PWA (vite-plugin-pwa). `npm start` serves the runtime at http://localhost:4890 and the editor at /editor. - App definition: one ./data/app.json holding collections (fields of type text, number, boolean, date, image, and one-to-many relation), screens and users. Keep the last 20 saved versions in ./data/versions/ with a restore button. - Storage: better-sqlite3 in ./data/app.db. When a field is added or renamed in app.json, apply the migration automatically and refuse changes that would drop data unless a flag is confirmed. - API: a generic REST API for each collection (list with filter, sort and paging, get, create, update, delete) validated with `zod` schemas built from the definition, plus file upload for image fields into ./data/uploads/. - Screens: list, grid, detail, form and tabs, each bound to a collection. Buttons run actions: go to a screen, create, update or delete a record, set a field, or call a webhook URL. Filters may use the signed-in user, e.g. owner = currentUser. - Editor: form-driven panels, not drag and drop: add collections and fields, add a screen, choose its layout, bound fields and actions, reorder with up and down buttons, and preview in an iframe at phone width. - End users: email and password (`argon2`), session cookie, an admin flag, and a user list in the editor. No accounts for the editor itself beyond one password in .env. - Export every collection as CSV and the whole app as one zip. No accounts, no telemetry, local-first. - Out of scope: push notifications, payments, a drag-and-drop canvas, native store builds, marketplace. - README: reaching the app from phones over HTTPS (Tailscale or a VPS behind Caddy, since the PWA needs it), and how to wrap the runtime with Capacitor for a store build, noting that iOS needs a paid Apple Developer account and a Mac.
Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.
The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Adalo.
Add a CSV importer to the app generator in this folder. Requirements: - `npm run import -- <collection> <file.csv>` maps CSV columns to collection fields by header name, and prints unmapped columns and the rows it skipped with the reason. - Convert dates in ISO, US and European formats, and yes/no, true/false and 1/0 for booleans. - A --dry-run flag that changes nothing and a --map file for renamed columns. - Note in the README that relationship columns need a second pass, one collection at a time. - Update the README.
Add notifications to the app generator in this folder. Requirements: - A notification action type that, on a record create or update, sends email (`nodemailer`, SMTP in .env) or a web push message (`web-push`, VAPID keys generated on first run into .env). - The recipient is a field of the record that points at a user. - A per-user preference page to turn each kind off, and a log of sent notifications in SQLite. - Update the README, including that web push on iPhone only works once the PWA is added to the home screen.
Add a payment action to the app generator in this folder. Requirements: - An action type that creates a Stripe Checkout session for a price id taken from a record field, using the `stripe` library with STRIPE_SECRET_KEY in .env (test keys first). - A webhook route that verifies the signature and sets a boolean field on the paid record. - Show paid and unpaid state on the detail screen. - Update the README with how to test with Stripe's test cards.
A non-developer can ship a database-backed app to phones without writing code, and Adalo prices it flat with no usage meters. People pay for that one place that holds the editor, the database and the store publishing, even though the app can't leave it as code.
Estimate · Free on your own machine, about $5 a month for a small VPS. The build is token usage on your agent plan; store accounts, if you want native apps, are extra.
| Plan | Monthly | Annual, per month | What you get |
|---|---|---|---|
| Free | $0 | $0 | 0 published apps, unlimited test apps and screens, 500 records per app, 1 editor, hosted Postgres database, Ada AI assistant (beta). |
| Starter | $45 | $36 | 1 published app, 1 editor, 5 GB of data per team, custom domain, publish to the web, automated App Store and Google Play publishing, custom fonts, no Adalo branding. |
| Professional | $65 | $52 | 2 published apps, 5 editors, 25 GB per team, custom integrations, geolocation, push notifications, custom actions and formulas, app analytics, design versions. |
| Team | $200 | $160 | 5 published apps, 10 editors, 125 GB per team, priority support, Xano integration, app and collections API, version history, white labeling. |
| Adalo Blue | custom | — | Enterprise offering for existing businesses. |
Free builds unlimited test apps with 500 records per app and one editor, but publishes nothing.
Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: The drag-and-drop canvas and component marketplace, Automated App Store and Google Play submission.
About $45 a month on the Starter plan, $540 a year (checked 2026-10-19).
The drag-and-drop canvas and component marketplace; Automated App Store and Google Play submission; Push notifications, geolocation and Stripe payments as ready-made blocks; Hosted Postgres with backups and scaling handled for you; The Ada AI assistant, templates and community answers. If any of those matter to you, keep paying.
Yes: Saltcorn (open source), Appsmith (open source), ToolJet (open source).