Pricing
BladePipe's pricing is based on pay-as-you-go billing. It charges according to the number of data rows you need to move. The unit price varies for different functions, namely, Full Data, Incremental, Verification, Correction, and Schema Migration. For different plans, the pricing varies.
Plans
Cloud (BYOC)
In a BYOC deployment model, BladePipe Worker is deployed in your local network, and the Worker is connected to the BladePipe Console on the cloud for management and control.
In BYOC model, only necessary information is kept at BladePipe Console, such as database authentication information, schema information, and performance statistics. The specific business data is maintained in your own network.
The unit price for BYOC model is shown in the table below. You can also estimate the cost based on the price calculator.
Function | Pricing |
---|---|
Full Data | 0.01 usd for 1 million rows |
Incremental | 10 usd for 1 million rows |
Verification | 0.01 usd for 1 million rows |
Correction | 0.1 usd for 1 million rows |
Schema Migration | 0.1 usd for 100 tables/schema |
Enterprise (On-premise)
In an on-premise deployment, BladePipe is completely deployed in your local network. Now we offer binary deployment method to ensure the privacy of your data.
Unlike BYOC, BladePipe Enterprise uses a prepaid license for authorized use. The license defines the number of links and duration. The price is shown in the following table:
Links | Duration | Price |
---|---|---|
1 | 1 Hour | 0.3 usd |
More examples of pricing:
Links | Duration | Price |
---|---|---|
1 | 1 month | 216.0 usd |
1 | 1 year | 2628.0 usd |
5 | 1 month | 1080.0 usd |
5 | 1 year | 13140.0 usd |
How to Choose
Both Cloud (BYOC) and Enterprise (On-premises) plan are suitable for a variety of business use cases. The main differences are as follows:
Cloud (BYOC) | Enterprise (On-Premise) | |
---|---|---|
Deployment | Private Workers connected to a public Console | Totally deployed in your own network |
Role-Based Access Control | No | Yes |
Resource | Only 1 VM (virtual machine) for Worker | Console, Worker, Meta-db all in one (need larger VM) |
Parallel DataJob * | No | Yes |
DataJob Grouping * | No | Yes |
SSO support | Username-password, LDAP | |
Customization * | No | Yes |
- Parallel DataJob: BladePipe can sync the same data using several DataJobs. The data is partitioned and synced automatically, thus the performance is significantly improved when moving a large volume of data.
- DataJob Grouping: BladePipe can group and manage related DataJobs, such as Kafka consumer groups. Different tables can be used to create multiple DataJobs for the same business purpose.
- Customization: BladePipe provides paid support for common features that are not supported yet after evaluation, such as new DataSources, new functions, etc.
How to Pay
Cloud (BYOC)
Payment
- Log in to BladePipe.
- Install a Worker.
- Add a card.
- Navigate to Settings > Payment page.
- Click Add New Card.
- Enter card info and save.
- Subscribe BladePipe.
- Navigate to Settings > Payment page.
- Choose one card already added.
- Click Subscribe.
- Create a DataJob.
Billing
BladePipe bills based on the volume of data you used. You can check the volume you used on a daily basis.
- Navigate to Settings > Billing page and check daily billing.
- Navigate to Settings > Billing > Details for more details.
BladePipe Cloud accepts payment through Stripe by using it's subscription.
Enterprise
Payment
- Log in to BladePipe and download the BladePipe On-Premise package.
- Install BladePipe On-Premise.
- Get License and activate BladePipe.
BladePipe Enterprise accepts payment through Stripe.