Monte Carlo Data Pricing: Data Observability Pricing per Credit, per Table and per Year

Monte Carlo's AWS Marketplace listing is the one place it publishes a contract-sized dollar figure. Re-read from the rendered listing on 15 September 2026, it sells a single dimension with the key Data_Obs and the display name "Monte Carlo Credit" at $50,000.00 for a 12-month contract at quantity one. Only a 12-month duration is offered, so there is no 24 or 36 month price to check for a multi-year discount. The listing carries an auto-renew badge, and its support term states that "all fees are non-cancellable and non-refundable except as required by law."

What the listing does not say is how many credits a $50,000 unit contains. It also attaches a usage-based overage rate to the same dimension, "Monte Carlo Additional Usage Credit" at $0.01 per unit. That figure cannot be a credit at either published rate, since a credit is $0.18 or $0.28, so the Marketplace "unit" and the rate-card "credit" are not the same thing, and the listing never bridges them. If the contract unit were denominated at the Start rate, $50,000 would fund about 277,800 credits, roughly 435 table-years of monitoring. At the Scale rate it would fund about 178,600 credits, roughly 280 table-years. Monte Carlo does not say which, so treat those as arithmetic, not entitlement, and ask before you buy through the Marketplace.

The same pattern shows up across the category, and the contrast is the useful part. Bigeye's listing states its entitlement in tables. Datafold's states it in developers. Acceldata's names its meters. Monte Carlo's states a dollar amount for an undefined quantity, and then, unlike Alation or Collibra, publishes the consumption rates and the per-credit price elsewhere on its own site. The information exists; it is just in three places. We tabulate the whole field in data observability pricing.

Monte Carlo is the category leader for a reason, and this page is not an argument that it is overpriced. If you need machine-learned anomaly detection across warehouses, lakes, streaming pipelines and AI agents, with a fleet of agents to triage and troubleshoot what it finds, the credit model is the price of that breadth, and the bracketed rate card is genuinely generous past the first few thousand tables. Plenty of enterprise data teams get their money's worth.

The mismatch shows up on a specific kind of team. They came to the pricing page because a column changed and three dashboards broke, or because nobody could say what a table feeds before deleting it, or because a model went stale overnight and the first people to notice were in the weekly business review. Those are lineage and change-impact problems. Lineage is included on every Monte Carlo tier, but it is not sold on its own: to get it you enable Table Monitors, and every table you enable is 1.75 credits a day. A thousand tables of "we just want to see what feeds what" is $178,850 a year on Scale.

Datatrail is built the other way round. It connects to Snowflake, Databricks, BigQuery, Redshift or Postgres with a read-only role, parses query history and dbt artifacts into column-level lineage that maintains itself, and derives everything else from that graph. Open any column and see downstream impact analysis, every model, exposure and dashboard that reads it, before you merge the change. Freshness monitoring and schema change alerts run on the same graph, so an alert arrives ranked by what it actually breaks. The plans are flat, $99, $299 or $799 a month on the pricing page, and there is no per-table meter to forecast.

It is a narrower product and that is the point of it. If you want the full observability platform, read the Monte Carlo alternatives comparison, which covers what Monte Carlo does genuinely well, or the direct Datatrail vs Monte Carlo page. If your shortlist is broader, the field is mapped in data observability tools and data lineage tools.

Four documents, all public, all on Monte Carlo's own domains or on AWS Marketplace, all read on 15 September 2026. The per-credit rates are on two order-form pages published 2 August 2025 and last modified 23 April 2026. An earlier version of the Scale page that search engines still quote in snippets read $0.25 per credit; the live page reads $0.28.

BASE=https://montecarlo.ai/pricing
curl -sL "$BASE/start-order-form/"   # $0.18 per Credit
curl -sL "$BASE/scale-order-form/"   # $0.28 per Credit

The consumption rates are the docs page both order forms incorporate by reference, Consumption Rates Version 2.1, last updated 8 September 2026. The docs site serves a Markdown version of every page if you append .md, which is how the tables above were read without a browser.

DOCS=https://docs.getmontecarlo.com/docs
curl -sL "$DOCS/version-21.md"                  # current
curl -sL "$DOCS/consumption-rates-version-11.md" # previous

The AWS Marketplace figures come from dumping the rendered DOM of listing prodview-hikicsfohm3gg with headless Chrome and reading the embedded rate cards, since the page returns nothing to a plain fetch. Comparison prices for Bigeye, Datafold, Sifflet and Acceldata were read the same way on the dates shown, and Metaplane's from its pricing page on 14 September 2026.

Three limits, stated plainly. Enterprise and Business Critical credit rates are not published anywhere we can find, so the two largest tiers cannot be computed. The dollar totals are list: Monte Carlo's pricing page says committed usage earns discounts, and enterprise deals are negotiated, so what you pay will be lower than what is printed here. And the rate card is versioned and has changed at least once; the figures are correct for Version 2.1 as read on 15 September 2026, and the order forms name a "successor URL" clause that lets the rates move. Where our figures and an order form disagree, the order form governs your contract. What this page gives you is the number to walk in with.