Pay for motion, not mystery

Read from sources for free. Store data with no storage charges. Matterbeam charges only for data in motion: loading, replaying, and transforming data plus a monthly platform fee.

Benefits

  • Reading from sources is free
  • No storage charges
  • Read, replay and transformation on one meter
  • Fan out the same data to multiple destinations for no additional charge
  • No hidden connector or source / destination charges

Pricing Summary

  • Platform fee: $200 per month
  • Usage pricing: starts at $25 per million records moved
  • What's billed: loading, replaying, transforming data
  • Not billed: source reads, at-rest storage,  additional destination fan-out, number of connectors, number of sources or number of destinations
  • Volume pricing: the more records, the lower the price per record

Example

You want to sync 20 million rows from a SQLServer database every month using change tracking. Those row syncs are any inserts, updates or deletes. You want to emit those rows into Parquet formatted files in an S3 bucket as well as a PostgreSQL database.

  • Loading all table data from SQLServer is free.
  • Storing it in Matterbeam is free.
  • Moving that data, or a subset of that data and emitting it to Parquet costs $25 per million rows: in this case, 20 million rows x $25 = $500
  • Writing that same stream to PostgreSQL is free.
  • Platform fee: $200

Total: $700 / month

FAQ

What counts toward usage?
Only data in motion: loading, replaying, and transforming.

Are source reads really free?

Yes. Reading data from a source is not a billed event.

Do you charge for storage or retention?

No. Storing data in Matterbeam is not a billable dimension.

How do transforms count?

You are charged for processing the number of records through the transform.

How do replays count?

When you replay historical data back through a live flow, that replayed records count as billable motion.

What is the platform fee?

A fixed $200/month monthly platform fee is applied in addition to any usage.

Do more destinations cost more?

Reading data to emit to one destination is billed, every additional destination of the same data stream does not cost more.

Stop Fighting Your Data Infrastructure

Most companies we talk to know something’s broken. They just assume six-month timelines and ballooning costs are normal. They’re not. Let’s talk about what’s actually possible.

Schedule a Demo