300+ Tools CoveredSource Data Updated Weeklydates

Rivery pricing

By Egor Burlakov · Edited · Source dates below

Rivery pricing snapshot

Rivery bills usage in BDU (Boomi Data Unit) credits, also called RPU credits: database, file and webhook sources by data transferred, most API sources per pipeline run. It does not charge per connector, user or environment; instead each edition sets its own limits.

Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.

Rivery editions and pricing

EditionPriceRivery positions it for

Base

$0.9 / BDU credit, monthly billing

Introductory pay as you go edition

Professional

Usage in BDU credits

Core functionality for small data teams

Pro Plus

Usage in BDU credits

Data teams with larger data replication needs

Enterprise

Contact Rivery about Enterprise plans

Enterprises with extensive data and security requirements

The free trial includes all Professional features for 14 days or 1,000 free credits (worth $1,200), whichever runs out first. After it, you register for an on-demand plan or contact Rivery about annual and Enterprise plans.

Which edition fits

Every data source is available on every edition, so choose by limits and features rather than connectors.

  • Base works while two users, one environment and syncs every 60 minutes are enough.

  • Move to Professional for more than two users, a second environment, RBAC, Python, CI/CD, API and CLI access, or 15-minute syncs.

  • Move to Pro Plus for a third environment, single sign-on and SCIM, PrivateLink or API high-frequency syncs.

  • Move to Enterprise for unlimited environments, Oracle CDC, VPN tunnels, an Enterprise SLA or 5-minute syncs.

Edition details

Show full plan details

Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.

What each edition adds

EditionAddsMax sync frequency

Base

Unlimited connections, workflow orchestration, built-in version control

60 min

Professional

All Base, plus RBAC, Python code, built-in CI/CD, Rivery API and CLI access

15 min

Pro Plus

All Professional, plus single sign-on and SCIM, PrivateLink, reverse SSH, API high-frequency syncs

15 min

Enterprise

All Pro Plus, plus VPN tunnels, Oracle CDC, Enterprise SLA

5 min

  • Vendor source · Observed · Stored official pricing capture for rivery.

How credits are counted

Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.

How Rivery counts BDU credits

Source or pipelineCredit usage

Application (API) source, default

0.5 credit per output table per execution; above 50MB in one execution, 0.5 credit per 50MB; an execution with no data still costs 0.5 credit

API high-frequency sync source (Pro Plus, Enterprise)

1 credit per 100MB transferred, pro-rata, regardless of execution frequency

Standard database, file storage or webhook replication

1 credit per 100MB transferred, pro-rata, regardless of execution frequency

Log-based CDC database replication

2 credits per 100MB transferred, pro-rata

Orchestration and advanced workflows

0.5 credit per execution of an entire workflow

Python

Based on script execution time, server instance size and network bandwidth

Database, file, webhook and high-frequency API runs with no data cost 0 credit; the minimum counted transfer is 1MB. Database replication is charged by bytes, not rows. Simple source-to-target pipelines need no workflow.

Worked examples

Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.

Rivery's own credit examples, each for the stated pipeline only

ScenarioCredit usageWorking

2 CRM output tables every 8 hours, Monday to Friday

15 credits a week

2 tables × 3 runs a day × 5 days × 0.5 credit

One workflow pulling 5 API sources, once a day

3 credits a day

5 API pulls × 0.5 credit + 1 workflow × 0.5 credit

1,725MB a month from Postgres, standard replication

17.25 credits

1,725MB / 100MB

280MB a month from files on SFTP servers

2.8 credits

280MB / 100MB

These are Rivery's own examples, in credits. Each covers only the pipeline described, not other sources, workflows, Python or warehouse costs. Multiply by your edition's credit price; Base lists $0.9 per credit with monthly billing.

What drives the bill

  • API schedules and output tables. Every run of every output table costs 0.5 credit, even when no data arrives.

  • Volume and method. Databases, files and webhooks pay per 100MB moved; log-based CDC uses 2 credits per 100MB, standard replication 1.

  • Frequent API syncs. For API sources run often, such as every 5 minutes, or with many output tables, Rivery points to high-frequency syncs, billed like a database, and asks you to contact sales.

  • Row counts. Rivery calls its 1 row = 0.5 KB conversion a very rough estimate; measure real transfer sizes in the trial.

Easy to miss

  • PrivateLink, from Pro Plus, allows up to 3 connections across AWS PrivateLink, Azure Private Link or Google Private Service Connect.

  • SQL transformations run inside your own cloud data warehouse, so budget for that warehouse's compute and storage as well.

  • The listed Base price is for monthly billing. Rivery says annual billing unlocks additional savings, so ask for the annual credit price before you commit.

Our take

Rivery fits a team that wants ingestion, transformation and orchestration in one managed product. If most of your data comes from databases and files, credits follow megabytes moved and are straightforward to forecast; if it comes from many frequently scheduled API tables, run counts drive the bill, so price that workload with Rivery before committing.

Evaluate this price

Sources

Prices, edition limits and credit rules were observed on Rivery's pricing page on 2026-10-26; product details on Rivery's product overview the same day.