You are reaching the volumes that will be better served by our Enterprise offering, which includes:

Contact Us:   

Configure and estimate the cost

Data Sources

True False




OT Automation

API Orchestration

The pricing for the Waylay Enterprise platform is composed of:

Estimated monthly volume cost: $-     For details please see below 👇

Estimate the consumption in one month

True False

Estimated monthly cost

Total Cost
Estimated monthly cost $-
Volume discount -


Price table

Volume Discounts

Volume Discount (%)
- -
- -
- -

Waylay metrics explained


Function is a service that runs your code without provisioning or managing servers. You pay only for the compute time that you consume—there is no charge when your code is not running. When you use functions, you pay for two different things: the number of requests and duration. The price for duration depends on the amount of memory you allocate to your function and it is expressed in GB-second. In the current release, memory allocation is fixed to 128M, and you can’t change it.

If you use Waylay native functions, such as Function sensor, you are not paying for any duration, only for the request, since this function is executed within rules engine - in about 0.2 ns.


If you execute a function 10 million times in one month, and it ran for 100ms each time, your charges would be calculated as follows:
Monthly compute charges ($1 per million requests, $0.00002 per GB-s)
Total compute (seconds) = 10M * (0.1sec) = 1,000,000 seconds
Total compute (GB-s) = 1,000,000 * 128MB/1024 = 125,000 GB-s
Total price: $10 + (125000 * $0.00002) = $10 + $2.5 = $12.5

Task transitions

Task transitions occur every time a task invocation infers that any other node needs to be executed as the result of a previous node execution.
However, if the task has only one sensor, and that task runs periodically or as the cron expression, then the number of steps in that task will always be zero. Even if that task has multiple sensors, but these sensors are not connected, the number of steps for such a task will always be zero.

Example, if we have a reactive task that sends an email every time the threshold is crossed (for instance temperature reading for a sensor) and if that threshold is crossed on average twice a day, then the total number of task transitions per month will be:
30days*2 conditions of the threshold crossing sensor triggered execution of * 1 sensor (email) = 60 steps = 60* $0.025/1000 = $0.0015

Task logs storage

The price is $5 per 1GB of task logs stored.

Network egress

Network egress is the outbound data transfer and it is priced at $0.15 per GB. Inbound traffic is free.

Ingested Messages

The number of stream messages (payloads) entering in our system, regardless whether they are later stored or not. If stored, they will be present both in payload database, as well as in the metrics database, providing they come in the proper format.
Ingested message is a payload that arrives at the Broker. The cost is $0.3 per million messages.

Converter calls

Each message payload can be processed by the velocity template prior to being sent to the Broker. The cost of converter calls is $1 per million messages.

Time series database metrics

Time series database will not be metered in the first release. Please note that the cost will be $25 per 1GB per month.

TS write metrics

If the message payload has 3 metrics, one message that is stored will result in 3 data points written. The cost of writing metrics in the time series database is $5 per 10 million data points.
Example: If you have 100 devices, each sending data every 15 minutes, and each payload has three metrics, in one month you will be stiring: 100 devices * 30 days * 96 messages per day * 3 metrics = 864000 data points. Price of time series storage would be 864000 * 5/10000000 = $0.432

TS read scan

Every time you fetch data from the time series database (over UI or REST), Waylay meters the number of metrics scanned in the time series database. Please note that this is not the same as the number of returned metrics, in case your query uses the aggregates and grouping in your query.The cost is $1 per 500 million metrics scanned.
Example: If you ask for the temperature of one sensor over 1 week, and data is stored every 15 minutes, irrespectively whether the query asks for all data or the aggregate, the read scan will be metered as: 7 days * 96 points = 672
If you call this query 10 times a day, for 100 sensors, that would be in one month:
100 sensors * 30 days * 10 times a day * 672 read scans = 20160000 scans and the total price would be 20160000 * 1/500000000 = $0.04


Asset is a resource, resource type or a resource constraint. The default price is $0.2 per 100 assets and it is metered at the end of the calendar month.

Please note that the asset based pricing may be different in the Enteprise contracts, where different elements and features are combined into one bundled price per asset.

Message(payload) database

Message database holds up to 100 messages per resource.

Message database size

The cost of the database is $25 per GB per month, measured at the end of the calendar month.

Message Read Scan

It meters the number of messages read from the database. The cost is $0.1 per 100.000 object reads.

Resource database

Resource database holds metadata for resources (and all change logs), resource types and resource constraints.

Resource database size

The cost of the database is $25 per GB per month, measured at the end of the calendar month.

Resource read scan

Not metered for the moment.

Object database

The price is $0.1 per GB, metered at the end of the calendar month.

Object reads

The total number of read bytes, price is $0.15 per GB

Objects writes

The total number of write bytes, price is $0.15 per GB


The total number of alarms sent in one month. This metric includes all alarms: if the alarm is opened the count for that alarm will increase and it will be counted too. The price is $1 per 1000 alarms triggered.


Vault enables you to keep your API keys encrypted at rest. It is metered as long as there is one entry in the vault. The price of this feature is $2.

BYOML Compute time

You are not charged for the number of models uploaded, only for usage, the compute time of the machine learning models. The price is $1 per minute. The total computation time depends on the model complexity and on how often you wish to run the model per given resource. For instance, if you run a model every 15 minutes or once a day, that will highly influence the total cost, as in the latter case, the price is about 100 times cheaper.

Example: if you run one ML model per device, every 15 minutes (~100), and you have 50 devices, you will have about 50*~100*30 ~ 150K invocations per month. If you run the same ML model once per day, you get to ~1.5K executions per month for 50 devices.