What to select: the free or paid plan?

Trick question. They're both awesome! If you're just starting and want to use Beebotte, the free plan is a great place to start. It is also suited for personal or amateur projects. However, if you expect large in/out messages, you'd better go for a paid plan. Anyway, we'll be happy to have you as a user whatever plan you select!

What if I need someting bigger?

You came to the right place! Contact us to discuss enterprise plan with:

• Higher usage limits
• Custom support & training
• Consultancy services

Can I cancel at any time?

Yes. Although we hate to see our friends leave, you can easily cancel your account at any time from within your admin page. Beware that if you have subscribed for annual billing, you will not be refunded for the remaining period.

What happens if I go over my limits?

Hard limitations are only applied on the free plan. For paid plans, if you exceed the limit, no worries, you will continue to use the service. We'll prompt you in advance to upgrade. The extra usage will be charged in prorata with your plan. We will upgrade your plan automatically if the extra charge is higher than the upgrade (so you pay less).

What do channel & resource mean?

A channel is an abstract concept that represents (1) a physical object like an Arduino, RaspberryPi, etc. or, (2) a virtual object like an application, Webpage, Blog, Twitter account, etc. A channel should be connected to Internet (through Ethernet, WiFi, 3G, etc.) and is expected to read and to write from and to the Beebotte Cloud platform.

A channel can be created by a user; it has a unique name, a description, a scope (public or private) and a set of resources which are the most elementary part of Beebotte. For example, consider a channel representing a mobile wheather station; it might have 3 resources: temperature, wind speed, and GPS position.

What is a message?

A message is basically any call of the API regardless of the technology being used (REST, WebSocket, MQTT).

Beebotte currently allows a maximum limit of 16 KB for inboundmessages. Each 1KB chunk of publish/subscribe data is billed as 1 message. For read API, each chunk of 64KB outbound data is billed as 1 message.

In addition, MQTT and Websockets connect, disconnect, subscribe and unsubsribe calls count as messages.

Examples:

• A client publishes a message of 4KB. This publish message will be billed as four messages. If this message is delivered to 10 subscribers, it will be accounted as 4 * 10 = 40 messages. In total, the user will be billed 4 + 40 = 44 messages.
• A client calls the read API to request latest 10000 records (persisted messages) of a resource. This results in outbound data of 200KB. The user will be billed 200/64 = 4 (rounded) messages.

What is a persistent message?

A persistent message is a message received through the API and stored in Beebotte database. Persisting messages has plenty of advantages:

• Data availability
• Historical view (i.e. variation of temperature over a period of time)
• Statistical view (i.e. daily min, max and average temperature)

Still have questions?Contact us