22 November, 2017

Money matters: flespi pricing explained [UPD: May 26, 2022]

We spell the flespi platform pricing policy for you to fully cover the sensitive issue of finance and leave no aspect untouched.

On our pricing page, we did our best to explain every aspect of our pricing policy clearly and concisely. But requests for clarification keep coming. So, we are putting together a more detailed commentary and complementing it with a few examples to leave no questions unanswered.

Pricing details

Below is a slightly regrouped pricing table from the website (all prices are specified per month):


FreeCommercial
Default — all you get for a fixed fee (you can’t have less)
channels23
streams13
flespi devices101 000
plugins12
calculators51 000
devices assigned to calculator1 000
storage (see clarification below)see limits by element type∞ (1 GB included)
tokens10010 000
subaccounts1 000
limits (for subaccounts)10 000
realms210
realms users510 000
SLA€ 0 (Best Effort)€ 0 (Priority)
Cost so far:€ 0€ 100
Extras — employ additional elements as your project grows (drop them if scaling down).
Available for Commercial use only.
extra channel (see clarification below)€ 30
extra stream€ 10
extra 100 devices€ 1
extra plugin€ 20
extra 100 devices assigned to calculators€ 1
extra 1 GB storage€ 1
SLA Advanced€ 900
Cost so far:€ 0€ 101+

Quick summary:

  • you cannot extend any of the limits in the Free version. E.g., you can have up to two channels, but you can’t go any further. To start scaling up, you need to switch to the Start commercial plan first.
  • you will be charged for all elements of each type present in your account even if they are disabled. So, if you have six channels, three of which are disabled, you will still be charged for all six.
  • even though the flespi panel shows the total storage volume for each element type, the storage is not redistributed between the elements. E.g., when you create two streams, you get 100 MB of storage for each one. Even if the first stream uses only 20 MB, the second one still has its 100 MB, not 180 MB.
  • storage in the Free mode is limited based on the restrictions for each element type (see the table below).
  • storage is not limited in the Commercial plans.

Platform restrictions

flespi platform imposes some storage and traffic restrictions that are generous and reasonable enough for you not to be too concerned about them. However, we want to put them straight, clarify what they mean, and give tips on how to avoid hitting them.

ResourcesFreeStartEnterpriseUltimateAction if exceeded
Platform
Maximum access tokens10010 000100 0001 000 000additional access tokens are blocked
Maximum subaccounts01 000100 0001 000 000additional subaccounts are blocked
Maximum limits010010 000100 000additional limits are blocked
Maximum realms21010010 000additional realms are blocked
Maximum realms users510 000100 0001 000 000additional realms users are blocked
REST/MQTT traffic per minute50 MB2 000 MB4 000 MB8 000 MBplatform suspended for 1 minute
REST API requests per minute20010 000200 0001 000 000platform suspended for 1 minute
Logs storage period30 days30 days30 days30 daysobsolete log records are deleted
Account inactive60 daysaccount is deleted
Telematics hub
Maximum channels21001 00010 000additional channels are blocked
Maximum streams11001 00010 000additional streams are blocked
Maximum devices1050 000500 0005 000 000additional devices are blocked
Maximum plugins11001 00010 000additional plugins are blocked
Maximum calculators51 000100 0001 000 000additional calculators are blocked
Maximum modems21010010 000additional modems are blocked
Active connections per channel55 00050 000200 000channel suspended for 1 minute
Stored data per channel100 MB10 000 MB10 000 MB10 000 MBchannel suspended for 1 minute
Channel traffic per minute10 MB100 MB1 000 MB2 000 MBchannel suspended for 1 minute
Channel messages per minute30020 000200 000500 000channel suspended for 1 minute
Stored data per stream100 MB10 000 MB10 000 MB10 000 MBnew messages are discarded
Stream traffic per minute10 MB100 MB1 000 MB2 000 MBstream suspended for 1 minute
Stored data per device100 MB10 000 MB10 000 MB10 000 MBnew messages are discarded
Plugin traffic per minute1 MB20 MB200 MB1 000 MBnew messages are discarded
Plugin messages queue size1005 00050 000200 000new messages are discarded
Storage
Maximum containers2010 0001 000 00010 000 000additional containers are blocked
Stored data per container100 MB10 000 MB10 000 MB10 000 MBnew messages are discarded
Maximum CDNs51 000100 0001 000 000additional CDNs are blocked
Stored data per CDN200 MB10 000 MB10 000 MB10 000 MBnew files are discarded
MQTT broker
Active MQTT sessions2050 0001 000 00010 000 000new sessions are discarded
Max subscriptions per MQTT session2005 0005 0005 000new subscriptions are discarded
MQTT messages per minute20 0005 000 00050 000 000500 000 000platform suspended for 1 minute
Persistent MQTT session storage100 MB1 000 MB1 000 MB1 000 MBsession is deleted
MQTT retained messages storage100 MB10 000 MB10 000 MB10 000 MBnew retained messages are not stored

Platform suspension means that all REST API requests are temporarily rejected. 

Channel suspension means that all existing channel connections are closed and the new ones are rejected on the channel's URI.

Clarification 1: storage types and calculation

We have a few different types of storage in the flespi platform — channels, streams, devices, containers, CDNs, MQTT sessions that have dedicated space to store the data.

Which types of storage do we limit?

The data stored on the flespi platform includes messages queued in the channel, device, and stream buffers, data in containers, files in CDNs, persistent MQTT sessions, and MQTT retained messages. The platform restrictions table above specifies the limits for each element type. Exceeding the limit immediately triggers the corresponding action (the right column in the table). All limits are strict and governed by the platform architecture.

We do not limit the amount of data transferred through the channel or stream!

How do we calculate your storage use?

  • We snapshot the storage used throughout the flespi platform (channels + streams + devices + containers + CDNs + MQTT sessions) every minute and calculate the daily average.
  • Based on the daily average we calculate their monthly average.
  • Round the resulting number up to the nearest gigabyte.
  • Charge you.

Example: Say, you use a Commercial plan and had one channel and one device in the system throughout the given month. The daily storage use is illustrated in the table and diagram below.

flespi storage use calculation

The average monthly use amounted to 4 000 MB.
4 000 MB — 1 000 MB included in the Commercial plan = 3 000 MB => you owe us € 3!

How to make sure I do not use too much storage?

If you notice that the messages pile up in the buffer quicker than you expected but you still want to keep your storage use within certain limits, you can go one of the two ways (or both):

  1. reduce TTL in the element settings — this will lead to messages living less in the buffer thus not accumulating that fast.
  2. read messages from the element buffer more frequently — once you read the messages from the buffer into your application, you can clear the buffer.

Clarification 2: extra elements in the platform

If your infrastructure requires more elements in the flespi platform than the Commercial plans provide by default, you are welcome to go beyond the limitations by as much as you need. At an extra cost. How will we charge you? You can find the monthly prices for extra elements in the table above or on the pricing page.

What if I use the element for less than a month?

The logic is similar to storage calculation. We will collect the daily average for each element type and average it for the given month rounding up to the closest integer where necessary.

Example: You created the fourth channel on November 1 and used it for 15 days. Then created the fifth channel on November 1 and used it for the entire month (30 days). Therefore, in November you had (5*15 + 4*15) / 30 = 4.5 = 5 channels on average.
You will pay €30 * (5 total channels — 3 default channels) = 60.

Terms of hardware integration

You can request the integration of a new device model or an entirely new protocol. This process may vary in terms of required time and efforts from our engineers, so it is usually estimated on a case-by-case basis. Here's a detailed explanation of possible scenarios.

Billing terms and conditions

Once you start using the flespi Commercial account you should be aware of the order of payments and consequences of non-payment. Below is the detailed timeline of how you are billed for flespi services:

  • You get the invoice from us for the reporting month (e.g. November) no later than five days after the end of the reporting month (December 5). 
  • You have to pay until the middle of the current month (December 15). 
  • You’ll get an additional reminder five days before the deadline (December 20). 
  • In case of non-payment of November's invoice, your account will be downgraded to the free version with consequent reduction of all limits — channels, devices, storage, etc. exceeding the free limits will be unavailable.
  • Once you pay the invoice, your limits and data will be restored immediately.
  • The first payment after the upgrade is proportional (€30, €50, €70, or €100) to the number of days left until the end of the current month and will not include actual platform usage (e.g. if you request an upgrade on January 15, the first invoice will be for €50 covering the period until January 31; the next invoice will be issued on March 1 covering the month of February and the actual consumption of the flespi resources during this month).

See more details in the Public offer contract (Section 2. Consideration to the Company).

Downgrading

Should you for any reason decide to downgrade from a Commercial to a Free account, please learn how to do this properly.

***

We understand the importance of financial matters for the business and believe that trustworthiness and openness is the best strategy. We left no aces up our sleeve and put everything in plain view. If there is still any ambiguity or confusion in our explanations, please let us know, and we’ll fix it.