Matillion pricing in credits per task hour across the Developer, Teams and Scale editions

How much does Matillion cost?

Matillion costs whatever your sales quote says, because the Data Productivity Cloud has no public list price and no permanent free production tier. What Matillion does publish is the consumption side: its credit consumption terms, read on 27 September 2026, charge 1 credit per orchestration task hour, 3 per transformation task hour, 1 or 2 for streaming CDC, and 70 credits a month for each developer user beyond those included. The price of a credit, and the size of the annual package, are in the Order Form. Matillion's AWS Marketplace listing, also read on 27 September 2026, bills one dimension, "usage in cent of the product" at $0.01 per unit, and lists no contract price.

Those figures cover the Matillion license alone. There is a second meter that most first-time buyers miss: warehouse compute. Because Matillion runs transformations inside your data platform rather than on its own servers, the SQL it generates burns credits or slots on Snowflake, BigQuery, Databricks, or Redshift, and that lands on your cloud bill, not Matillion's invoice. A busy transformation workload can make the warehouse line rival or exceed the license. So a budget has two lines you model yourself (task hours times the consumption rate, and warehouse compute) and one number only sales can give you, the price per credit.

What drives the bill	Published by Matillion	Where the number comes from
Credits per task hour	Yes: 1 orchestration, 3 transformation, 1 or 2 streaming	Credit consumption terms, read 27 Sep 2026
Extra developer users	Yes: 70 credits per user a month	Credit consumption terms, read 27 Sep 2026
Dollar price per credit	No	Your Order Form, including the overage rate
Annual package size	No	Sales quote; AWS Marketplace shows only a $0.01 usage unit
Warehouse compute	Not a Matillion charge	Your Snowflake, BigQuery, Databricks or Redshift bill

Read the table as a checklist for the quote. Ask for the price per credit and the overage rate in writing, model a normal month of task hours against the published rates, and budget the warehouse compute as a separate line because it moves on its own.

How does Matillion's credit-based pricing work?

Matillion's credit-based pricing works by selling you a fixed annual package that includes a pool of credits, which your jobs draw down by task hours as orchestration and transformation work runs. A task hour is the unit of consumption: the more work your pipelines do, the more credits they burn. Additional developer users beyond your included seats add cost.

The exchange rate between work and credits is published, even though the dollar price of a credit is not. Matillion's credit consumption terms, read again on 27 September 2026, set orchestration pipelines at 1 credit per task hour, transformation pipelines at 3 credits per task hour, and streaming change capture at 1 credit per task hour on essential or 2 on premium. Each developer user draws 70 credits a month. Consumption is measured in 2 second increments, and validation and sampling are not billed. The overage rate, per the same terms, is whatever your order form says.

What runs	Credits consumed
Orchestration pipeline	1 credit per task hour
Transformation pipeline	3 credits per task hour
Streaming (CDC), essential	1 credit per task hour
Streaming (CDC), premium	2 credits per task hour
Developer user	70 credits per user per month
Validation and sampling	Not billed

The 3x multiplier on transformation is the number to model. A team that moves its heavy logic into transformation pipelines triples the credit draw per hour of that work, so the same data can cost very differently depending on where the SQL runs. How a credit meter behaves next to row, task and execution meters on one ordinary job is worked through in data integration pricing compared.

The model rewards efficient pipelines and punishes wasteful ones. A tightly built job that runs in minutes draws fewer credits than a sprawling one that churns for an hour on the same data, so pipeline design has a direct line to the invoice. Because you commit to the package annually, a quiet quarter does not refund unused credits, and a heavy quarter can push you toward the top of your included pool or into an overage conversation. Matillion does not publish a per-credit dollar rate, so the only way to translate a workload into dollars is a quote. The sensible move is to estimate your task-hour volume, size the package to it, and revisit the commitment once real usage data comes in. Matillion also offers Maia, its AI agent layer, which can speed up pipeline building, though how any assisted work maps to consumption is another thing to confirm with sales.

What is the difference between the Matillion Developer, Teams, and Scale editions?

The three editions differ mainly by how many developer users they include and who they target. Developer is for individuals and includes one developer user with a free trial to start. Teams, the edition Matillion marks Most Popular, is built for scaling businesses and includes five developer users. Scale is aimed at large organizations and also includes five developer users with the higher-end capabilities and support those buyers need.

The seat counts are starting points, not caps. On Teams and Scale you can license additional developer users, and each one adds cost, so a growing data team steadily raises the license line even before task-hour consumption is counted. There is no permanent free production tier on any edition: the free option is a time-bound trial meant for evaluation, not for running production pipelines indefinitely. Which edition fits comes down to team size, the governance and support you need, and how many people build pipelines, and the credit consumption model sits on top of whichever edition you pick.

Edition	Included developer users	Best for	Credit and free-trial notes
Developer	1 developer user	Individuals evaluating or building solo	Free trial available. Credit consumption applies once you run real work
Teams (Most Popular)	5 developer users	Scaling businesses with a small data team	Extra developer users add cost. No permanent free production tier
Scale	5 developer users	Large organizations needing higher-end capabilities and support	Extra developer users add cost. Priced by quote, credits on top

Treat the seat numbers as the floor of the license, not the ceiling of the bill. Both Teams and Scale grow with every extra developer user and every extra task hour, so map your real team size and expected workload to the edition before you commit.

Does Matillion charge for warehouse compute?

No, Matillion does not charge you for warehouse compute directly, but you still pay for it. Matillion pushes ELT transformations down into your data platform, so the SQL it generates runs on Snowflake, BigQuery, Databricks, or Redshift, and that compute lands on your cloud bill rather than Matillion's invoice. The true cost of running Matillion is therefore two moving meters, not one.

This design is a genuine strength for performance, since your warehouse is usually the fastest place to transform data at scale, but it splits the budget across two vendors. Matillion credits cover the orchestration and the developer tooling. Your warehouse provider bills the actual number crunching, and a heavy transformation schedule can drive that line higher than you expect. It pays to keep an eye on the cloud spend from day one, because a pipeline that looks cheap in credits can be expensive in warehouse compute if it scans more data or runs more often than it needs to. Tuning the SQL, filtering early, and scheduling sensibly all pull that second meter down. When you compare Matillion against tools that run transformations on their own infrastructure, remember to add this warehouse line to the Matillion side so the comparison is fair.

Why is Matillion pricing hard to predict?

Matillion pricing is hard to predict because two consumption meters move at once and neither has a public rate. Credits burn by task hours, which change every month as pipelines are added, run more often, or process more data, and warehouse compute moves on its own on your cloud bill. With no published price to anchor against, the same estate can produce very different invoices from one quarter to the next.

Three forces compound the uncertainty. First, task-hour volume: a busy month that runs more or heavier jobs draws more credits than a quiet one. Second, developer users: every seat beyond your included count raises the license, and data teams tend to grow. Third, the warehouse meter: transformation compute lands on Snowflake, BigQuery, Databricks, or Redshift, so a pipeline change can raise that line even if your Matillion credits hold steady. Because there is no per-credit rate published, you cannot self-serve an accurate estimate, so forecasting means modeling task hours, counting seats, and projecting warehouse usage, then negotiating a quote. The practical mitigation is to instrument your expected workload, size the annual package to it, and track both meters as real usage data arrives.

Cost driver	What it does to the bill
Credits (task hours)	Core meter. More or heavier jobs draw down the included credit pool faster, so a busy month costs more
Developer users	Each seat beyond your edition's included count adds license cost as the data team grows
Warehouse compute	Separate meter on your cloud bill. Pushdown transformations burn Snowflake, BigQuery, Databricks, or Redshift compute
Edition tier	Developer, Teams, or Scale sets the included seats and capabilities, and Scale carries enterprise pricing by quote

Every rate here comes from Matillion's own terms; the dollar value of a credit comes only from a quote. Sizing the annual package well helps, but it does not make the invoice flat, so confirm the specifics with Matillion and budget the warehouse line separately before committing.

Is there a cheaper alternative to Matillion?

Yes, for the common case of moving data between apps, databases, and warehouses on a schedule, a flat-price connector platform is far cheaper and far more predictable than Matillion. Adapters publishes its rates ($49 Starter, $149 Growth, $399 Scale, Enterprise $798), charges the same regardless of which connectors you use, and lets you see the exact price with no sales call required.

The saving is not only sticker price, it is predictability. Because there is no credit meter and no separate warehouse-compute surprise for the extract-and-load step, a heavy month costs the same as a quiet one, so finance can forecast the line with certainty. The sync machinery that Matillion charges you to configure is built in: incremental loads, idempotent writes, automatic retries, and per-record logs come standard. Our Matillion alternative page lays out the feature-by-feature comparison, and the flat pricing page shows every plan in full. If you are weighing other ELT tools in the same search, the Fivetran alternative covers a similar trade-off. The honest caveat: if you need a deep, warehouse-native transformation studio with heavy orchestration and pushdown ELT built for a dedicated data engineering team, that is Matillion territory, and a flat connector platform is not trying to replace it. For most teams that simply need reliable pipelines into a warehouse without watching two meters, a self-serve Matillion alternative covers the job at a fraction of the cost.