If you received a usage alert in Kondado, it can come from two different places: your Plan or Via Kondado. This article helps you identify which of the two is close to its limit.
TL;DR — Quick Summary
| Aspect | Kondado Plan | Via Kondado |
|---|---|---|
| What the limits control | Monthly records processed + number of active pipelines | Accesses and stored cells (per unit) |
| Typical alert | "X% of plan records used" | "X% of Via Kondado storage" / "X% of accesses" |
| Where it appears | Usage/billing area of your account | On the Via Kondado destination page |
| How to fix | Upgrade the plan | Add units to Via Kondado |
Rule of thumb: if the alert mentions "storage" or "accesses", it's Via Kondado. If it mentions "plan", "records" or "pipelines", it's your subscription.
Do I have two types of limits?
Yes — and they are completely independent.
- You can be at 100% Via Kondado while only at 20% of the plan — or the other way around.
- Hitting one does not block the other.
- Each has its own counter, its own usage screen, and its own upgrade path.
Common confusion: an "80% storage" alert comes from Via Kondado, not your plan. If you only use Via Kondado for a few dashboards, this alert can easily appear while your plan is nearly empty.
Kondado Plan Limits
Your plan defines how much you process per month and how many pipelines you can keep active.
What counts toward the Plan
| Resource | What it is | Limit |
|---|---|---|
| Records/month | Rows of up to 500 bytes inserted into destinations. Rows larger than 500 bytes count as more than one record. | Depends on the plan |
| Active pipelines | A flow of 1 connector + 1 destination + 1 object (e.g., Salesforce → Via Kondado → Leads) | Depends on the plan |
The plan does not limit connectors or destinations — all connectors and all destinations are unlimited on every plan. What counts is the record volume and the number of active pipelines.
Full plan table and pricing: kondado.io/en/pricing.html.
Typical Plan alerts
"You have used 85% of your plan records this month"
"You have reached the pipeline limit of your plan"
What happens if you hit the limit?
- Records limit: your pipelines may be paused until the next billing cycle, or you can upgrade the plan.
- Pipeline limit: you cannot activate new pipelines without upgrading.
How to upgrade
Upgrade directly at app.kondado.io/upgrade, or check all plans at kondado.io/en/pricing.html. Questions: info@kondado.io.
Via Kondado Limits
Via Kondado is sold in units, and each unit has its own monthly limits — separate from your plan. Every account already includes 1 free unit; additional units cost $3.19/month each (pricing).
What counts toward Via Kondado
| Resource | What it is | Limit per unit |
|---|---|---|
| Accesses | Data reads, counted in 10 MB blocks (each read is rounded up) | 2,000/month |
| Cells | One cell = 1 row × 1 column stored | 10 million/month |
| Active models | SQL models active on Via Kondado | 2/unit |
How accesses work: a 5 MB table consumes 1 access; a 25 MB table consumes 3 accesses (rounded up in 10 MB blocks).
How cells are counted: a table with 100,000 rows × 50 columns = 5 million cells.
Each BI refresh is one or more reads: every time Power BI, Looker Studio or another BI tool refreshes, it consumes accesses proportional to the size in MB of the table being read.
Typical Via Kondado alerts
"You have reached 80% of Via Kondado storage"
"Via Kondado at 95% access usage"
What happens if you hit the limit?
- Accesses: new reads are affected until the next cycle or until you add a unit.
- Cells: the per-unit limit blocks new writes on that unit.
- Active models: you cannot activate a 3rd model with just 1 unit.
Each extra unit stacks the limits: 2 units = 4,000 accesses/month, 20 million cells, 4 models.
Full Via Kondado details: kondado.io/wiki/en/via-kondado.
Is my alert about the Plan or Via Kondado?
Use this quick decision tree:
1. Where did the alert appear?
- In the usage/billing area of your account → it's the Plan
- On the Via Kondado destination page → it's Via Kondado
2. What does the alert mention?
- "Records", "pipelines", "plan" → Plan
- "Accesses", "cells", "storage", "unit" → Via Kondado
3. What were you doing right before the alert?
- Creating/running many pipelines → likely Plan
- Refreshing a dashboard (Power BI, Looker Studio, etc.) or adding tables to Via Kondado → likely Via Kondado
Upgrade: each one is separate
| Situation | Action |
|---|---|
| Hit the Plan (records or pipelines) | Upgrade plan at app.kondado.io/upgrade |
| Hit Via Kondado (accesses, cells or models) | Add unit(s) to Via Kondado |
Changing the plan does not raise the Via Kondado limit, and adding Via Kondado units does not raise the plan's record limit.
FAQ
Does Power BI read the entire table on every refresh?
Yes. In a standard (non-incremental) refresh, Power BI reads every row of the table. This consumes accesses proportional to the table size in MB (rounded up in 10 MB blocks).
Does reducing the number of columns decrease access consumption?
Not directly. Accesses are counted by the volume in MB read, not by the number of columns. Removing columns only reduces consumption if it makes the table small enough to cross into a lower 10 MB block (e.g., going from 25 MB to 12 MB reduces 3 accesses to 2; going from 8 MB to 5 MB changes nothing — still 1 access).
1 Via Kondado unit = 2,000 accesses, is that per table?
No. The 2,000 accesses are the total monthly amount for the unit, combining every read across every table in that unit.
Can I monitor usage in real time?
Yes — the usage/billing area (for the plan) and the Via Kondado page (for the destination) update with little delay.
If I hit Via Kondado, does my plan stop too?
No. The limits are independent. Hitting Via Kondado does not interrupt your pipelines — and vice versa.
Do other destinations (BigQuery, PostgreSQL, Excel, S3/Athena) consume Via Kondado accesses/cells?
No. Only the Via Kondado destination has accesses and cells counters. Other destinations count only plan records.
Need help?
If after reading this article you are still unsure which alert is yours, email info@kondado.io with:
- Screenshot of the alert you received
- Which Kondado screen it appeared on
That way we can quickly identify whether it is a Plan or Via Kondado limit.
Identify Which Kondado Limit Triggered Your Alert
Follow these steps to determine whether your usage alert came from your Kondado Plan or Via Kondado, and take the correct action.
Check where the alert appeared
Open your Kondado account and note the screen that showed the alert. If it appeared in the usage/billing area, it relates to your Kondado Plan. If it appeared on the Via Kondado destination page, it's a Via Kondado limit.
Read the exact wording of the alert
Look for keywords in the message. Alerts mentioning 'records', 'pipelines', or 'plan' indicate your subscription limit. Alerts mentioning 'accesses', 'cells', 'storage', or 'unit' point to Via Kondado. This is the fastest way to tell them apart.
Review your recent activity
Think about what you were doing before the alert. Creating or running many data pipelines suggests a Plan limit. Refreshing dashboards or adding tables to Via Kondado suggests a destination limit.
Check your current usage counters
Visit the usage/billing area for real-time Plan metrics, or the Via Kondado page for destination metrics. Both update with little delay, so you can verify which counter is actually high.
Apply the correct fix
If you hit the Plan limit, upgrade your plan at app.kondado.io/upgrade. If you hit Via Kondado, add units to that destination. Remember: changing one does not affect the other — they are completely independent.
