AppSheet Pricing 2026: Plans, Free-Tier Limits & the Per-Seat Math

AppSheet pricing in 2026 is free to build and test for up to 10 users, then $5/user/month (Starter), $10/user/month (Core), and $20/user/month (Enterprise Plus), plus a flat $50/month per app (Publisher Pro) for public apps with unlimited users. The free tier is a prototyping plan, not a free production plan — the 10-user cap is what forces the upgrade.

The number that matters more than the sticker price is per user, per month, forever. AppSheet is licensed by seat, so your bill scales with headcount, not with how much work the app does. For a 5-person field team that math is trivial. For a 30-person internal tool running for two years, it's the whole decision — and it's where a one-time, owned Apps Script build starts to look very different on the spreadsheet.

This guide is the pricing breakdown we wish existed when we were scoping these projects: the real plans, what the free tier actually includes, Core vs Enterprise Plus, and the per-seat math that tells you when AppSheet stops being the cheap option.

Prices are indicative and change. Everything below was confirmed against Google's official AppSheet pricing page at our last review (mid-2026), but Google adjusts these tiers periodically. Treat this as a map, not a quote — confirm the live numbers at about.appsheet.com/pricing before you commit budget.

Current AppSheet plans & prices (2026)

Plan	Price	Best for	Data ceiling
Free (build & test)	$0	Prototyping, internal POCs	≤10 test users
Starter	$5 / user / month	Small apps, basic automation	5 databases × 2,500 rows
Core	$10 / user / month	Most internal business apps	10 databases × 2,500 rows
Enterprise Plus	$20 / user / month	Large datasets, external data, governance	200 databases × 200,000 rows
Publisher Pro	$50 / month per app (flat)	Public, no-sign-in apps	Unlimited users

A few things this table makes obvious that the marketing pages soften:

• Core is the default, and you may already own it. Core ($10/user/month) is bundled into most paid Google Workspace editions. If your team is on Business Standard or Plus, you likely have AppSheet Core entitlement already — check before you buy seats separately.
• The jump from Core to Enterprise Plus is 2×, and it's not about app features so much as data scale and governance (more on that below).
• Publisher Pro is the only per-app price. Everything else is per-user. If you're building a public catalog or directory with no logins, the flat $50/app can be dramatically cheaper than per-user — but it only fits no-sign-in apps.

For how this stacks up against building the same thing in code (and against PowerApps), see the full AppSheet vs Apps Script breakdown. This post stays focused on cost.

What the free tier actually includes — and its limits

AppSheet's free usage is genuinely useful and genuinely limited, and the gap between those two facts trips up a lot of teams budgeting for a rollout.

What you get for free: full app-building capability. You can connect a Google Sheet, generate views, build forms, configure bots and automations, and test the whole thing — with up to 10 test users, no time limit. You can prototype indefinitely. For a solo builder or a 2-3 person team validating an idea, the free tier can carry you a long way.

Where it stops: the 10-user cap is the wall. It's not a feature limit you can work around — it's the line between "testing" and "production." The moment an eleventh real person needs to use the app, you're on a paid plan. There's no free production tier, no "free for small teams forever" plan like some SaaS offers.

The quieter limit — data ceilings. Even when you pay, the entry tier constrains the AppSheet database: Starter caps you at 5 databases of 2,500 rows each. For a contacts app or a small inventory that's fine; for anything that accumulates transactional history, you'll hit the ceiling and need Core (still 2,500 rows/database) or Enterprise Plus (200,000 rows) sooner than you'd expect. If your data lives in Google Sheets rather than the AppSheet database, Sheets' own limits apply instead — but the AppSheet-database row caps are a real planning constraint people miss.

If what you actually need is an unlimited-user internal tool that's free to run, that's not what AppSheet's free tier is. That's Apps Script, which runs at no per-user cost under standard Workspace quotas — different tool, different trade-offs, covered in the comparison post.

Core vs Enterprise Plus: who actually needs which

This is the most-searched pricing decision, and the honest answer is that most teams need Core, not Enterprise Plus — the 2× price gap is paying for scale and governance, not for a better app.

Choose Core ($10/user/month) if:

• Your data lives in Google Sheets or the AppSheet database and stays under a few thousand rows per table.
• You connect only to Google sources (Sheets, Drive, Calendar, Gmail via bots).
• You need standard role-based security, not org-wide governance.
• Email support is enough.

Core covers the large majority of internal business apps — request trackers, inspection forms, field logs, simple inventory, approval workflows. And because it's bundled with most paid Workspace editions, many teams effectively get it at no incremental cost.

You need Enterprise Plus ($20/user/month) when:

• Data scale pushes past Core's ceilings — Enterprise Plus lifts you to 200 databases of 200,000 rows each.
• External data sources matter: connecting to cloud databases, third-party APIs, or SaaS services (not just Google sources) is an Enterprise Plus capability.
• Governance is a requirement — team management, governance controls, and enhanced application security for a regulated or large org.
• You want machine-learning modeling and priority support.

A useful rule of thumb from the rollouts we've scoped: if you can't name a specific Enterprise Plus capability you need — external DB connection, 200k-row tables, formal governance — you're on Core. Don't pay 2× for headroom you won't use; you can upgrade later.

The hidden cost: per-seat math at scale

The trap in per-user pricing is that it's invisible at the demo and unavoidable at the all-hands. A $10/user/month app feels free when you and two colleagues are testing it. It doesn't feel free when payroll has added it to 30 people's accounts and it's still billing two years later.

Work a concrete example. A mid-size team standardizes on one internal AppSheet app — say a job/inspection tracker — on Core, 25 users:

Horizon	Cost on Core (25 × $10/mo)
Per month	$250
Per year	$3,000
Over 18 months	$4,500
Over 3 years	$9,000

That $4,500 over 18 months buys you the right to keep using the app — it's rent, not equity. When you stop paying, the app stops. And the bill grows with the company: every new hire who needs the tool is another $10/month, indefinitely.

Now compare the shape of the alternative. A one-time custom Apps Script build that does the same job is a fixed, one-off cost, runs free under standard Google Workspace quotas (no per-user, no per-row fee), and you own it outright in your own Google account — a one-time build you own rather than a subscription you rent. For a stable 25-person internal tool, the owned build frequently costs less than 18 months of seats and then keeps running at zero marginal cost while the AppSheet meter would have kept ticking.

This is the same logic we lay out for replacing rented SaaS with tools you own in Google Workspace: the cheapest automation is often the one running inside the Google account you already pay for, built once instead of rented monthly.

When AppSheet pricing stops making sense — the Apps Script crossover

To be fair to AppSheet — and credibility is the whole point of this post — the crossover isn't always in Apps Script's favor. Here's the honest decision line.

AppSheet stays worth the price when:

• You need offline mobile. This is the one capability Apps Script genuinely can't match. Field techs, warehouse pickers, delivery drivers with patchy connectivity — AppSheet caches data on-device and syncs later. If that's your use case, pay for AppSheet; the per-seat cost is buying something real.
• The team is small (under ~10–15 seats). Per-user pricing is cheap at low headcount, and the time-to-ship of no-code beats a custom build.
• The app changes constantly and a non-developer needs to reconfigure it weekly. Owning code is great until someone has to maintain it.

The math tips toward an owned Apps Script build when:

• 20+ users are on a stable internal tool — the per-seat fees compound past the one-time build cost.
• The horizon is long (a year or more). One-off cost vs. forever-rent: time is the variable that decides it.
• The logic outgrows no-code anyway — multi-step API integrations, custom calculations (FIFO costing, fuzzy matching, AI prompt assembly), jobs that run longer than a bot allows. If you're already dropping in Apps Script triggers to cover AppSheet's gaps, you're paying per-seat for a UI wrapped around code you could own end-to-end.

The cleanest framing: AppSheet is rent that buys you speed and offline mobile; an owned Apps Script build is a one-time cost that buys you zero marginal scaling. Pick rent for small, fast, mobile-offline. Pick ownership for large, stable, long-lived internal tools. Plenty of teams run both — AppSheet where its strengths earn the fee, Apps Script where the per-seat math doesn't.

If you're staring at a per-seat bill that keeps climbing, it's worth pricing the owned alternative before you renew. We scope these as fixed-price projects and can tell you honestly which side of the crossover your app is on — including when the answer is "stay on AppSheet."