Priority Refresh Pricing
Get faster and more consistent refresh times immediately for
On sale until end of March!
Up to 25k data refreshes per day
An extra $100/month for each additional 10k data refreshes.Let's Chat
How will it help?
Refresh your data sources nearly every minute, even in peak usage periods.
While all Klipfolio dashboards can update automatically with live data, all data sources are treated equally to ensure a fair and positive experience for all.
This means that data sources queued to refresh every minute can often lag a few minutes behind.
Picture a long, fast-moving line in front of a single doorway. 8000 data sources pass through it every minute. And all data sources are treated equally.
For your priority workloads, when you don’t want to wait in line: We’ve added a dedicated doorway.
Who is it for?
Priority Refresh is perfect for Klipfolio customers with:
- Large numbers of users
- Requirements to see data in near real time, or as soon as it changes
- Data coming primarily from:
- SQL databases, local or cloud
- Rapidly changing Google Sheets, shared Excel files, or FTP/SFTP
- REST connectors
- Large numbers of dynamic data sources
- Specific periods of heavy usage (early morning, end of month, etc.)
- High priority dashboards that get a lot of views
What does it do?
Let's break it down a bit more... Priority Refresh includes the following key features:
Priority queue for data source refreshes
Faster and more consistent refresh times. Data sources in the public queue are sometimes delayed by the number of other sources waiting in the queue.
Data always up to date
Priority refresh includes the ability to warm up your data sources by scheduling a time for refresh at a strategic time of the day before people first log in. You’ll experience faster load times on initial login because your dashboard data will already be up to date.
Longer dynamic data sources retention
Dynamic data source instances will be retained for longer than in our public environment. Load time on first login will be decreased because fewer dynamic data source instances will need to be recreated.