Everyone has an opinion about the "modern data stack." Very few people publish the bill.
The standard pitch — Fivetran for extract, Snowflake for warehouse, dbt Cloud for transform, Looker for BI, Monte Carlo for observability — is sold as the default for any company with more than three engineers. In 2020 that bundle cost a small team maybe $1,500/mo. By 2024 it was closer to $3,000. In 2026, with Fivetran counting deletes as MAR and enforcing a $5 per-connection minimum, it's worse.
Meanwhile, something genuinely new happened in the last eighteen months: open-source ELT caught up to the commercial tools, and AI coding agents got good enough to own the "glue work" that used to justify half the price tag. The honest cost of running a growing team's data stack in 2026 isn't $3,000/mo. If you're willing to self-host and let an agent do the connector wiring, it's closer to $15.
This post is the math, not the pitch. If you disagree, the numbers are there to argue with.
The 2024 baseline — a growing team on managed everything
Let's pick a realistic "growing team" profile and price it out in 2024:
- 10 sources — a couple of production Postgres databases, Stripe, HubSpot, Segment, Shopify, Salesforce, Google Ads, a couple of internal APIs
- 10M rows/mo ingested across those sources
- 20 dbt models on top — staging, intermediate, marts
- 3 analytics engineers using the transform tool
Here's what that looked like on a "default" managed stack eighteen months ago:
| Layer | Tool | Monthly cost |
|---|---|---|
| Extract + Load | Fivetran Standard | ~$500 (10M MAR + $5/connection minimum × 10) |
| Warehouse | Snowflake (XS, ~40hr compute/mo) | ~$120 |
| Transform | dbt Cloud Starter | $300 (3 seats × $100) |
| BI | Looker / Metabase Cloud | $200–$400 |
| Observability | Monte Carlo Entry / Elementary Cloud | $200–$500 |
| Total | $1,320 – $1,820/mo |
Where these numbers come from, because it is the weakest part of the post and worth saying plainly: they are our estimates for the profile above, not quotes. Checked in August 2026, most of these vendors publish no rate card you can compute a bill from — Fivetran points at an estimator and a consumption table with no per-MAR rate, Airbyte prices its paid tiers on compute capacity rather than data moved, and Snowflake's pricing-options page carries no dollar figure at all. dbt Cloud Starter at $100/seat/month is the one line here taken from a published price. Your own bill will differ, sometimes by a lot; run the numbers through Fivetran's estimator and Airbyte's pricing page for a binding figure. The Datanika rows below are exact, because our rate is published.
Nobody budgets for this up front. It creeps in one invoice at a time until someone in finance prints all five of them on the same page.
A few things to notice:
- The "extract" layer is the most expensive single line. Fivetran's MAR-based pricing rewards narrow pipelines and punishes the long tail of small sources. Adding a sixth source you only sync once a day still costs $5 minimum — before any data moves.
- Transform is priced per seat, not per workload. dbt Cloud charges you $100/month for the third analyst, whether they push one commit or a hundred.
- Connector count is a lock-in metric, not a utility metric. Every vendor brags about "700+ connectors." Most teams use 8–12.
What changed between 2024 and 2026
Two things, mostly.
First: open-source ELT became legitimately production-ready. dlt (the Python library, not "data loading tool" the consulting company) went from "interesting library" to "the thing you'd actually pick" over about eighteen months. Its incremental-load primitives, schema evolution, and native typing are good enough that the main reason to pay for Fivetran — "we don't want to maintain extractors" — weakened considerably. Pair that with dbt-core (still free, still open source) and you have the whole EL-and-T loop in two Python packages.
The blocker used to be orchestration and the UI. You'd end up with a half-finished Airflow deployment, a YAML graveyard, and a Grafana dashboard nobody checks. That's the piece that actually burned out small data teams.
Second: coding agents. In 2024, writing a new source extractor with dlt meant reading the docs, writing a test, debugging pagination, and babysitting the first few runs. In 2026, you ask Claude or GPT to scaffold it, give it the API spec, and the first draft compiles. The "agent-shaped work" — wiring up credentials, mapping columns, writing the five lines of Jinja dbt needs — is the cheapest it has ever been. (We wrote about this shift in more depth in our AI-agent-native positioning post; the short version is that the API surface you expose to agents now matters more than the connector count.)
The implication is uncomfortable for the managed-ELT vendors: the thing you were paying Fivetran to avoid doing is now the thing an agent does in eight minutes for the cost of a few tokens.
The 2026 line-item budget for the same team
Same 10 sources, same 10M rows/mo, same 20 dbt models, same 3 analysts. Here's a stack built in 2026 with open-source ELT, a single VPS, and an AI agent doing the glue work:
| Layer | Tool | Monthly cost |
|---|---|---|
| VPS (Hetzner CPX31 — 4 vCPU, 8 GB RAM, 160 GB NVMe) | Hetzner | €11.49 (~$12.50) |
| Snapshots / backups | Hetzner | €0.20 |
| Extract + Load |
dlt (open source) |
$0 |
| Warehouse | DuckDB / Postgres on the same box, or BigQuery on-demand (~$5–$20 depending on volume) | $0–$20 |
| Transform |
dbt-core (open source) |
$0 |
| Orchestration + UI | Datanika (open source) | $0 |
| BI | Metabase OSS (same box) | $0 |
| Observability | Grafana + Prometheus (same box) | $0 |
| DNS / CDN / SSL | Cloudflare free tier | $0 |
| Transactional email | Resend free tier | $0 |
| AI agent (pipeline build + dbt model scaffolding, ~20 hours/mo) | Claude or similar | ~$20–$40 |
| Total | ~$15 – $75/mo |
The range comes from two variables: (a) whether you run the warehouse locally (DuckDB/Postgres, $0) or reach for BigQuery on-demand for heavier workloads, and (b) how much you let an agent drive. At the low end, with DuckDB and light agent use, you're paying €15/mo to run what used to cost $1,500. That's a 100× cost reduction for the same team profile.
If that sounds too good, it is and isn't. The cost of the tools dropped by 100×. The cost of operating the thing — someone who understands how pipelines fail at 3 AM — didn't drop at all. We'll come back to that.
Apples-to-apples: where each layer actually lands in 2026
Here's the same 10-source, 10M-row profile priced across everything a 2026 data team could actually pick:
| Stack | EL + T + Orch | Warehouse | BI + Obs | Total / mo |
|---|---|---|---|---|
| Fivetran + dbt Cloud + Snowflake + Looker | $900 | $120 | $400 | ~$1,420 |
| Airbyte Cloud + dbt Cloud + BigQuery + Metabase OSS | $550 | $20 | $0 | ~$570 |
| Hevo + dbt Cloud + Snowflake + Metabase OSS | $540 | $120 | $0 | ~$660 |
| Datanika Pro ($79) + BigQuery + Metabase OSS | $79 | $20 | $0 | ~$99 |
| Self-hosted Datanika + DuckDB + Metabase OSS + agent | €12 | $0 | $0 | ~$15 |
Datanika's $79 Pro tier includes EL, T, scheduling, notifications, and multi-tenant dbt projects in a single app — which is why it lands where it does. The self-hosted tier is a straight VPS bill.
Before anyone writes me an angry email: yes, these are rounded. Yes, "it depends." Yes, the Snowflake bill for any team that actually writes meaningful SQL is going to be more than $120. But the order-of-magnitude gap between the top row and the bottom row is the real story and it's not a rounding error.
"But you're paying with your time"
Here is the honest objection. Managed stacks aren't expensive because the vendors are greedy. They're expensive because someone, somewhere, is being paid to keep the pipelines running at 3 AM when the Shopify API changes its pagination without telling anyone. That someone is a real cost, and when you self-host you inherit their job.
Two things have changed about that math:
The operational surface got smaller. A decade ago self-hosting "the data stack" meant running Airflow (a distributed scheduler you will fight), a warehouse you provision yourself, and a half-dozen custom extractors. In 2026 it means one Docker Compose file with six containers, running on a $12 box, with dlt handling the boring parts of extract and dbt-core handling transform. If the box falls over, you restore a snapshot. That's not zero work, but it's far from a full-time job.
Agents absorb the worst part. The failure mode that used to eat analytics engineers alive wasn't writing the pipeline — it was modifying it. Stripe adds a field. Shopify deprecates an endpoint. HubSpot changes its OAuth scopes. In 2024 this was half your calendar. In 2026 you open Claude, paste the error, and it hands you back the patch. The schema-drift tax didn't disappear, but its price collapsed.
So yes, you're "paying with your time" — but the bill is roughly one afternoon a month for a team of three, versus zero afternoons a month but $1,500. Plenty of teams should still pick managed. Plenty shouldn't. The default changed.
The three questions that actually decide it
If you're sitting on a 2024-era bill and wondering whether to rip it out, don't start with the tools. Start with these:
- How many of your sources are in the long tail? If seven of your ten sources are small and only syncing once a day, Fivetran's $5-per-connection minimum is eating you alive. Self-hosting wins on long-tail pipelines and loses on high-volume ones. Look at your distribution of row volume, not the total.
- Do you have anyone who can debug a Python stack trace? Not "love doing it" — just "can." The agent-assisted version of self-hosting is dramatically easier than the 2020 version, but there's still a floor. If nobody on the team can read a traceback, pay for managed and move on.
- Is your warehouse bill the biggest line item? If yes, this post doesn't help you. Nothing in the EL/T layer moves the needle compared to rewriting a few nested CTEs. Go fix the warehouse first.
If the answers are "yes long-tail, yes Python, no warehouse isn't the biggest" — the 2026 stack at $15/mo is a real option, not a thought experiment.
Where Datanika lands in this
You can do everything in this post without us. dlt is on PyPI, dbt-core is on PyPI, DuckDB is on PyPI, Metabase ships a Docker image. Nothing about "open-source ELT + an agent" requires buying anything from anyone.
What Datanika is, honestly, is the UI and orchestration layer that keeps the six-container Docker Compose from turning into Airflow. We wrap dlt for extract, dbt-core for transform, APScheduler + Celery for scheduling, and add a multi-tenant Reflex UI so you can point-and-click the boring parts and let an agent drive the rest via our Agent API. The core is open source under AGPL-3.0; the billing layer is a paid plugin. If self-hosting scares you, Pro is $79/mo. If it doesn't, the core runs on the same €12 VPS class as everything else in this post.
We are not the cheapest thing on the table — dlt + dbt-core hand-rolled is. We are the cheapest thing with a UI and scheduling and notifications that an agent can talk to.
The punchline
The modern data stack in 2024 was an unbundling story: one tool per layer, each one priced for the Fortune 500, all of them assuming you had a dedicated data team. The 2026 version is a rebundling story. dlt + dbt-core + one VPS + one agent collapses five vendor invoices into a Hetzner bill with a euro sign on it.
None of this is theoretical. We publish our own infrastructure bill, line by line, including what changed when we moved hosts. Our Agent API exists because we use agents to build pipelines on Datanika, not just because other people might.
If the number on your current data-tools invoice has three commas in it and you haven't looked at this math in twelve months, look again. A lot changed while you weren't looking.
Datanika is an open-source data pipeline platform — dlt for extract, dbt-core for transform, APScheduler for orchestration, Reflex for the UI. Start free, self-host it, or read the Agent API docs if you want an agent to drive the whole thing.
Top comments (0)