Skip to main content

​
Frequently Asked Questions

Find answers to common questions about Dune’s pricing, credits, billing cycles, and subscription plans.

​
General Questions

Team admins can view invoices in the team’s Plan settings:
  1. Sign in to Dune.
  2. Open the account switcher in the sidebar and find the team that owns the subscription.
  3. Open the More options menu (three dots) next to that team and select Plan under Team settings.
  4. Scroll to Invoices. Enterprise teams see Extra credit invoices here. If your team belongs to an organization, an organization admin can find invoices under the organization’s More options menu → Plan instead.
You can also open https://dune.com/settings/teams/manage/<team-handle>/plan, replacing <team-handle> with your team’s handle.
Upgrading a paid plan resets your billing cycle start date. Unused days on your current plan are credited to your next invoice.Downgrades to lower tiers are applied at the end of your billing cycle. Benefits from your current tier remain until the end of your billing cycle. Check the confirmation page for the scheduled change date.
Only team admins can change a team’s subscription. For a self-serve plan:
  1. Sign in to Dune.
  2. Open the account switcher in the sidebar and select the team that owns the subscription.
  3. Open the More options menu (three dots) next to that team and select Plan under Team settings.
  4. Select Change plan, then choose the plan you want.
  5. To cancel, select Downgrade to Free. Complete the cancellation questions and any remaining steps, then select Downgrade on the final confirmation page.
  6. Check that the success page shows Plan change scheduled and the date the change takes effect. You can also review the scheduled change in the team’s Plan settings.
Your paid subscription remains active until the end of your current billing cycle. After the downgrade, Free access is view-only: your queries and dashboards stay saved, but running queries requires a paid plan.For an Enterprise or custom plan, contact support@dune.com. If your team’s Plan option is disabled because its plan is managed by an organization, ask your organization admin to manage the subscription.
Subscription settings are now called Plan. Personal settings and team settings are separate.If you only see Public profile and Account, you are in personal settings for an account that uses teams. Open the account switcher, find the team that owns your subscription, then use its three-dot menu to open Team settings → Plan.If you can view the plan but cannot change it, ask a team admin to make the change. If you still cannot find your subscription, contact support@dune.com with your team handle.
If your trial shows a paid plan scheduled to start, a team admin can cancel it before the displayed charge date:
  1. Open the team’s Plan settings.
  2. In the trial section, select Cancel trial and complete the confirmation.
  3. Check that the section shows Trial cancelled. It also shows when your remaining trial access ends.
The scheduled paid plan will not start and you will not be charged for it. Your account moves to Free view-only access after the remaining trial access ends.
Yes. New accounts receive a team automatically, and a team can have one member. Manage its subscription in Team settings → Plan.Existing accounts can retain a separate personal plan. If your subscription belongs to your personal account, open personal Plan settings.
For general info on how to use Dune, please see our docs. If you have other issues or questions not listed on this page, please contact support@dune.com.

​
Credits and Spending

Credits are the measurement unit for usage on Dune. They provide flexibility across query performance, programmatic executions, and API exports. Credits are consumed proportionally to the actual compute resources your queries use—simple queries cost fewer credits while complex ones use more.
Open the account switcher and use the three-dot menu next to your team to select Usage under Team settings. This page shows your credit usage and allowance. Use Plan to manage billing and spending limits.
Annual billing enables customers to pay for their plan yearly at a reduced rate. Customers on this plan will still have their credits reset on a monthly basis, as well as receive monthly charges for any potential extra credits incurred.
Credit usage is determined by the actual compute resources your queries consume. Your credit consumption directly reflects each query’s complexity and resource requirements.Query Execution (App & API)
  • Credits reflect the compute resources each query uses, including processing power (CPU), data scanned, and the time your query occupies the query engine.
  • High-frequency, lightweight queries, such as metadata lookups and the repeated calls generated by dbt or other automated workflows, also occupy the engine and are reflected in your credit usage.
  • Simple, efficient queries use fewer credits
  • Complex queries with large data scans require more credits
  • Queries cost the same whether executed manually or programmatically
API Export
  • Current plans charge for the volume of data exported in MB.
  • Export rates depend on your plan. See API billing for current rates.
  • Legacy plans can use datapoint-based billing. Check your plan settings for the billing model that applies to your subscription.
There are several ways to control and optimize your credit consumption:Monitor Your Usage
  • Check Team settings → Usage regularly to track your credit consumption patterns
  • Review which queries and users consume the most credits
  • Set extra credit limits to control how many additional credits can be purchased beyond your plan’s included amount
Control Spending
  • Set query cost caps in Team settings → Plan to limit the maximum credits any single query can consume
  • Configure team-level caps to prevent accidental high-usage queries
  • Use these caps while testing new queries or during development
Optimize Your Queries
  • Write efficient SQL to dramatically reduce credit consumption
  • Review our query optimization guide for specific techniques
During a free trial, using all 2,500 trial credits ends the trial and moves your account to view-only access. Upgrade to a paid plan to continue running queries and using the API. Free accounts and trials cannot buy extra credits.On paid plans, usage beyond your included monthly credits is billed at your plan’s extra credit rate, up to your configured extra credit limit. Check Team settings → Plan for your plan’s rate, or see the pricing page for current self-serve plans. Enterprise pricing follows your agreement.You can set query cost caps in Team settings → Plan to control your credit usage and prevent unexpected charges.
No. On paid plans, extra credits are billed as you use them, up to your configured extra credit limit. Free accounts and trials cannot buy extra credits.
Remaining credits at the end of a billing cycle do not rollover to the next month.
No. Free access is view-only and does not include monthly credits or pay-as-you-go usage. New accounts receive a 7-day trial with Plus plan features and 2,500 total credits. Adding a card places a hold for the plan amount, which is released if you cancel and captured if you keep the plan. The trial ends after 7 days or when the credits run out, whichever comes first. Upgrade to a paid plan to continue running queries and using the API. Paid plans support additional usage up to your configured extra credit limit.
A team admin can open Team settings → Plan, enable Limit extra credits, and set a monthly amount. Set the limit to $0 to prevent further extra credit usage. This limit does not cancel your subscription or remove charges for usage already incurred. For organization-managed teams, organization admins set the organization extra credit limit and monthly per-team credit caps in Organization settings → Plan. Team admins can set per-query and per-request limits in Team settings → Usage.
Lowering your extra credit limit does not remove charges for usage already incurred. If your current extra credit spend is already above the new limit, further extra credit usage is blocked. You will still be billed for the usage incurred before the change.

​
Query Engines & Executions

When you manually trigger an execution by pressing Run in the Query Editor, dashboard, or via the API, we accrue that usage to the user or team account. To ensure you are accruing usage in the correct account, check the selected user or team in the account switcher in the sidebar.
We have three different query engine sizes that you can use on Dune, each consuming credits based on actual compute resources used:Small Engine
  • Requires an active trial or a paid plan
  • Credits consumed from your trial or paid-plan allowance based on actual usage
  • 2-minute timeout limit
  • Maximum of three (3) concurrent executions
  • No performance guarantees
Medium Engine
  • Run queries with a larger timeout, manually or programmatically
  • Credits consumed based on actual compute resources used
  • No limit on concurrent executions
  • Suitable for most standard queries and dashboards
Large Engine
  • Optimized for complex workloads requiring more computational power
  • Credits consumed based on actual compute resources used (more compute and resource than Medium for the same query)
  • Best for data-intensive queries and complex analytics
The Large engine provides approximately 2x the computational capacity of the Medium engine. While both Medium and Large engines charge based on actual usage, the Large engine will typically consume more credits for the same query due to the additional resources allocated, but will complete faster. The Small engine is limited in capacity and has stricter timeout constraints.Note: Exact credit consumption varies based on query complexity, data volume scanned, processing required, and the time the query occupies the engine rather than being a fixed rate per execution.
Programmatic executions are query executions done through the Dune API, scheduled executions, materialized view refreshes, or dashboard runs. Programmatic executions consume credits based on actual compute resources used, just like manual queries. Both manual and programmatic executions are charged based on the complexity and resources required by your query, ensuring consistent and fair pricing across all execution methods. Automated workloads (scheduled queries, materialized view refreshes, and dbt or similar pipelines) consume engine time like any other query and are metered the same way.
Free access is now view-only and does not include query execution on any engine. You can browse existing queries and dashboards, and your saved work remains available. Running queries requires an active trial with remaining credits or a paid plan. See how credits work.

​
Features

If you add a private query to a public dashboard, other Dune users will be able to see the visualization in the public dashboard, but won’t see your code when they click the query. The results table, other visualizations you might have, and the underlying query are all private.
No, you can archive private queries that you no longer need to increase your existing private queries quota. Archived queries are not accessible by anyone else and cannot be run. You can unarchive them later if you change your mind.
Yes, anyone visiting the website with the embed can see the visualization you chose to embed and nothing else.
When logged in to the team on Dune, work you’ve created will not have watermarks. Public dashboards URLs always have watermarks.

​
Teams

Owners of editor seats can create and edit content owned by their team, but they cannot access team management features; those are reserved for admins. Viewers have read-only access to the team’s content and can still benefit from their team plan features and quotas.
Yes, team benefits apply to Dune content when your team is selected in the account switcher in the sidebar.
Quotas are applied to all team usage.
Yes, you can invite as many people as you need into your Dune team at no additional cost. All team members will need a Dune account to collaborate with you.
You can create 1 Free team on Dune.

​
API

Datapoints are used for API export billing on legacy plans. Current plans use exported data volume in MB instead. See API billing.For legacy datapoint-based plans, a datapoint can, in most cases, be thought of as rows * columns with an additional limit of 100 average bytes per cell in a set of results. This can be expressed as:datapoints = max(rows * columns, ceil(total_bytes / 100))
Each API request that returns result data consumes export credits, even when you fetch the same results again. Current plans charge by exported data volume; legacy plans can charge by datapoints. See API billing.
Query executions are identical to those triggered on dune.com. Please note: free executions are not supported via the API.
API access is available during an active trial and on paid plans, subject to the plan’s features, credits, and usage limits. Free access after the trial is view-only and does not include API access. See API billing and rate limits.