Zite Database

Operator's take

If your team database is on a per-seat plan, you already know the shape of the problem. The bill tracks how many people can open the thing, not how much the thing is worth. Half those people update one field a week. Zite Database's whole bet is on charging for a different axis: unlimited users on every plan, including free, with the meter running on how many records you store and how much automation you fire. For an ops team that keeps buying seats for people who barely touch the base, that arithmetic lands before any feature comparison starts.

Underneath the spreadsheet view it's Postgres, which is the part that matters once your data stops being a list. Relations behave like relations rather than like lookups bolted onto a grid, and the vendor pitches millions of records with real rate limits. You get configurable views, department-level permissions for sharing across teams without exposing everything, a REST API, and native paths into Zapier, Make, and n8n. It also sits in a suite: Fillout collects the data, Zite Database holds it, and Zite Apps puts a front-end on it, all under one account. That's a genuinely short distance from "form submission" to "internal tool," and it's the strongest argument for adopting the stack rather than the single product.

The catch is what "Postgres" is doing in that sentence. It describes how Zite built the thing, not a database you can point your own tools at, and the supported way in and out is the REST API like any other SaaS. Whether a direct connection string is available on any plan isn't documented publicly. So the honest read is that this buys you relational behaviour and seat-free pricing, not ownership of the store — and if your reason for shopping is that you want to hold your own database, this isn't the tool that does it. The real ceiling is records, not people: 5,000 on free, 100,000 on Pro, 250,000 on Business. Price the record count you'll hit in eighteen months, not the one you have now, and the decision usually makes itself.

What it's good at

• Pricing that ignores headcount — unlimited users, editors, and portal guests on every tier including free. Paid plans are $15/month (Pro) and $55/month (Business), billed annually, priced per workspace rather than per person.
• Relational data that holds up — Postgres underneath, so linked records and complex relations behave properly rather than degrading as the base grows.
• Permissions granular enough to share across departments — access controls aimed at letting sales see sales without seeing payroll.
• A short path from form to database to app — Fillout for collection and Zite Apps for the front-end, same account, no connector to maintain.
• Automation that plugs into what you run — REST API plus native Zapier, Make, and n8n integrations, with 1,000 to 50,000 workflow runs per month depending on tier.

What it's not

• Not a database you own — it's a managed store reached through an API. If the goal is holding your own Postgres and renting only the interface, look at NocoDB Business or a self-hosted Teable instead.
• Not somewhere to put unbounded data — 250,000 records is the top documented tier, so high-volume logging or event data will outgrow it.
• Not a fit if you already have a database — Zite works on data living in Zite (or in Airtable, Google Sheets, or an upload); there's no external Postgres, Supabase, or MySQL connection.
• Not the mature ecosystem — Airtable has a decade of templates, integrations, and hireable experts. This doesn't, and that gap is real when something breaks on a Friday.
• Not a separate purchase — it's bundled into Zite's plans rather than priced on its own, so evaluate it as part of the suite rather than head-to-head on database features alone.