Estimate a workspace's monthly cost

Most of a device workspace’s cost comes from its endpoints, its parameter requests, and its stored readings. What each of them counts is in What is charged. The prices are on the Prices page (See prices in a billing account’s settings, or /prices in the web app), which needs no sign-in.

Example: 10 meters polled once a minute

Ten meters sit behind one gateway, with 5 parameters each, polled once a minute with no other reads. That is 50 parameters × 1,440 reads a day = 72,000 readings a day. On day d, 72,000 × d readings are kept, so month 1 keeps 1.1 million on average (days 1 to 30) and month 12 keeps 24.9 million (days 331 to 360). With a 90-day retention, 6.48 million readings are kept every day from day 90 on.

Usage	Month 1	Month 12, keep everything	Each month after day 90, 90-day retention
Endpoints	1 endpoint	1 endpoint	1 endpoint
Parameter requests	2.16 million	2.16 million	2.16 million
Stored readings	1.1 million	24.9 million	6.48 million

Multiply each row by its price on the Prices page.

Estimate the cost

1. Open the Prices page.
2. Count the Endpoints for the share of the month they are enabled, and the Static VPN addresses of WireGuard endpoints. Devices on one Modbus TCP connection, such as meters behind one gateway, share its endpoint.
3. Work out the Parameter requests for 30 days: parameters read × reads per day × 30. Each parameter counts, so a meter read for 5 parameters counts 5. Add the reads that live views, dashboards, and automations make.
4. Work out the Stored readings: the number of readings kept, on average over the month, in millions. Every successful read is stored. The number grows every month until readings reach the retention limit, then stays level. With Keep everything, the default, it keeps growing.
5. Multiply each quantity by its price: per endpoint per month, per million requests, and per million records per month.
6. Add the other kinds of usage you expect, such as assistant replies, SMS, or files.

Extra reads, such as live views, are counted as requests and as stored readings. A live read that replaces a background reading is stored only once, so the estimate can be slightly high.

To keep the stored readings cost level, set a retention; see Manage stored data.

Get an estimate from Overvis

• Ask the assistant, for example “estimate connecting 10 meters and storing their data for 1 year”. It states what it assumed, asks what would change the total most, and can build a calculator dashboard you can adjust.
• Call billing.estimate, which needs no sign-in. Describe the devices in groups, plus monthly amounts of anything else; it returns the cost of each month and the month the cost levels off. See billing.estimate.
• In a dashboard, price the same profile with a billing.estimate source of a document, or with estimateCost from @overvis/hmi-shared/billing in code, so a calculator updates as you change its inputs.