Noloco Review: AI App Builder, Pricing & My Test Results

Noloco is a no-code builder for portals and internal tools: tables of data, pages on top of them, roles, and workflows. Its AI builder, Nola, builds those from a chat. It is a private company with its own hosting, and the apps run on noloco.co addresses.

This was the free sign-up. A new workspace gets a 14-day trial of the Build plan, with no card, and the free credits: 30 a month plus 5 a day. Free on its own allows 2 user roles, 2,000 rows and 100 workflow runs, and Build is $79 a month.

Every number here comes from my own tests and my own monitors. I tested on the free sign-up, with its Build trial and free credits. I never entered a card, and I say below what the free plan itself would have stopped. These are the tools I used:

Noloco has a Free plan with 30 credits a month plus 5 a day, then $79 Build for 250 credits and the features this app needed: more than two roles, a custom domain, public apps and 5,000 workflow runs. Prices read on 27 October 2026, monthly view. Billed yearly Build is lower.

Noloco plan page: Free at $0 with 30 monthly credits, 50 active clients, 2 user roles, 2,000 rows, 100 workflow runs and Noloco branding and domains marked unavailable; Build at $79 with 250 credits, unlimited user roles, 25,000 rows, public apps, custom branding and custom domains

The free plan could not run my app: it has two roles and the app has four, so I stayed on the trial rather than switch and take the live app down. What a switch would do to the app, I did not test.

In total I paid nothing. The app, with all twelve changes, used about 18 of the 35 free credits. The first working version used about 6, and the changes about 12.

Noloco Billing and Usage page: plan usage with 20 of 5,000 workflow runs and 17 of 25,000 records, 6 of 10 team seats, credit usage of 17.88 over the last 30 days, and the banner Enjoy your free Build trial with 14 days left

A busy studio would need Build at $79 a month. I did not test what 1,000 bookings a month would cost; the Free plan allows 100 workflow runs, and each booking runs two.

Noloco's builder made the app, but not in one go. The brief is 1,689 characters and the chat box takes 1,000, so I attached it as a text file. Nola built the tables and rules, then stopped with 'Something went wrong', and I had to reload the page and tell it to continue. A second prompt set up the roles and credits. The app was live 44 minutes after the brief, in three prompts.

Noloco builder with the Nola chat on the left showing the last answer, and the finished Fitting Room app on the right in a green theme, with Class timetable, My bookings, All bookings, Ask the studio, Members, About and My waiting list in the menu

I ran the checks after it was live. Four approvals were needed along the way, such as creating the first classes.

A 4: under 90 minutes and 15 prompts, but not under 30 minutes. The error and the second fix are in the time.

Mostly: 20 of 24 checks passed. Booking, cancelling, the capacity rule, My bookings, the coach's list and the Ask the studio form all work, and the pages hold only the brief's facts. Six more checks, the payments and the two emails, need keys that are yours, so I left them out.

Noloco test app live Class timetable for a member: a Class card per row for Power Reformer, Mat Flow and Reformer Basics, each with start time, days, duration, instructor, capacity, spots left and the $24 drop-in price, and an Instructor filter

Four failed. A member with no credits is not told to buy a pass; the Book button just vanishes. The admin cannot delete a class in the app. The bookings CSV puts the member's name where the email should be. And the owner's name and the $95 pass appear nowhere in the app.

I ran all twelve changes, one prompt each, and nine worked first time. Two worked in part: the phone number is on the admin's list but not on the sign-up form, and the colour is green with no cream. The admin-only export could not be done, because Nola cannot set a button's visibility by role.

Noloco test app admin All bookings page in dark mode: ten bookings with class, names, a Member email column that shows names, session date, Booked or Cancelled status, one ticked Attended box and an Export CSV button

The planted bug went as it should: Nola removed the credit give-back when I asked, and when I called it a bug it said it was not one and put it back. It answered one question before the capacity change, and it was open about what it could not do.

Publishing was quick, a few seconds, but the app stays private until you switch on Live Mode. It goes live on a noloco.co address with a 'Powered by Noloco' label. A custom domain is a Build feature.

The weak spot is speed: the page is heavy and the main content took about sixteen seconds on a simulated phone. The timetable has no sideways scroll at phone widths, but the label overlaps the logo.

Every day I also run the Noloco speed test and the Noloco security check on the test app, so a later change shows up.

A review tells you what happened on one day. This tells you what happens every day after. I check the test app every five minutes for thirty days, from one fixed place.

Noloco hosts the app, and it stays up as long as the workspace does. The trial ends on 10 November 2026, so the record will show whether the app survives the move to the Free plan.

Every check so far is on the Noloco uptime record.

Noloco test app log-in page showing Use your password to sign in, a Password box, a Sign in button, Forgot your password and Powered by Noloco

Both of my attacks were blocked. Asking for another member's bookings returned only my own rows, and the admin-only delete of a class answered 'You do not have permission to do this'. So did changing a class and creating an order to give myself credits.

Sign-up logs you straight in with the default User role, and only the builder can make an admin. Support told me Team Admin is for the team and is assigned in the builder, not chosen on sign-up. That is the right rule.

The weak spot is page visibility. Nola cannot set it by role, so the admin pages and an Export CSV button show in every menu. A member sees only their own rows, but the doors are open. A seventh booking sent straight to the server was accepted for a moment, then cancelled by a workflow.

The password reset and the magic-link sign-in both emailed within seconds.

Almost: five of six data checks passed. Bookings and the Ask the studio form wrote records. They survived reloads, more than ten publishes, the colour change and the dark mode, and the admin could filter, edit and, in the data panel, delete them.

Noloco test app admin All bookings page in dark mode: ten bookings with class, names, a Member email column that shows names, session date, Booked or Cancelled status, one ticked Attended box and an Export CSV button

The CSV is the miss: it downloads, but the 'Member email' column holds the member's name, because a linked field exports as a name and an ID. A user I did not create, 'Jane Blogs', also appeared in the member list with the Team Admin role.

Noloco workflow run that failed at Email member confirmation with the message Email address not verified: this app cannot send emails until its owner has verified their email address

I did not run payments, because Stripe and email need keys that are yours to supply, and Noloco has no payment feature of its own. Nola said a Stripe Payment Link button is possible, with an outside tool such as Zapier or Make to create the order. The six checks that depend on payments and emails are left out, and this test is not graded.

The emails Noloco sends itself did arrive within seconds: the booking confirmation, the sign-in link, the password reset and the waiting-list position. Two things went wrong first. Until I verified the builder's own email address, the workflow's emails failed with 'Email address not verified'. After that the member's emails sent, but the notification to the studio failed every time with 'Email rate limit exceeded'.

You can take your data out, but not the app. Any table view can get an Export button that downloads a CSV, and the data panel exports each table. Noloco's support wrote: 'We do not provide a native feature to export your entire app's configuration or the underlying code as a package.'

The terms say the data is yours. Section 7, last updated on 26 April 2022, reads: 'You retain all right, title, and interest in and to your Direct User Content.' The app itself stays on Noloco, so moving means rebuilding.

I sent Noloco's chat the three standard questions. A bot answered in a minute. Then a person, Pranay, joined about twenty minutes later and answered all three. Team Admin is not something a sign-up can choose. The export gives a CSV and no app or code. On the free plan there is nothing to cancel.

To delete the workspace you delete the apps first and then contact Noloco, who check the request. Because the account never paid, there was no cancel, no invoice and nothing to check afterwards. The trial ends by itself on 10 November 2026.

I have not yet read what other users say about Noloco, so this draft has no review scores. Read them before you decide.

If this were my studio, I would use Noloco when the app is mostly data with roles around it, and I would set the admin pages by hand in the Visibility tab before sharing the link. It built the booking rules, the capacity limit and the roles from one attached message, and the server refused every write a member should not make.

It suits teams who want a portal on top of their own tables and can pay $79 a month once they need more than two roles. It suits you less if you need payments inside the app, a cream-coloured theme the AI can apply, a fast page on a phone, or the app itself to leave with you. I tested on the free sign-up, so I did not see what the Free plan does to the live app after the trial.

The nine graded tests average 3.6 out of 5, and I rate Noloco 3.6. Build speed, the changes, data and support are strong. Ownership is the lowest, because only your data can leave.

See the Noloco test results and how I rate.