Do More. Pay Less.
More capabilities to deliver your data faster at a lower TCO.
Base
One Environment- Two Users
- Unlimited Connections
- Workflow Orchestration
- Built-in Version Control
Professional
for small data teams
Two Environments- Unlimited Users & RBAC
- Run Python Code
- Built-in CI/CD
- Access to Rivery’s API & CLI
Pro Plus
data replication needs
- Three Environments
- Single Sign-On & SCIM
- PrivateLink
- Reverse SSH
- API High-frequency syncs
Enterprise
data and security requirements
- Unlimited Environments
- VPN tunnels
- Oracle CDC
- Enterprise SLA
- Higher sync frequency
Edition Details:
Account
Connectors & Integrations
Extensibility
Orchestration
Security
How will you deliver efficiently?
Infrastructure / software maintenance cost
No infrastructure to provision like EC2 / VMs or software upgrades to manage
Dedicated pricing for high-volume replications
True data size based pricing for high-volume replications like databases vs. costly row based pricing models
Scalable per usage pricing
Usage based discounts and extra savings with annual billing
Build faster with fewer engineers
Build reliable solutions faster with native connectors, pre-packaged solutions and all the tools you need to quickly deploy a solution to production. Do it all without an army of data engineers
Fewer tools to manage
No dependency on external tool licenses for end-to-end data processes like an orchestrator tool or reverse ETL tool
Gal Bar
Founder and CEO
“We saved several $100K we could have spent on development and maintenance. Within a few hours, you can build a production-ready, scalable ETL system.”
Eric Sanders
VP, Business Analytics & Platforms
“We looked at Matillion, Informatica, Fivetran, Rivery, and probably four more. We tested every single one. We looked at features, pricing, and we picked Rivery. Over the years, we’ve redone that shopping and confirmed our choice – Rivery is exactly what we want.”
Daniel Rimon
Director of Data Engineering
“With a simple onboarding, you can save your business money in terms of development, maintenance & monitoring resources and get your data in a smooth and reliable way.”
Rivery Pricing FAQs
BDU credit = Boomi Data Unit (also known as RPU) credit:
- Database, file storage and webhook sources are charged only on the amount of data transferred down to the byte.
- Most application (API) based sources are charged for each execution of a data pipeline.
- Applications (APIs) with high-frequency syncs (replications) can be charged on the amount of data transferred similar to databases.
We charge based on actual usage, not number of rows, allowing you to scale in a flexible and transparent way.
Data replication from database and file sources consume less compute time and therefore costs less for Rivery, so we’re passing these savings onto our customers.
If you have the need to replicate data frequently from a certain application (API) in order to fulfill near real-time data analytics or operational use cases (i.e. sync Salesforce data every 10 minutes), you have the option to mark this data source for API High-frequency syncs. By doing so, the BDU credits for that source will be calculated as if that source is a database instead of a standard application (API), providing you better savings considering the usage nature.
If you’re not sure how many GB per month you’ll need, and want an estimate based on the number of rows, we usually use 1 row = 0.5 KB of data as a very rough estimate. This means 1 GB = about 2 million rows.
Please note: For database replication, Rivery charges based only on the amount of data transferred, regardless of the number of rows. This means transferring 2,000 rows of 60 bytes each, costs exactly the same as 12,000 rows of 10 bytes each (120,000 bytes).
Credit usage is based on data source and pipeline type:
| Data Source/Pipeline Type | Credit Usage |
| Application (API) Based Sources | By default, you’re charged 0.5 credit every time you ingest data from a single output table. If your source is configured as a High-frequency sync source (under the Pro Plus or Enterprise editions), you’re charged 1 credit per 100MB of data transferred (pro-rata), regardless of execution frequency. |
| Database Replication File Storage Sources Webhook | For standard database, files and webhook replication, you’re charged 1 credit per 100MB of data transferred (pro-rata), regardless of execution frequency. For log based CDC database replication, you’re charged 2 credits per 100MB of data transferred (pro-rata), regardless of execution frequency. |
| Orchestration & Advanced Workflows (Logic and Transformations) | You’re charged 0.5 credit for every execution of an entire workflow. |
Here are some examples:
| Scenario | Credit Usage |
| Ingesting deal information from your CRM once every 24 hours. | 0.5 credit a day |
| Ingesting both deal info & contact data (2 output tables) from your CRM every 8 hours, but just Mon-Fri. | 15 credits a week 2 output tables * 3 times a day * 5 times a week * 0.5 BDU per execution = 15 |
| Running an orchestration workflow that pulls data from 5 different API sources, once day. | 3 credits a day 5 API pulls * 0.5 BDU per execution + 1 advanced workflow * 0.5 BDU per execution = 3 |
| You transfer 1,725MB of data per month between your Postgres database and your data warehouse using standard replication. | 17.25 credits 1,725MB / 100MB = 17.25 |
| You transfer 280MB of data per month from files on SFTP servers to your data warehouse. | 2.8 credits 280MB / 100MB = 2.8 |
Please note:
- Simple “source to target” pipelines do not require setting up a workflow to execute.
- For application (API) based sources, pipelines that transfer more than 50MB of data per execution, 0.5 credit will be charged per 50MB of data. If no data is detected in the execution, the charge will be 0.5 credit.
- For databases, files, webhooks, and API High-frequency sync sources, if no data is detected in the execution, the charge will be 0 credit. The minimum amount of data moved is considered as 1MB (i.e. a data transfer of 0.8MB will be charged 0.01 credits).
Python
Python pricing is based on script execution time, server instance size, and network bandwidth.
For complete Python details and Python examples, please see our Python documentation for more.
Rivery’s free trial includes access to all of the professional plan features, for 14 days or 1,000 free credits (worth $1,200) of usage, whichever expires first.
When your trial period ends, you can continue using Rivery by registering for any on-demand plan, or by contacting us to explore our annual and Enterprise plans.
No, Rivery does not charge per connector and there is no minimum or maximum on the number of connectors you can use. We believe in providing you with the best single source to efficiently align your data from internal databases and third-party platforms.
No, Rivery does not charge per user.
The Base edition is limited to 2 users.
All other editions includes unlimited users.
No, Rivery does not charge per environment.
The Base edition is limited to 1 environment
The Professional edition is limited to 2 environments.
The Pro Plus edition is limited to 3 environments.
The Enterprise edition includes unlimited environments.
No, there is no minimum on the number of API integrations required for an account.
Yes – every data source we offer is available on all editions.
Yes! You have multiple options for connecting to practically any source, in addition to Rivery’s managed sources. Learn how.
The biggest differentiator is the completeness of Rivery’s platform, combining the ease-of-use of a no-code SaaS with the power and flexibility of a custom-coded solution.
Any user, technical or non-technical, can sign up (for free) and start building data pipelines and workflows in seconds.
On G2, users rate Rivery 9.4/10 in “ease of use,” 9.9/10 in “quality of support,” and 9.1/10 in “ease of setup.”
For more information, check out our ETL/ELT tools comparison page.
Please reach out to our sales team directly – we’d be more than happy to help.