Pricing
You pay for your coverage. Not for promises.
You license your own workspace plus the slice of the catalog you actually need - your region, your scene, your sources - and the interfaces to use it. Pricing follows that scope, so a pilot stays a pilot-sized commitment.
The model
What a tenant includes.
An isolated workspace
Your own database-backed tenant with its catalog, users and settings - strictly separated from every other customer.
Entitlements, not a firehose
You are entitled to the slice of the qualified catalog you actually need - by region, genre or source - and can review it before it ships.
Delivery interfaces
REST API with scoped keys, webhooks with delivery tracking, and an initial backfill of your entitled catalog.
Packages
Three ways in.
Pilot
Prove it on your real use case.
- One tenant workspace
- One coverage scope (region or scene)
- Catalog backfill + continuous delivery
- REST API with scoped keys
- Email support during the pilot
Growth
The operating setup for a live product.
- Everything in Pilot
- Multiple coverage scopes
- Webhooks with delivery tracking
- Review workspace for your team
- Source scoping for your territory
- Priority support
Enterprise
Custom coverage, contractual guarantees.
- Everything in Growth
- Custom source onboarding at scale
- Multiple tenants / brands
- Contractual SLAs and data agreements
- Dedicated onboarding
We quote per scope rather than publishing flat prices, because coverage differs wildly - a city’s jazz scene and a national portal are different projects. A concrete quote takes one conversation.
Questions
Fair questions about paying for data.
Why is there no price list?
Because the honest answer is “it depends on scope”: how many sources, which region, how much review effort, what delivery volume. We’d rather scope your case in a call than publish numbers that mislead in both directions.
What does a pilot look like?
A defined coverage scope, a working tenant with backfilled data, API access for your team, and a clear evaluation window. The goal is that you judge the data quality on your own product, not on our slides.
Do we get locked in?
Your product consumes a documented REST API and standard webhooks - no proprietary SDK requirement. If you leave, your integration surface is the thing you already own.
Does DataHub compete with our ticketing?
No. DataHub is ticketing-neutral: records deep-link to the original shop, and we never sit in the checkout. Ticketing providers are sources and partners, not competition.
See it run on your city.
Tell us your region, your scene or your sources - and we will show you the live pipeline on real data from your area, not a canned demo.