Free seats. Priced by what you use.

No, and we never will. Seats are unlimited on every tier including Free. Charging a team to let more of its people read its own numbers is how analytics got expensive; value should scale with data volume, not headcount.

None. Experiments, session replay, feature flags, surveys, embedded analytics, scheduled deliveries, pipelines, connectors, teams and role-based access all work on Free. Paid tiers buy volume, retention, query priority and support — never capability.

Free defaults to a hard cap rather than a bill: ingestion is rejected with a clear error once an allowance is spent, after a small grace margin. Adding a card converts the account to pay-as-you-go at list rates, and per-dimension spend caps stay available on every tier.

An organization is an isolated workspace: its own members, datasets, dashboards, pipelines and quality rules. One account can hold several — useful for consultancies delivering governed analytics to more than one client.

Yes. Tables are stored as standard Parquet files with a Delta Lake transaction log — an open, documented format with full version history. Exporting means copying files, not negotiating a migration out of a proprietary store.

The shape differs more than the numbers: AZ-Five never charges per seat and never gates a feature, so the bill follows data volume rather than headcount or plan tier. We publish honest side-by-side pages — az-five.com/vs/posthog, /vs/amplitude, /vs/metabase, /vs/databricks and /vs/looker — that state where each tool is stronger.