Stacker review

Stacker is a hosted, no-code app builder that sits between business data and the people who need to use it. It connects to Airtable, Google Sheets, or SQL databases, then generates interfaces over tables, fields, and relationships. Teams use those interfaces to make customer portals, internal tools, and partner apps without building a frontend themselves.

The app layer includes layouts, filters, forms, buttons, and permissions. Stacker says it reads and writes connected data through two-way sync, so it is not just a read-only dashboard. Its server-side permission rules control which records and fields each logged-in user can see and which actions they can take.

Architecturally, this is a managed application layer over existing data, not a database replacement or a client library. The vendor describes a hosted service with custom-domain portals. That makes it a fit for teams whose source of truth is already in a supported system, but leaves the interface, access-control logic, and app behavior tied to Stacker.

The published build path is connector-driven: connect an Airtable base, Google Sheet, or SQL database in Stacker, then configure the generated app through its interface. The homepage describes choosing layouts, filtering and sorting data, adding forms and buttons, and inviting users. It also says connected data stays in sync both ways.

That is a different workflow from building against a documented developer API. The homepage does not name a REST API, SDK, programming language, CLI, or webhook integration. We would treat the supported integration surface as the listed data connectors and ask the vendor to confirm API and SDK support in its documentation before planning custom code around Stacker.

The product is aimed at building without developers, not at embedding a code-first framework into an existing application. Custom CSS and scripts are listed on Plus, but the homepage does not describe their interfaces or limits. Check the vendor’s docs for connector compatibility, SQL requirements, and the available controls before making Stacker a dependency in a production workflow.

Stacker has no free plan. The vendor offers a 30-day free trial with no credit card required. Starter costs $29 per month and includes one app, 50 external users, five internal users, 10 tables, and one portal with a custom domain. That is a constrained entry point for a live workflow: the external-user allowance and one-app limit are the first caps to check.

Plus costs $149 per month. It lists 100,000 records per app, unlimited external users, three roles per app, 20 tables per app, and custom CSS and scripts. The increase from Starter is substantial, so compare its record and role limits with the actual data model before moving a process onto the platform.

Enterprise pricing is custom and includes SSO, SQL and Salesforce connectors, unlimited roles, tables, and apps, plus a dedicated account manager and custom SLAs and security review. Starter and Plus are billed monthly; annual pricing is not published. The pricing details do not list overage fees or add-ons, so ask the vendor how it handles usage beyond plan limits.

Stacker is presented as a hosted service for building and sharing apps; the vendor does not publish a software license or state that the product can be self-hosted. We would not assume access to source code or an on-premises deployment. Ask the vendor directly about hosting options and contractual access to the application and its configuration.

The homepage says data stays in Airtable, Google Sheets, or the connected database, while Stacker reads and writes it. That keeps the underlying records in the connected source, but it does not establish an export path for Stacker-built pages, permissions, or workflows. The vendor does not publish details about exporting those app definitions.

Migration would likely involve recreating the interface and permission model in another tool or custom application. Before building a critical process, confirm how to retrieve records and app configuration, and whether Stacker offers a transition or export process.

Stacker says it enforces permission rules server-side and is SOC 2 Type II certified. Those are useful starting points for customer-facing portals, but teams should still review the vendor’s security materials, access-control behavior, and data-processing terms against their own requirements. Enterprise includes SSO, a security review, and custom SLAs; the vendor does not publish those terms as standard plan limits.

Plan caps can affect a live app: Starter allows one app, 50 external users, five internal users, and 10 tables. Plus lists 100,000 records per app and 20 tables per app. The vendor does not publish rate limits, uptime figures, performance guarantees, or overage handling in the published plan details. Ask what happens when a record or user cap is reached and what SQL connector behavior is supported.

The product’s dependency on connected data sources also makes connector behavior a production concern. Confirm sync timing, error handling, backup responsibilities, and recovery procedures with the vendor before making Stacker the only operational interface to important records.