top of page

Conveyor pricing

Conveyor offers plans adapted to each type of user.

Plans range from Free, enabling you to start quickly, all the way to Enterprise, allowing you to meet strict compliance regulations. 

Features

CLI

WEB UI

Templates

 

 

users

projects

environments

clusters

core hours

Spot nodes

Batch jobs

Streaming jobs

Notebooks

Cost dashboard

 

RBAC

SSO

Roles

Productivity audit

 

cost audit

feature development

SLA

 

Support

Cloud

Free

 

Unlimited

Unlimited

1

1

5000

1

Best effort

 

Community

AWS Cloud

Team

Unlimited

Unlimited

Unlimited

1

Unlimited

 

Multiple

99%

Standard


AWS and Azure

Enterprise

 

Unlimited

Unlimited

Unlimited

Unlimited

Unlimited

Multiple

Quarterly

Quarterly

Prioritized 

SLA Tailored

 

Premium

Any cloud

The pricing is for the Conveyor platform only. It does not include pricing for any required cloud resources (e.g. compute instances, databases, ...). The baseline cloud cost for a single cluster is about 10 USD per day or about 300 USD per month.

Free

€0.00
per core hour

  • Unlimited users, projects

  • Single cluster and environment

  • 5000 core hours to play and try

  • Single RBAC role

  • AWS only

  • Community support

Team

€0.05
per core hour

Everything on the free plan and

  • Unlimited environments

  • Unlimited core hours

  • Cost dashboard

  • 99% SLA uptime

  • AWS and Azure

  • Standard support

Enterprise

Everything on the team plan and

  • Unlimited clusters

  • SSO support

  • Multiple RBAC roles

  • Productivity and cost auditing

  • Custom SLA uptime

  • Prioritized feature requests

  • Premium support

  • Any cloud

contact us 
for more info

Pricing example

Use the following steps to estimate the Conveyor and instance costs for a particular workload. 

Jobs and environments

Let’s say you have two environments (staging and production). Each environment runs 10 DAGs with each one an average of 20 tasks. We will calculate the monthly costs for only the production environment were the jobs run daily.

In our example, the 20 tasks are split into 2 types:

  • 10 Spark jobs running one mx.small driver and five mx.medium executors for 30 min.

  • 10 container jobs running one mx.medium instance for 10 min.

Compute the number of mx.medium hours

Conveyor proposes multiple job compute types. In order to simplify calculations, we convert any types's number of hours of compute back to equivalent mx.medium hours. By definition, this type has 1 cpu core and 4 GiB mem.

The mx.small has 0.5 cpu cores, so this means that 1 hour of this instance is equivalent to 0.5 hours of an mx.medium.

 

Let’s do it for the production environment.

Spark hours

Spark executor: 10 DAGs * 10 tasks * 5 executors * 1/2hour* 30days = 7500 mx.medium hours

Spark driver: 10 * 10 * 1/2 hours *30 = 1500 mx.small hours = 750 mx.medium hours.

Container hours

Container jobs: 10 * 10 * 1/2 hours *30 = 1500 mx.medium hours

Total hours

Monthly you will use 9750 mx.medium hours.

Conveyor license costs

The Conveyor license costs are computed in core-hours. Because the mx.medium has a single cpu core, you can reuse the total amount of mx.medium hours without any additional multiplication.

For the production environment this means that 9750 instance hours will cost you 487.5 EUR in licensing cost for one month using the Conveyor Team plan.

Cloud cost

An mx.medium job is a Conveyor concept. The underlying Kubernetes cluster itself can run on many types of instances. Kubernetes will scale the number of actual worker nodes for you based on the required number of cpu cores and memory. This means that for an estimation, you will need to roughly convert the mx.medium (1 cpu, 4 GiB mem) to the actually provisioned cloud instance.

 

Let’s say on AWS a mx.medium job is running on a m6i.mxlarge (4 cpu, 16 GiB mem) instance with an hourly cost of 0.214 EUR. A single mx.medium job hour is then roughly equivalent to 0.25 of a m6i.mxlarge hour, thus costing 0.0535 EUR per hour.

For our production environment, this means that the 9750 instance hours results in a cost of 521.63 EUR when running on-demand.

If you would run on spot instances, we can reduce this cost up to 90%, but let’s take a more conservative 70% reduction: 156.48 EUR.

This principle is the same on any cloud provider.

Total cost

The total conveyor cost is the sum of the license and the cloud cost.

Our monthly total cost for the production environment would be 1009.13 EUR when running on-demand, and 643.98 EUR when running on spot instances.

Didn't find what you were looking for? 

  • Is the Free plan really free?
    Yes, the free plan is Free as in Beer. It is given to you at no cost with no expectations of you. As the data plane is running within you cloud account, you will be paying for the resources consumed by it. The cost of this is estimated around 200-300 USD per month.
  • What is the consumption period of the core hours in the Free plan?
    The consumption period is one calendar month. At the beginning of every month, your counter is automatically reset.
  • What happens when I consume more than the Free plan allows?
    We won’t block you from using more than the free plan allows. We will inform you about your quota and reach out to you to move to the Team plan or Enterprise plan.
  • How do I downgrade from Team to the Free plan?
    Once you have reduced your consumption to the boundaries of the Free plan, contact support@conveyordata.com to change plan.
  • How do I terminate my account?
    Contact support@conveyordata.com to request your account termination. Within 3 business days we will get back to you and remove all cloud resources managed by Conveyor.
  • When do I need multiple clusters?
    How many clusters you need depends on the organisational structure, security policies or the amount and size of the different workloads. There is no limit on how many environments can be created within a single cluster. A cluster is however restricted to a single network segment (VPC/ VNET). Some common scenarios for multi-cluster: Your production and development environment live in disconnected network segments You are setting up a data mesh organisation and want to have a clear separation between different domains
bottom of page