Dune Analytics Revamps Credit‑Based Pricing – What Analysts Need to Know
June 3 2026 – DeFi Pulse
Dune Analytics, the on‑chain analytics platform that powers thousands of dashboards across more than a hundred blockchain networks, announced a fundamental shift in how users are billed for query execution. The change moves the service from a flat‑rate credit model to a usage‑based system that charges in proportion to the resources a query consumes. The update also brings new pricing tiers, longer time‑outs, and a suite of tools for cost control and query optimisation.
Why the Move to Usage‑Based Credits?
Until now, Dune charged a fixed amount of credits for every query, regardless of its complexity or execution time. While simple to administer, the model created two major inefficiencies:
- Overcharging simple queries – analysts paid the same price for a quick count as they did for a multi‑join, multi‑chain aggregation.
- Undercharging heavy queries – resource‑intensive jobs were subsidised, often hitting hard time‑outs that limited the depth of analysis.
With the platform’s user base expanding rapidly—spanning dozens of L1/L2s, complex relational tables, and a growing ecosystem of API and connector integrations—Dune’s team argues that a static credit charge no longer reflects real usage patterns. The new engine aligns cost with actual compute, storage, and data‑transfer consumption, offering a fairer bill for both light and power users.
What’s Changing?
| Aspect | Old Model | New Model |
|---|---|---|
| Credit consumption | Fixed per query | Scales with CPU, memory, and runtime |
| Query time‑outs | Rigid limits, often cut off long jobs | Longer allowances, enabling deeper analytics |
| Pricing plans | $49 / mo (monthly) • $45 / mo (annual) | $75 / mo (monthly) • $65 / mo (annual, $780 / yr) |
| Enterprise tier | Standard per‑credit rate | Discounted credit pricing + custom support |
| Cost‑control tools | None | Credit caps per query, overage limits, usage dashboards |
The credit ledger itself remains unchanged, meaning existing balances carry over. However, when a query runs, the system now evaluates the resources consumed and deducts credits proportionally. Small, well‑optimised queries will cost fewer credits, while larger workloads will be billed more accurately, albeit at a higher per‑query credit rate.
New Features & Integrations
The upgrade paves the way for a broader set of capabilities that were previously constrained by the flat‑fee model:
- Extended time‑outs – Users can run longer analytical jobs without hitting abrupt interruptions.
- Advanced connectors – Upcoming support for dbt‑style pipelines, Trino REST API, and SQL Mesh will let teams embed Dune data directly into their data‑warehousing workflows.
- AI‑driven automation – Early‑stage integration of generative‑AI assistants for query generation and result summarisation.
- Cost‑management UI – A dashboard for monitoring credit spend, setting per‑query caps, and configuring monthly overage limits.
Analyst Perspective: Pros and Cons
Pros
- Fairer billing – Credit usage now mirrors true compute effort, rewarding efficient SQL.
- Incentive to optimise – Teams will be motivated to refactor queries, adopt indexes, and reduce unnecessary scans.
- Scalability – Larger research projects—such as cross‑chain token flow analyses—can run to completion without artificial throttling.
- Transparency – Real‑time usage metrics let organisations forecast spend and avoid surprise bills.
Cons
- Higher baseline cost – The new monthly and annual pricing tiers represent a price increase of roughly 50 % for standard plans.
- Learning curve – Users must become familiar with the new cost‑control settings and the best‑practice guide for writing efficient queries.
- Potential credit volatility – Heavy, exploratory queries could quickly deplete balances if not capped.
Key Takeaways
| Takeaway | Implication |
|---|---|
| Pricing shift – Fixed‑credit pricing is being replaced by a consumption‑based model. | Expect lower costs for simple lookups; larger analyses will cost more but gain longer execution windows. |
| Plan price hike – Monthly subscription rises to $75, annual to $65 per month. | Existing subscribers will see the increase on the first billing cycle after October 21. |
| Enterprise advantage – Larger organisations can negotiate per‑credit discounts and receive tailored support. | Companies with high query volume should contact Dune’s sales team promptly. |
| Cost‑control tools – New UI features allow caps per query and overall overage limits. | Proactive budgeting becomes feasible; teams can prevent accidental credit exhaustion. |
| Optimization is rewarded – Efficient queries directly translate to credit savings. | Investing time in query refactoring and learning Dune’s performance guidelines will pay dividends. |
Action Items for Current Dune Users
- Audit current usage – Review recent query logs to gauge average credit spend.
- Set caps – Use the newly released “credit cap” feature to limit exposure on particularly heavy jobs.
- Refresh query practices – Follow Dune’s updated guide on writing efficient SQL to minimise consumption.
- Re‑evaluate plan selection – If you foresee higher query volumes, discuss enterprise options; otherwise, the standard monthly plan may still suit lighter workloads.
- Monitor upcoming connectors – Keep an eye on the announced dbt, Trino, and SQL Mesh integrations, which could reshape data pipelines and further influence cost dynamics.
Where to Find More Information
- Detailed documentation on the credit system and FAQs can be accessed on Dune’s learning portal.
- Guidance on query optimisation is available in the “Writing Efficient Queries” section of the Dune docs.
- For custom pricing or enterprise arrangements, reach out via the Dune Enterprise page.
By aligning credit consumption with actual resource use, Dune hopes to foster a more transparent and scalable analytics ecosystem for DeFi researchers, data engineers, and blockchain enthusiasts alike. The transition will require users to adapt their workflow, but the promise of fairer pricing and richer feature sets could make the shift worthwhile for the rapidly evolving on‑chain analytics community.
Source: https://dune.com/blog/credits-changing
