Skip to main content
In short: A live app costs credits for the initial build, for changes and fixes, and for every data refresh. The Console always informs you before credits are charged. In the Overview tab, What it costs shows what has been charged so far.

​
What credits are charged for

  • The initial build: Alex builds the dashboard. Every further revision via Order another round costs credits again.
  • Changes and fixes: Every change via Ask for a change and every fix via Order a fix or Order the fix is a job of its own.
  • Data refreshes: From the first go-live onward, the refreshes run through the account of the person responsible (owner). Every run consumes credits. Refresh now also costs the same as a regular refresh.
  • Having rules written down: Write them down is a job of its own for the delivering coworker.
The daily display check is free.

​
Where you see the costs

What it costs in the Overview tab shows credit consumption over the last six months. It is broken down by type: data refreshes, fixes, changes to the dashboard and the initial build. For the current month, you see the total so far and a forecast. In the Data table, each data area shows roughly what one run costs. One run can refresh several areas. The value is therefore a share, not a separate bill. The History tab lists every run with its cost.
Screenshot needed: the “What it costs” section in the Overview tab.

​
No costs without warning

The Console always informs you before credits are charged. It does so in two ways:
  • With a cost estimate: When you request a new dashboard or a change via Ask for a change, you see how many credits are expected before sending. The same applies when you have rules written down (Write them down).
  • With a notice: When you click Approve and put live or Refresh now, or restart paused refreshes, the Console points out in advance that credits will be consumed.
This way, you consciously decide at every step whether to accept the costs.
No longer need an area refreshed regularly? Only when asked pauses its refreshes. Stop expecting updates ends them. If the area shares a run with other areas, that run continues for the others. See Data areas and refreshes.

​
Who pays

Credits are charged to the workspace that runs the work. In the Console, that is the workspace you have selected. If you make a request by chat or email, the plan shows it in a line such as Billing: your organization. Check this line before you approve. See Workspaces and billing.

​
What you can do next

Workspaces and billing

Which workspace pays.

Credits overview

Balance, usage and costs.