We're still finalizing rates with our design partners, so there's no rate card to publish yet. Here's the honest shape of how pricing will work, and why it looks different from most product analytics tools.
Most product analytics tools charge by monthly tracked users or events ingested, because they're the ones storing and processing your event data. EngineFresh isn't. That changes what a fair price actually tracks.
Because EngineFresh queries your warehouse instead of ingesting events, there's no per-tracked-user or per-event fee, that pricing model doesn't make sense for something that doesn't ingest anything.
Warehouse compute is billed separately, by BigQuery or Databricks, and stays yours to see and control. We don't mark it up or add a margin on top of it.
What you pay EngineFresh for is the product layer: dashboards, funnels, alerts, and the queries we run on your behalf, priced by how much of the product you use, not by how much data your company happens to generate.
These are directional, not a rate card. Feature boundaries between tiers are the part most likely to shift as we work through early access with design partners.
For a small team connecting one warehouse and asking a handful of core questions.
For teams that want real-time alerts running continuously, not just dashboards someone checks.
For teams that need deployment or contract terms beyond a standard plan.
During early access, pricing is worked out directly with each design partner based on warehouse size and team needs, not a fixed rate card.
No. Warehouse compute is billed to you directly by BigQuery or Databricks, and we don't see or mark up that spend. Your EngineFresh bill is only for the product layer.
Not decided yet. What we can say is that trying EngineFresh doesn't require a paid plan or production access, see our sandbox options for ways to test it with sample data first.
Design partners who join now help shape the eventual rate card, and we intend to give them early, favorable terms as a thank-you for that, not have pricing sprung on them later.
We're leaning toward usage of the product (dashboards, alert volume) rather than a hard per-seat fee, so that adding a teammate who just wants to look at a dashboard isn't a pricing decision. That's still being tested with design partners, not finalized.
Design partners get a direct say in how this shakes out, plus early, favorable terms.
Request early access