Macaron playbook

Base44 Review: App Builder, Plans and Hosting

Base44 can turn a prompt into a hosted app with backend services, but the first useful test is a narrow workflow with one user role and a clear permission boundary. Estimate message and integration credit use, then check app visibility and data access before sharing the result.

By MacaronOperated by MINDAI PTE. LTD.

What Is Base44 and What Can You Build With It?

Base44 generates apps and websites from natural-language requests. Its scope includes interface structure, logic and supporting infrastructure. Start with one user flow, such as adding an item and returning to edit it, instead of asking for a large marketplace before deciding what successful use looks like.

Public website check. In an anonymous pricing-page check, switching Yearly to Monthly changed Builder from $40/month billed annually to $50/month, Pro from $80 to $100, and Elite from $160 to $200. A full year of Builder is $480 on the annual rate versus $600 across twelve monthly payments before taxes or promotions; compare that $120 difference with the commitment and current checkout terms. Official source. Click-through screenshot.

What happened in one free-account prototype

On November 5, 2026, an AI agent asked Base44 to make a small reading list with title, author, status and notes fields, without external integrations. The builder created five fictional seed books. We added Sample Book A as a sixth record, then changed its status from Reading to Done and its note to Marked done during fictional prelaunch test. The visible Reading count fell from 2 to 1, and the Done count rose from 2 to 3. Filtering for Done returned three records. After a preview refresh, the six-book list and changed record still appeared. This checks a narrow add, edit, filter and persistence path; it does not establish a reliable production data model.

The preview displayed PRIVATE, while Dashboard → Overview showed App Visibility: Public; the Private choice was disabled on this free account and labeled for Starter or higher. Dashboard → Data → Book → Permissions displayed Creator Only controls and a role=admin user-property check. These were settings we read as the owner, not proof of what another user could access. The app's public address displayed isn't available yet with a prompt for the admin to publish it. We did not publish it or test a second identity. Before using a list for private records, check the published route and record-level permissions separately with a non-owner test account.

Built-In Backend and Hosting: Less Initial Setup

Authentication, data storage, hosting and publishing are part of Base44's product proposition. Those included building blocks reduce initial setup. They do not establish that a generated app has correct permissions, handles invalid inputs or is ready to hold confidential records. Try both the owner and ordinary-user paths.

A documented access review happens inside Base44. In Dashboard → Overview → App Visibility, choose who can open the app; the guide reserves Private apps for paid plans. Then inspect the actual records in Dashboard → Data → the relevant table → Permissions → Edit. Access to the app and permission to read, update or delete a record are different controls.

For a personal reading list, the documentation's Creator Only rule can restrict Read, Update and Delete to the record's creator when login identifies that person. Save the rules and use Test Permissions in preview before sharing. Publishing and copying a link do not establish that the recipient has access or that data rules are correct. We inspected the setting and table rules in a fictional prototype, but did not run an ordinary-user permission test or publish it.

Test visibility and record permissions as separate gates

Base44's access guide distinguishes opening an app from reading or changing its records. For a private reading list, a preview that looks correct to the owner is not enough:

Gate	Setting or check	Failure it can expose
App entry	Dashboard → Overview → App Visibility.	The wrong audience can open the app, or the intended person cannot.
Record access	Dashboard → Data → table → Permissions → Edit, then Test Permissions.	A non-owner can read or change a record that was meant for its creator.
Export and continuation	Builder-level GitHub sync is a code route, not a full service migration.	Data, authentication or hosting dependencies remain after code export.

Check the second gate with an ordinary-user identity before sharing real records. Our prototype was built and inspected only as its owner; it was not published or tested under a second identity.

Limits: Debugging, Credits and Ownership Questions

The current pricing table lists Free at 25 message credits and 100 integration credits per month. Starter lists in-app code edits and custom-domain connection; Builder adds the listed GitHub integration. Building/editing messages and the finished app's integration actions are separate usage budgets. A daily allowance was not independently confirmed from this current table, so no fixed daily limit is asserted here.

Base44's terms say the company does not claim ownership of Customer Data, including listed code/materials, except for pre-existing company intellectual property in generated output. Ownership does not remove the platform licenses in those terms. The GitHub documentation describes two-way code sync for Builder or higher, initiated by an app owner. That gives a documented export/development route, not proof of a complete independent migration of hosted data, authentication and services. Review those dependencies before treating exported source as a finished self-hosted deployment.

A personal prototype with one owner is a reasonable Free-plan evaluation; a custom domain points to the documented Starter feature, while GitHub sync points to Builder or higher. Choose by that dependency, then by editing and integration usage. For a multi-user app, make ordinary-user access and export requirements part of the acceptance decision before paying. An attractive first screen answers neither question.

Captured public states

Base44 monthly billing state.

Base44 vs Macaron: Full Apps or Personal Mini-Apps?

Open Macaron chat to adapt the request below. Review account access and plan conditions before creating a tool.

Budget for the workflow after the first prompt

Before choosing an app builder, list the login, data and external-service actions the finished app needs. Building messages and integration actions are separate budgets. A personal reading list can be evaluated with an add/edit task; a public multi-user app also needs independent permission and deployment checks.

Sample request

"Build a personal reading tracker with an entry ID, title, unread/reading/finished status, next action and notes, where add and edit preserve the ID, unfinished filtering changes visibility without deleting records, and two books with identical titles remain separate entries."

Suggested fields: Title; reading status; next action; notes; unfinished-items view.

Proposed checks with fictional data:

Adapt the request in Macaron using only fictional, non-identifying data.
Check each input and edit below against the expected result.
Correct the stated behavior before entering personal information; use a manual record if the draft cannot preserve it.

Fictional input or edit	Expected result to check	If it differs
IDs B1 and B2 share a title; B1 is finished and B2 unread	Unfinished view contains B2 only; both saved records remain	Separate title matching from unique record identity
Edit B2's note, then clear and reapply the filter	B2 retains the edit and B1 is still retrievable	Check saved data before judging the visible screen
Try to reuse ID B1 for another new book	Reject the duplicate or require a new ID	Do not silently overwrite the earlier book

Illustrative build sequence: describe the smallest reading workflow, review the generated screen, add a sample book, then ask for a new status option.

The reading-tracker example has two separate checks: a filter changes which books are visible, while an edit changes a saved record. If finishing a book removes its saved entry, the filter has been implemented as deletion and the workflow has failed, however convincing the screen looks.

Which workflow fits your needs?

Need	Base44	Macaron example
Main purpose	An app-building platform with backend and publishing	A conversationally specified personal mini-app
What you work with	App structure, access rules and deployment decisions	A focused daily-life workflow refined by follow-up requests

Generated interfaces and calculations still need checking. Neither this example nor a public sharing feature establishes that a tool is suitable for confidential records or production business operations.

Next step

Explore Macaron for a personal tool you can adapt to this task.

Scope and source notes

How this review was checked: Review for Macaron, prepared with AI. An AI agent built and edited an unpublished Base44 reading-list prototype with fictional records in a new free account. A second user's access, published deployment, paid features and the proposed Macaron mini-app were not tested.

Review scope: Base44’s hosted app-building platform, including building and integration allowances. The Macaron comparison is a personal reading workflow, not a claim of production readiness.

Sources reviewed: last updated November 5, 2026. Product details may change; confirm current information with the provider.

Source	Supported scope and limitation
Base44 Plans & Pricing \| Start Free, Scale as You Build	Published plan, feature or billing conditions; account offer and region may differ
Terms of Service \| Base44	Provider terms and stated access/data boundaries; not an independent compliance audit
GitHub Integration - Base44 Support Documentation	Documented workflow or access conditions; not results from this review’s own test
Choosing who can access your app - Base44 Support Documentation	Dashboard visibility, paid Private scope and sharing/access distinction; not a production build
Managing data permissions - Base44 Support Documentation	Per-table action permissions, Creator Only and Test Permissions in preview; not tested security

Corrections: contact@macaron.im.

FAQ

Does Base44 include a backend?

Yes. Its product includes generated authentication, storage and supporting app logic, alongside hosting.

Are message credits the same as integration credits?

No. Treat them as separate allowances when estimating how the planned workflow will use a plan.

Does a generated login prove that permissions are correct?

No. Test what each user role can actually see and change.

What is a sensible first Macaron mini-app request?

A small reading list with explicit fields and an add/edit workflow is easier to review than a broad app request.

How should I test a status edit in the Macaron reading tracker?

Create two fictional books with separate IDs, change one from reading to finished and reopen the list. Its note and next action should remain attached to that book; this proposed check does not establish public hosting or shared-user permissions.

Does the Macaron example inherit Base44 hosting or permissions?

No connection, publishing flow or shared-user permissions were tested for that mini-app. Its proposed reading records should be checked with fictional data first, and any real sharing or privacy setting must be verified in the environment where the tool is actually built.