mesibo stands out with a truly developer-friendly and fair pricing model, ensuring you only pay for what you actually use, without hidden costs or unfair charges. With transparent pricing, robust features, and state-of-the-art algorithms, mesibo has become the most popular platform choice for massively scalable solutions without breaking the bank.
No other platform we're aware of can match mesibo's blend of comprehensive features, cutting-edge technology, and unbeatable price.
If you happen to come across one that does, let us know.
mesibo primarily offers three pricing models: self-hosted (on-premise), cloud, and for startups & non-profits.
The most popular option is to download and run the entire mesibo platform and server in your datacenter at no cost. Enterprises, financial institutes, governments, health sector, smart cities, and more deploy mesibo on-premise due to the extreme level of privacy, security, and control over your data it offers.
This model offers the most economical deployment, paying only a nominal per-user cost while maintaining complete control over infrastructure.
If you prefer to use the mesibo cloud instead of an on-premise deployment, you pay for per-user usage and resources you consume (bandwidth, database, CPU, etc). This eliminates the need to manage infrastructure internally, providing a flexible and scalable solution.
mesibo charges a slightly higher fee for cloud deployment compared to on-premise, due to the increased server infrastructure costs. Thousands of emerging apps across various sectors, including dating, health, fleet management, classrooms, events, and more, rely on mesibo's cloud services for their operations.
mesibo is completely free for educational institutions, students, research organizations, non-profit entities, climate tech startups, environmental conservation groups, and non-commercial apps aimed at social or ecological good.
mesibo offers substantial discounts and free credits to upcoming startups associated with credible incubators. For startups, mesibo offers up to $12,000 in credits, distributed monthly over a 12-month period.
You can seamlessly mix both on-premise and cloud models in one account for different apps, providing unparalleled versatility and scalability.
mesibo primarily charges based on the number of Monthly Active Users (MAU), and not based on the number of messages or calls. The table below outlines various features and metrics along with their associated monthly charges in US dollars ($) for both on-premise and cloud deployments. Many of these features are unlimited and not charged for separately. For a detailed explanation of each pricing component, please refer to the 'Pricing Notes' section below.
A user is considered active (MAU) if any real-time or backend API operations are performed on that user within a monthly billing cycle. For example, establishing a real-time connection, sending or receiving messages, making or receiving calls, etc. For on-premise deployments, all messages, calls, backend operations are free as they go through your own servers. The user is counted as one MAU regardless of how many operations are performed within the billing cycle.
For precise details on how MAU is calculated, please refer to the section 'Pricing Notes' below.
Number of simultaneous connections.
There is no limit on the number of concurrent users you can have when you host mesibo on-premise.
For mesibo cloud offering, the concurrent user limit is set at 10% of your MAU. Based on our experience, the number of simultaneous users is typically less than 5% of the MAU, so it's unlikely you'll exceed this limit. However, if you do surpass the 10% threshold, we'll compensate by billing you for an MAU count calculated as (Concurrent Users x 10).
There is no limits on number of One-to-one and Group Messages. The fair usage policy applies on cloud.
mesibo one-to-one video and voice calls are end-to-end encrypted and are completely free and unlimited. There are absolutely no charges for one-to-one video and voice media bandwidth.
There are no charges on on-premise. On cloud, mesibo only charges for the bandwidth consumed by all your participants and a nominal flat fee per participant call irrespective of minutes. There is no limit on the number of participants. Conferencing Bandwidth depends on the number of participants and video resolution used
Real-time storage includes all data stored by your apps within a monthly billing cycle, such as messages, users, groups, etc. This data is retained for the lifetime of your active app, with no limit on the maximum storage used.
Bandwidth consumed by your apps including realtime client connections, messaging, backend API, webhooks, push notifications, database connections, server-side URL previews, etc. However, media bandwidth used by video and voice calls or conferences does not count.
TURN servers dramatically increase the reliability of video and voice calling, especially when your users are behind firewalls, or non-cooperative routers, or symmetric NAT. It's ON for your apps by default. You can disable it from the mesibo console if requires.
Scripting and Chatbots are charged by the script execution duration. The duration is calculated from the time your script begins executing until it returns or otherwise terminates, rounded up to the nearest 1ms.
At mesibo, security and compliance aren't just checkboxes to charge you extra – they're core values ingrained into everything we do. We go the extra mile to safeguard your app and data with robust end-to-end encryption, and adhering to stringent compliances like GDPR, SOC2, HIPAA, and ISO 27001 – all included at no extra cost.
mesibo allows you to use your own file servers or cloud services like Amazon AWS, Amazon S3, Google Cloud Storage, Microsoft Azure, etc. for file storage. Hence, there is no restrictions on file size or charges from mesibo.
At mesibo, we ensure your app can scale seamlessly with reliable performance, backed by dedicated infrastructure and continuous feature development. To support this, we require a reasonable minimum monthly billing of $49 per account and not per apps (even if you have multiple apps). This amount is not additional; once your spending reaches $49, it won't be charged separately.
mesibo allows you to create unlimited apps from a single account, enabling flexibility and scalability for your projects. To prevent misuse, the number of apps you create should justify their usage. Therefore, any apps created beyond the initial three will incur an additional minimum billing of $29 per month per app. This ensures fair use and maintains the integrity of the service.
mesibo is completely free for educational and research institutes, students, non-profit organizations, or other non-commercial apps for a good cause. Write to us.
Assume your application has 1,000 monthly active users (MAU) and sends 20 million messages of average 50 bytes (utilizing approximately 1 GB of bandwidth). Let's calculate the monthly cost for both on-premise and cloud deployments.
The total cost for 1,000 MAU will be $10 per month for on-premise (1,000 * $0.01) and $20 per month for cloud (1,000 * $0.02).
Additionally, for cloud deployments, the concurrent user limit is set at 10% of your MAU. In this case, with 1,000 MAU, the concurrent user limit would be 100 (1,000 / 10). If you exceed this limit, say 150 concurrent users, you will be charged for 1,500 MAU (150 * 10).
You can view your live usage and cost estimates in the mesibo console. The Pricing Calculator provides an estimate based on your usage, but please note that it does not account for overheads and other features. Therefore, the estimate should be considered a minimum, and the actual cost may be higher.
To know more about MAU, concurrent users, message bandwidth and storage, refer to Notes and FAQs below.
This section provides more details about the mesibo pricing described above. We highly recommend reading through it; understanding these details will help you make the best out of mesibo's services and managing your budget effectively.
mesibo offers a free trial to help you get started without any initial cost. Upon signing up, your account will receive sufficient free credits to test and develop using the service. These free credits allow you to explore mesibo's capabilities such as real-time messaging, audio/video calling, conferencing, user management, etc. to know if mesibo meets your requirements. You can switch to the Pay-As-You-Go (PAYG) plan anytime during or after the trial period by adding credit balance to your account.
You can transition to the PAYG plan at any time by adding a credit balance of at least $50 to your account. Charges are deducted from your credit balance based on your usage of various services and the credit expiry period. You can monitor your credit balance, usage stats and validity in the 'My Account' section of the mesibo console. You can also set up webhook notifications to monitor billing updates in real-time.
A user is considered active (MAU) if any real-time or backend API operations are performed on that user within a monthly billing cycle. For example, establishing a real-time connection, sending or receiving messages, making or receiving calls, etc. For on-premise deployments, all messaging, calls, backend operations are free as they go through your own servers. The user is counted as one MAU regardless of how many operations are performed within the billing cycle.
There is no limit on concurrent users in an on-premise deployment. In Cloud deployment, the concurrent user limit will be 10% of the MAU. In our experience, simultaneous users are generally less than 5% of MAU and hence you are unlikely to cross that limit. However, in case you cross the 10% limit, it will be compensated by billing you for MAU = ( concurrent users X 10).
There is no limit on the total number of users you can create. Since we do not charge for the total users, an app can misuse and load the system by creating unlimited users without any active users. Hence to avoid misuse and to ensure fair usage, we require that your monthly active users (MAU) should be at least 25% of the total users, if not more. If your MAU are less than 25%, MAU will be counted at least (total users x 25)/100.
There is no limit on the total number of groups you can create. However, for the cloud deployment, the number of groups should not exceed four times the monthly active users (MAU). This is a practical and generous limit only to prevent misuse by any app creating unlimited groups without any active users (generally an app shouldn't require more groups than the active users). In case, the total groups exceed 4 times the MAU, the MAU will be counted at least (total groups / 4). There is no such limit on on-premise deployment.
mesibo does not charge for number of one-to-one or group messages. Instead, mesibo charges for bandwidth consumed in sending and receiving messages. You can view statistics of your traffic and storage usage in mesibo console.
A real-time connection is counted every time when your client connects to mesibo server. Your client may connect multiple times in a day because of the way mobile operating systems work. When the screen goes OFF on your mobile device, Android and iOS usually move apps to sleep state within some duration and then disconnect all the network connections to conserve system resources and battery life. Hence, apps will need to reconnect when they come out of the sleep state. While mesibo client API takes care of reconnection and your app doesn't have to do anything extra, it is worth knowing why it happens and protocol/encryption overheads associated with it.
There is an overhead associated with the secure encrypted connection (TLS) and End-to-End encryption. On an average, TLS cost is approximately 3.5KB to 6KB for the initial handshake, and approximately tens of bytes for TLS record headers plus padding on each outgoing message. For most apps, this is a small percentage of your traffic. However, it can grow large if your client makes frequent connections for a short duration. This shouldn't contribute a lot to overall traffic, however it can be a substantial if your client connects frequently for the short duration.
There is additional bandwidth overhead from signaling and protocol operations, such as initiating group calls, establishing one-on-one calls, synchronizing user profiles and message histories, generating URL previews for shared links, and other similar functionality.
mesibo uses cut-through switching to deliver your messages in real-time with minimum latency. However, if the destination is not online, mesibo stores the messages till the user is online. If you decide not to save the messages in the database, you can do so by setting a flag while sending messages using Real-time APIs.
mesibo offers an unlimited message retention period, only limited by the storage quota and usage. You can anytime clear storage from the mesibo console or by using Backend APIs.
In addition to messages, mesibo also stores users, groups, profiles, location, call logs, etc, that contributes to database usage.
Audio and Video calling minutes are unlimited in both free and paid plans. Typically, 5 to 8 messages are exchanged to setup or re-connect a voice or a video call. In addition to that, minimal messages are exchanged from each end every few seconds to keep call alive, exchange quality and control information etc. The bandwidth consumed by those messages will be counted in your billing (approx ~50 Kbytes). There are no other charges for the duration of the call or the bandwidth unless you use our TURN (relay) service.
Each backend API invocation is counted when your server sends a backend API request to the mesibo server. There is absolutely no limit on the number of backend API invocations or any kind of rate limit when invoked for creating new users, new groups, and adding new members, subject to your account balance and validity. However, for any other operations, the number of monthly invocations should not exceed ten times the number of monthly active users (MAU). This is a practical and generous limit only to prevent misuse by any app sending unlimited requests (for example, to keep getting tokens from backend APIs instead of saving them locally). In such case, the total invocations exceeding 10 times the MAU, the MAU will be counted at least (total invocations / 10). This limit does not apply to on-premise deployment for group and messaging operations. Also, there are no charges for monthly up to 1000 invocations for free accounts and 10,000 invocations for paid accounts, irrespective of MAU.
Your account will be charged at the Pay-As-You-Go rates described in the pricing table above. The usage charges start from the billing date and consist of charges for all the chargeable resources consumed in a calendar month. All the pricing and charges are in US dollars ($).
You may cancel this PAYG subscription at any time by stop using it. There is no refund of the credit balance.
We have a great support team if you have any specific questions. You can reach us at https://mesibo.com/support
Mesibo is free to start. Mesibo gives you free Credits worth $50 on sign-up which is valid for 30 days. After that, Mesibo offers you Pay as you go pricing for both its On-Premise and Cloud offerings. That means you only pay for the services you consume, and once you stop using them, there are no charges or termination fees. Refer to the Mesibo pricing page to know more about pricing.
There is a Master Service Agreement / Terms document available which is applicable to all the mesibo users. You or mesibo will not require to sign (e-sign or physically), accept, or otherwise agree to any other documentation to use mesibo services.
The free tier/credits are offered for evaluation only and hence there are fair usage limits.
Monthly Active User (MAU) represents the unique monthly active users for a monthly billing cycle.
MAU is counted only when a user connects to a mesibo server (cloud or on-premise) within a monthly billing cycle, sends a message or a message is received for the user, or any real-time or backend API operations are performed on the user, for example, create, edit, group membership, etc. In the case of on-premise, all messages and real-time API operations are performed through your server and hence not charged for. To further clarify, it will be only counted as one even for multiple operations within a monthly billing cycle.
Concurrent Users
is a metric of the maximum users connected to the mesibo server at the same time at any given moment. Typically, CU is 10% of daily active users (DAU) which is typically 50% of MAU. However, these metrics vary between apps depending on the nature of the app. Calculating and watching CU will help you determine the right mesibo plan for your app today and in the future.
Concurrent users are also referred to as peak or simultaneous connections.
mesibo multi-device feature allows your users to log in from multiple devices (app or web) simultaneously and automatically sync messages, calls, etc between them. This offers your users a consistent and seamless experience across all devices. If the multi-device feature is used, mesibo needs to maintain a real-time connection and sync database from each device and hence each additional device will be counted as a separate MAU.
If your application doesn’t require the multi-device feature, your users can still log in from multiple devices without incurring extra charges for additional users. In this scenario, when a user logs in from a new device, the connection from other devices will be terminated, allowing the user to maintain only one active connection at a time.
Message rate limit (throttling) is referred to as a total number of messages that can be sent by all your users in any given second. Typically, a message rate/second for an application like WhatsApp is 0.05% of MAU (based on public stats). mesibo assigned much higher rate limit than that so you should encounter rate limit only in rare circumstances.
Absolutely not - quality remains the same whether you are in free or a premium plan.
The mesibo charges only for the TURN bandwidth and not per-minute usage. The reason is that the TURN server is only active for a short duration, and hence it is not fair to charge for the entire call duration. Generally, the TURN server is active during the call initialization and then becomes inactive once the peer-to-peer connection is established. Hence, you will only be charged for bandwidth consumed during the active duration. The active duration can be longer if the participants are behind no-cooperative NATs/firewalls or can be a fraction of the total duration (say 30 seconds for a 60-minute call).
The bandwidth consumption depends upon the call quality and the active duration. Typically an HD (720p) call for 100 minutes will consume around 1 GB of bandwidth per participant. A non-HD call for 250 minutes consumes around 1GB per participant. Hence, depending on your call quality and TURN active duration, you can estimate the TURN bandwidth and the cost. You can use the mesibo console to monitor TURN usage and charges.
There are no limitations once you are a paid user. However, mesibo has intelligent algorithms to detect unfair usage and abuse patterns and in such conditions, requests from your users may be throttled.
The free trial has a limitation on the number of users and groups.
No, all the features are available in all the plans.
We usually do not throttle your app immediately, unless in extreme situations. We will send you an email and also inform your backend using the webhook when your app usage exceeds available credits. We will throttle or temporarily disable your app only if you do not take any action in 24 hours even after these notifications. We will further wait for 7 more days before we delete your data.
The Mesibo console is the best way to keep a tab on your usage and charges. The Mesibo console is updated at regular intervals with the usage and corresponding charges.
You are free to use Mesibo APIs and Services, within free tier limits for testing and development. Our demo apps and source code is an ideal testing ground for you to evaluate what Mesibo can do for you. You can move to the PAYG plan once your evaluation completes or the free tier limit expires, whichever is early.
Absolutely not! There are zero changes to the way you deploy your application or use our APIs irrespective of you are using our free or PAYG plan.
We have 24-hour support and monitoring available from our Singapore and United States offices. For any queries, you can contact us via email at support@mesibo.com.
Yes, refer to the next question.
mesibo is completely free for educational and research institutes, students, non-profit organizations, or other non-commercial apps for a good cause.
To avail of this offer, your app must be completely non-commercial (no charges, no ads), must not use other commercial paid services, and must attribute mesibo for the mesibo services your app is using on all the key screens. You may also need to use mesibo on-premise.
To prevent misuse of our free offer, your mesibo account must use your educational institute or non-profit organization’s email address (not the free or alumni email address). We will also require proof(s) of current affiliation with the educational institute or non-profit organization.
Once your app is ready and live on respective app stores, send us a link to review. If all is good, we will mark your app for free usage.
Our payment service provider accepts credit cards and GPay. We also accept Wire Transfers to our bank in Singapore for the larger payment (you need to be an existing paid user for making wire transfers).
The credit validity varies from 30 days to 1 year depending on the payment amount. You will see the exact validity on the payment screen when you initiate a payment and also in your invoice. You can also check validity in Mesibo Console, under “My Account -> Payment History”. Your unused credits do not carry forward and they will be invalid after the validity period.
When you buy credits, we allocate system resources for you to ensure that you have the highest level of service experience using mesibo. Since we have already allocated resources for you, we are unable to extend the validity of your credits. If you require longer validity, we recommend buying credits for a larger amount which gives you the longest duration of validity.
Mesibo sends a payment receipt after receiving each of your payments. The payment receipt is sent automatically to the account email address. Please note that we will not send payment receipts to any other email addresses (even if you request them). The payment receipt will have the following information.
Additionally, all your payment information is available in Mesibo Console, under “My Account -> Payment History” with the payment date and the amount. You can take a print of it if you need it for your records. We do not provide any additional or duplicate invoices other than those sent automatically.