Softwr

Spreadsheets · head to head

NocoDB vs Stacker

NocoDB logo

NocoDB

Spreadsheets

Open-source no-code database platform with REST and GraphQL APIs

From
Free
Rated
-
Stacker logo

Stacker

No-Code

Permissioned portals over data that stays in Airtable, Salesforce or Postgres

From
On request
Rated
-

The short version

  • Only NocoDB has a free tier, so it costs nothing to try first.
  • Each has a real cost: NocoDB the free cloud tier is capped at 3 editor seats, 1,000 records and 1 GB of storage; Stacker there is no source export and no self-hosting, so leaving means rebuilding the entire interface and permission model elsewhere, even though the underlying records remain yours.
  • They diverge on capability: NocoDB covers REST API, Stacker covers Per-record permissions.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which NocoDB and Stacker actually diverge.

Attributes where NocoDB and Stacker differ
AttributeNocoDBStacker
Starting priceFreeOn request
Pricing modelfreemiumquote
Free tierYesNo
PlatformsCloud, Self-hosted, DockerWeb
CategorySpreadsheetsNo-Code
Founded2020Unknown

Identical on both: user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in NocoDB

  • REST API
  • GraphQL API
  • No-code database
  • Multiple SQL databases
  • Webhooks
  • Automation
  • Cloud support
  • Self-hosted support

Only in Stacker

  • Per-record permissions
  • External user portals
  • Live connection to the source
  • Page and layout builder
  • Workflow actions
  • Custom domains and branding
  • User onboarding
  • Role based navigation

What people use each for

The jobs each tool is most often brought in to do.

NocoDB

  • Self-hosting an open source alternative to a spreadsheet databasenot Stacker
  • Putting a spreadsheet interface over an existing Postgres or MySQL databasenot Stacker
  • Building internal tools on structured data with an APInot Stacker
  • Team bases with per-field and per-table permissions on the paid tiersnot Stacker

Stacker

  • Giving clients a login that shows only their own records inside an internal Airtable basenot NocoDB
  • Contractor or franchisee portals where each account must see one slice of a shared datasetnot NocoDB
  • Replacing a spreadsheet emailed to partners with a permissioned live view of the same datanot NocoDB
  • Putting a usable interface on a Salesforce or Postgres dataset for users who should never see the underlying systemnot NocoDB

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

NocoDB

  • The free cloud tier is capped at 3 editor seats, 1,000 records and 1 GB of storage
  • Records are the metering unit on cloud, so Plus covers 50K and Business 300K rather than scaling by seat alone
  • Row-level security, audit log retention and team hierarchy require the Scale tier
  • SCIM provisioning and air-gapped deployment are Enterprise only
  • The self-hosted Community edition is unlimited on records and seats but does without workflows, scripts and dashboards, which start at the paid self-hosted tiers

Stacker

  • There is no source export and no self-hosting, so leaving means rebuilding the entire interface and permission model elsewhere, even though the underlying records remain yours.
  • Performance is bounded by the data source, so an Airtable base near its row limit or an API under rate limiting produces a slow portal that no amount of Stacker configuration will fix.
  • Pricing distinguishes internal editors from external portal users, so a portal that succeeds by adding hundreds of light-touch external users can end up costing more than the internal system it fronts.
  • Custom logic is limited to the actions and conditions the builder exposes, so anything resembling a calculation engine or a branching multi-step approval hits a wall and needs an external automation tool bolted on.
  • It is a portal and CRUD tool by design, with no offline mode, no native mobile application and no real reporting layer, so it will not be the only system a growing operation runs.

Pricing, plan by plan

NocoDB

Free
  • Free (Cloud)Free
    • 3 editor seats
    • 10 commenter seats
    • 1 GB storage
  • Plus$12/month
    • Unlimited seats
    • 50,000 records
    • 20 GB storage
  • Business$24/month
    • Unlimited seats
    • 300,000 records
    • 100 GB storage
  • Scale$45/month
    • Minimum 3 seats required
    • 1,000,000 records
    • 150 GB storage

Stacker

On request
  • Stacker$undefined/month
    • Priced by workspace tier with caps on apps and users
    • External portal users charged differently from internal editors
    • Higher tiers add permission depth and support

Which should you pick?

Choose NocoDB if

  • You need rest api.
  • You want to start without paying.
  • You work on Cloud, Self-hosted, Docker.
  • You also want graphql api.

Choose Stacker if

  • You need per-record permissions.
  • You also want external user portals.

Questions people ask

Is NocoDB or Stacker better?
Neither clearly leads. NocoDB starts at Free and Stacker at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, NocoDB or Stacker?
NocoDB has a free tier; the other does not. Paid plans start at Free for NocoDB and On request for Stacker.
Does NocoDB or Stacker run on more platforms?
NocoDB runs on Cloud, Self-hosted, Docker. Stacker runs on Web.
Can I use NocoDB for free?
Yes. NocoDB has a free tier, so you can try it without paying. Stacker starts at On request.
What is NocoDB best used for?
NocoDB is most often used for self-hosting an open source alternative to a spreadsheet database, putting a spreadsheet interface over an existing postgres or mysql database, building internal tools on structured data with an api, team bases with per-field and per-table permissions on the paid tiers. Of those, self-hosting an open source alternative to a spreadsheet database and putting a spreadsheet interface over an existing postgres or mysql database are not what Stacker is typically brought in for.
What can NocoDB do that Stacker cannot?
NocoDB covers REST API, GraphQL API, No-code database, Multiple SQL databases. Stacker covers Per-record permissions, External user portals, Live connection to the source, Page and layout builder.

Answered from the vendors’ own pages

NocoDB: Is NocoDB free?

Yes, NocoDB offers a free cloud plan with 3 editor seats, 1,000 records, 1 GB storage, and 1,000 API calls per month. A free self-hosted Community edition with unlimited records and seats is also available.

Source
Stacker: Where does my data live?

In the source you connect: Airtable, Salesforce, HubSpot, Google Sheets or your own Postgres. Stacker reads and writes to it rather than becoming the system of record.

NocoDB: How much does NocoDB Plus cost?

NocoDB Plus costs $12 per seat per month (billed annually) or $15 per seat per month (monthly). For unlimited seats, it costs $108/month annually or $180/month monthly. Plus includes 50,000 records, 20 GB storage, and 100,000 API calls per month.

Source
Stacker: Can I export the app if I cancel?

No. The data stays in your source system, but the interface, permissions and workflows are Stacker configuration and do not come with you.

NocoDB: What is the difference between NocoDB Plus and Business plans?

Plus ($12/seat annual) includes 50,000 records and 100,000 API calls per month. Business ($24/seat annual) includes 300,000 records, 1,000,000 API calls per month, external database connections, SAML SSO, and table/field permissions.

Source
Stacker: Is it suitable for hundreds of external users?

Technically yes; check the pricing arithmetic first, because external portal users are charged separately and that is where the bill grows.

NocoDB: Can I self-host NocoDB for free?

Yes, NocoDB's Community edition is free for self-hosting. It includes unlimited records, storage, and seats, with all core features including webhooks and 6 view types.

Source
Stacker: Will it replace Airtable?

No, it sits in front of Airtable. If the base itself is at its limits, the fix is moving the data to Postgres rather than changing the portal.

Share

Related pages

Other head to heads