> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/account/pricing.md). # Pricing Noloco has three plans — **Free**, **Build**, and **Enterprise** — and you can pay monthly or annually. You can see current prices on the [pricing page](https://noloco.io/pricing). Every app starts with a **14-day free trial of Build**, so your team can evaluate the full feature set — workflows, permissions, automations, integrations, and building with [Nola](/nola.md). No credit card is required to get started. {% hint style="info" %} **Already a customer?** If you subscribed before these plans, your app stays on your existing plan with the same prices and limits — see [Legacy Plans](/account/pricing/legacy-plans.md). {% endhint %} ## The plans ### Free — $0 For learning Noloco and building your first app. * **AI credits:** 30 per month, plus a small daily allowance * **Records:** up to 2,000 * **Workflow runs:** 100 per month * **Seats:** unlimited team members, plus 50 client users * **Data:** native [Noloco Tables](/data/collections.md) only * Unlimited apps, with Noloco branding ### Build — $79/month For teams building client portals and internal tools on their own data. * **AI credits:** 250 per month * **Records:** 25,000 included, expanding automatically as you grow * **Workflow runs:** 5,000 per month * **Seats:** 10 team members included, plus 1,000 client users * **Data:** connect external sources like [Airtable](/data/airtable.md), [SmartSuite](/data/smartsuite.md), [PostgreSQL](/data/postgresql.md), and more * Everything you need to run a professional app, with Noloco branding removed ### Enterprise — custom For larger teams and complex use cases that need higher limits, additional data sources, and dedicated support. [Contact sales](mailto:sales@noloco.io) to discuss your use case. {% hint style="info" %} For the full feature-by-feature comparison and current prices, see the [pricing page](https://noloco.io/pricing). {% endhint %} ## How pricing works Noloco's plans are broadly based on **how many people use your apps** and **how much data those apps hold**. Everything else — workflows, permissions, integrations, page types — is a feature of the plan rather than something metered separately. When you're choosing a plan, there are only four things you really need to weigh up: 1. **Team members** — the people inside your organization who use your apps. See [user types](#user-types). 2. **Client users** — everyone outside your organization: clients, partners, contractors, volunteers. 3. **Records** — your rows of data, counted together whether they live in [Noloco Tables](/data/collections.md) or sync in from an external source. 4. **AI credits** — how much building and editing you expect to do with [Nola](/nola.md). If you're not sure where you'll land, start on the trial. Usage is visible in [Billing & Usage](/settings/billing-and-usage.md) from day one, so you can size your plan against real numbers instead of guessing. ## User types An app **user** is anyone who accesses your app with an email address — an admin, a team member, a client, a partner, a volunteer, a contractor. Noloco divides users into two categories, **team members** and **client users**, and each plan includes a different number of each. Both categories are counted the same way: a user takes a seat once they **log into** one of your apps, and holds it until they're deactivated. Someone you've invited who has never signed in doesn't count toward your plan. {% hint style="info" %} If you have several apps in one [workspace](/account/workspaces.md), a user with the same email address is counted **once**, not once per app. {% endhint %} ### Team members A user is counted as a team member if any of the following are true: * They have the same email domain as the app creator or any app builder. * They have the same email domain as anyone in the app's workspace. * They have a team member or data admin role. ### Client users Everyone who doesn't fall into the team member category is a client user. In practice this is the audience for your [client portal](/solutions/agency-os/client-portal.md) — the people you're delivering work to rather than the people delivering it. On paid plans, client users are included in far larger numbers than team seats, because portals are typically wide and shallow: many people, each using the app occasionally. ### Deactivated users [Deactivating a user](/users-and-permissions/offboarding-users.md) is how you release a seat. The change takes effect from your **next** billing cycle — if they logged in during the current one, they're still counted for it, so deactivating partway through a month doesn't remove them retroactively. Their records and history stay intact, which is why deactivating is the right move when someone leaves — deleting them would take their data with them. ## Pay-as-you-go for extra users If you go past the number of users included in your plan, you don't have to jump to the next tier. Additional users are added automatically and billed per seat on top of your subscription. * You're notified in-app and by email as you approach and exceed your included seats. * Extra seats are charged at the end of your billing cycle, so the charge reflects your actual usage over the month. * Team members and client users are charged at different rates, since they're included in different quantities. Current per-seat rates are shown on the [pricing page](https://noloco.io/pricing). ## AI credits Building and editing with [Nola](/nola.md) — including [Canvas](/nola/canvas.md) pages — runs on **credits**. Every plan includes a monthly credit allowance, with more on higher plans, and the Free plan also gets a small daily allowance. On Build you can raise or lower your monthly allowance yourself from [Billing & Usage](/settings/billing-and-usage.md), and larger allowances cost less per credit. For how credits work — what uses them, what's free, and how allowances reset — see [Credits & Usage](/nola/credits-and-usage.md). ## Data & records ### Which data sources can I use? Noloco builds your app from data you already have, so the data source is the first thing you choose. On the **Free** plan you can use [Noloco Tables](/data/collections.md), our own hosted database. **Build** and **Enterprise** add every external connector: * [Noloco Tables](/data/collections.md) * [Airtable](/data/airtable.md) * [SmartSuite](/data/smartsuite.md) * [Google Sheets](/data/google-sheets.md) * [Xano](/data/xano.md) * [PostgreSQL](/data/postgresql.md) * [MySQL](/data/mysql.md) * [Supabase](/data/supabase.md) * [HubSpot](/data/hubspot.md) * [Stripe](/data/stripe.md) You can connect more than one source to the same app, which is how most teams bring scattered systems into a single tool. ### Record limits Every plan includes a number of records, counted across all of your data — both rows stored natively in Noloco Tables and rows synced in from an external source. | Plan | Records | When you reach the limit | | ---------- | --------------- | --------------------------------------------------------------------- | | Free | 2,000 | Record creation and syncing are blocked immediately | | Build | 25,000 included | Records expand automatically, billed per block up to the plan ceiling | | Enterprise | Custom | Agreed with your account team | On **Build**, exceeding your included records doesn't break your app. Additional records are purchased automatically in blocks so new data keeps syncing and your users keep working; the charge appears on your next invoice. Very large data volumes move to Enterprise. On **Free** there's no tolerance — once you hit the limit, new records can't be created and external syncing pauses until you're back under it. {% hint style="info" %} Syncing is the same speed on every plan. Sources like Airtable and SmartSuite sync live, while others sync on a schedule — see [Syncing](/data/data-overview/syncing.md) for how each behaves. {% endhint %} ### What if I exceed my record limits? You're notified in-app and by email as you approach and exceed your limits. From there you can reduce the records you're storing, or move to a plan that fits. For the practical options — trimming synced tables, archiving history, reducing what you sync — see [Plan Limits and Usage](/settings/plan-limits-and-usage.md). ## Workflow runs Each time one of your [workflows](/workflows/workflows.md) is triggered counts as one **run**. What matters is the trigger, not the size of the workflow: * A workflow with ten actions is still one run. * A run that fails still counts. * Saving or editing a workflow doesn't count — only executions do. * Disabled workflows don't run, so they don't count. | Plan | Workflow runs per month | When you reach the limit | | ---------- | ----------------------- | ----------------------------------- | | Free | 100 | Workflows stop executing | | Build | 5,000 | Runs continue, billed as an overage | | Enterprise | Custom | Agreed with your account team | Only the Free plan stops workflows outright. On paid plans your automations keep running and the additional runs are charged as an overage. ## Overages ### What is an overage? An overage is an additional charge applied automatically when you go past a metered limit during your billing cycle. Overages apply to **workflow runs** and **file storage**; records and seats are handled by the pay-as-you-go mechanisms described above. ### How are overages calculated? Usage is totalled across your billing cycle and charged in arrears, alongside your next subscription invoice — you only pay for what you actually used. You can watch your usage against every limit in [Billing & Usage](/settings/billing-and-usage.md), and you'll be emailed as you approach and exceed a limit. Current overage rates are on the [pricing page](https://noloco.io/pricing). {% hint style="info" %} On **annual** billing, overages are still charged **monthly** as they're incurred. Add-ons such as additional records are pro-rated across the remainder of your annual term. {% endhint %} ## Billing options ### Monthly or annual You can pay monthly or annually on any paid plan. Annual billing is cheaper per month; monthly gives you more flexibility to change plan. **Monthly billing.** At the end of each billing cycle we review your usage — seats, records, workflow runs, file storage — and update your subscription accordingly. If your usage is steady, nothing changes. If you've gone past what your plan includes, you're notified by email and in-app, and the difference appears on your next invoice. **Annual billing.** You're billed for the next 12 months up front, based on the plan you choose. We still review usage at the end of each month, so growth in seats or records is billed as it happens rather than waiting for renewal. If you change plan mid-term, you're charged a pro-rated amount for the difference through to the end of your year. ### Changing or cancelling your plan You can change your plan, switch between monthly and annual, or cancel from the billing page in your app — **Settings** > [**Billing & Usage**](/settings/billing-and-usage.md) > **Manage billing**. Billing details, invoices, and payment methods are handled through Stripe's secure portal. ## Your free trial Every new app begins on a **14-day trial of Build**, with the full Build feature set unlocked. During the trial your AI credits are provided at the Free-plan level. When the trial ends, you can continue on Build, choose Enterprise, or move to the Free plan with reduced limits. No credit card is required to start. ## Support Every Noloco customer can reach our team, join the community, and use our learning material. Open the **Support** menu from Build mode in your app and click **Ask a question** — our AI support bot answers immediately, and you can ask to speak to an agent, Monday to Friday. Alongside that you have the [Community](https://community.noloco.io/), these guides, the [Noloco Academy](https://academy.noloco.io/register), and regular [webinars](https://noloco.io/webinars). See [Support](/settings/support.md) for everything available from inside your app. **Enterprise** customers get additional support arranged with their account team, including a named point of contact and agreed response times. [Contact sales](mailto:sales@noloco.io) to talk through what you need. ## Frequently asked questions
Are team members and client users counted differently? Yes. Each plan includes separate allowances for the two, and they're charged at different per-seat rates once you exceed them. * **Team members:** users with the same email domain as the app creator or anyone in the app's workspace, or users with a team member or data admin role. * **Client users:** everyone else.
How are users counted if I have several apps? Users are counted uniquely at the account level. The same email address using three of your apps is one user, not three.
Does someone who never logs in take a seat? No. A seat is taken when a user first logs into one of your apps, so you can invite people freely without being charged for anyone who never signs in. Once they have logged in, they hold that seat until you [deactivate them](/users-and-permissions/offboarding-users.md) — it isn't released by them going quiet for a month.
Are overages charged automatically? Yes, at the end of your billing cycle. You're notified as you approach and when you exceed a limit, so there's no surprise on the invoice.
How do I know how much I've been charged? Your invoice at the start of the next billing cycle itemizes any overage and pay-as-you-go charges from the previous period. Live usage is always visible in [Billing & Usage](/settings/billing-and-usage.md).
What happens when my free trial ends? You can continue on Build, move to Enterprise, or drop to the Free plan with reduced limits. Your app and data aren't deleted — the Free plan's limits simply apply.
How do I change or cancel my plan? From **Settings** > [**Billing & Usage**](/settings/billing-and-usage.md). Choose the plan you want and confirm, or open **Manage billing** to cancel.
Can I use a custom domain and remove Noloco branding? Yes on paid plans. See [Custom Domain](/settings/custom-domain.md) for setup. During a trial the "Powered by Noloco" branding stays visible; it's removed once you're on a paid plan. To send workflow emails from your own address, see [SMTP Emails](/integrations/smtp-emails.md).
Can I install a Noloco app on my phone? There's no native mobile app, but every Noloco app can be installed as a [Progressive Web App](/settings/progressive-web-apps.md), which gives your users an app-like experience on their device.
How do I delete my Noloco account? First delete your apps from your [dashboard](https://portals.noloco.io) — hover over an app, open the overflow menu, and click **Delete**. This permanently removes that app's configuration and data. Then contact support () to have your user account deleted, mentioning that you've already deleted your apps.
## More on pricing & billing {% content-ref url="/pages/BVklecllqO5Lq2mrL6Ab" %} [Legacy Plans](/account/pricing/legacy-plans.md) {% endcontent-ref %} {% content-ref url="/pages/VF06FPep5ovuLiftwC6a" %} [Credits & Usage](/nola/credits-and-usage.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guides.noloco.io/account/pricing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.