snow
Join us at the Snowflake Summit!
Visit us at Booth #1206.
snow

Get the Honeydew Semantic Layer

Whether you’re a small data team or large organization, we’re here to help you get started

Lite

For teams building an AI analyst or a shared data model for BI
$20 /user/month
Starting from 25 users, up to 250
Platform fee: from $500/month
Available for 100/250/500 active objects

Features

Standard

For organizations that seek to establish a shared source of truth
$30 /user/month
Starting from 50 users, up to 500
Platform fee: from $2000/month
Available for 250/750/2000 active objects

Everything in Standard plus

Enterprise

For organizations that require scale or specialized functionality
Custom
Tailored to your scope and requirements

Everything in Enterprise plus

Frequently Asked Questions

Yes! We provide a 30 days free trial.

Our trials include:

  1. Unlimited access to the system
  2. Support over a dedicated Slack or Teams channel
  3. Training session (typically on the second week of the trial)
  4. Up to 4 hours of data modeling guidance

Need a larger pilot? Talk to us.

An active object is a field within a Honeydew workspace (a source attribute, calculated attribute or a metric) that is part of an active domain, used by BI tools, AI agents, API calls or data deployments.

A domain is considered active if during a month it was used to serve a data consumption tool:

  • Process SQL queries
  • Process AI queries
  • Process API calls (excluding metadata)
  • Deploy a dynamic dataset

A domain is not considered active it is only accessed through the Honeydew UI.

For example, if there is a domain called marketing with 250 objects (out of 3,000 objects across many domains), and only that domain received queries from Power BI during a month, then for that month there would be 250 active objects.

The same unique object can participate in multiple active domains. It will only be counted once, regardless of how many domains it is included in.

The same unique object can participate in multiple development branches. It will only be counted once, regardless of how many versions exist in development branches.

It is possible that the same domain will have a different composition of objects in a development branch and in the production branch. An object is counted if it participates in active domain in any branch.

A user is someone who is consuming Honeydew through an external tool, an API or via the Web interface.

That can include:

  • Users that log into BI tools with user authentication or SSO (single-sign-on).
  • Users that ask questions through an AI interface (like a Slack bot)
  • Users that call the Honeydew Snowflake Native Application through a Snowflake connection
  • Users that use the Honeydew Studio for modeling or data exploration

There are no query limits. Users can query as much as they want.

Enterprise tier contracts may include query-limited users.

Yes. There are workloads where when there is no authenticated user running queries.

Common use cases include:

  1. Use a single integration user to process all queries from a BI tool.
  2. Data tools that do not support user identification or authentication.
  3. Honeydew API calls from an embedded application.
  4. Honeydew API calls from an automated process, like dbt.

In those cases, 5,000 monthly SQL queries or 500 monthly AI queries will be counted as a single user during a month.

For example, if a report is running 500,000 queries each month serving the organization with a shared service account, then that would count as 100 users.

Yes! We provide volume discounts upon annual commitment.

Overage consumption is charged based on the subscription tier without volume discounts.

Limited users are available in Enterprise tier.

A limited user can be limited to a specific domain or a limited number of queries.

All tiers include product support during business hours with response SLAs based on issue severity.

In addition, we provide training, as well as guidance based on your particular data model and business domain.

Questions we can help with include:

  • Best practices for data modeling and data governance
  • Assistance for modeling complex metrics and other semantics
  • Help to migrate semantics from existing sources, including with automatic conversion tooling
  • Provide guidance on how to model data best for AI workloads

Please fill your details to book a demo and we will get back to you