<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Hosted mesibo – Install and Run mesibo on Your Own Infrastructure on mesibo documentation</title><link>https://docs.mesibo.com/on-premise/</link><description>Recent content in Self-Hosted mesibo – Install and Run mesibo on Your Own Infrastructure on mesibo documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.mesibo.com/on-premise/index.xml" rel="self" type="application/rss+xml"/><item><title>mesibo On-Premise Local Configuration</title><link>https://docs.mesibo.com/on-premise/local-configuration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/on-premise/local-configuration/</guid><description>&lt;p&gt;While mesibo On-Premise can be configured entirely through the mesibo Console, many mesibo users, particularly those in regulated industries — prefer a local configuration file — &lt;code&gt;/etc/mesibo/mesibo.conf&lt;/code&gt;, for stricter control over credentials and deployment settings. Parameters in the local file take priority over both command line arguments and console settings.&lt;/p&gt;
&lt;p&gt;Local configuration is useful in the following scenarios:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Regulatory Compliance&lt;/strong&gt; — Financial institutions, government agencies, and other security-sensitive organizations often have strict requirements that prohibit sharing database credentials with external systems. Local configuration keeps credentials entirely within your own infrastructure.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Custom Certificates&lt;/strong&gt; — Specify SSL certificate paths in the config file rather than on the command line.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Advanced Logging&lt;/strong&gt; — Enable granular, per-component logging for debugging or audit purposes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Network Configuration&lt;/strong&gt; — Override hostname validation and other server-specific settings.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="creating-the-configuration-file"&gt;Creating the Configuration File&lt;a class="td-heading-self-link" href="#creating-the-configuration-file" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;h3 id="step-1---create-the-configuration-directory"&gt;Step 1 - Create the Configuration Directory&lt;a class="td-heading-self-link" href="#step-1---create-the-configuration-directory" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Create the configuration directory on your host system if it does not already exist:&lt;/p&gt;</description></item><item><title>Hosting Backend APIs with mesibo On-Premise</title><link>https://docs.mesibo.com/on-premise/hosting-backend-apis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/on-premise/hosting-backend-apis/</guid><description>&lt;p&gt;When using mesibo On-Premise, mesibo has no access to your database. As a result, only a limited set of operations — &lt;code&gt;useradd&lt;/code&gt;, &lt;code&gt;userset&lt;/code&gt;, and &lt;code&gt;usertoken&lt;/code&gt; — can be performed through the mesibo-hosted &lt;a href="https://docs.mesibo.com/api/backend-api/"&gt;backend API&lt;/a&gt;. For all other operations such as group management or sending messages, you must use the real-time APIs, for example the &lt;a href="https://docs.mesibo.com/api/group-management/"&gt;real-time group management APIs&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For this reason, hosting the backend APIs on your own server is the recommended setup for all On-Premise deployments. When you host the backend APIs, all backend API calls go directly to your own database without passing through mesibo at all, keeping your data entirely within your control. It also gives you full access to the complete backend API, ensures your database is updated instantly for all operations, and unlocks additional endpoints like &lt;code&gt;usersget&lt;/code&gt;, &lt;code&gt;groupsget&lt;/code&gt;, and more.&lt;/p&gt;</description></item><item><title>High Availability for mesibo On-Premise</title><link>https://docs.mesibo.com/on-premise/high-availability-ha/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/on-premise/high-availability-ha/</guid><description>&lt;p&gt;mesibo On-Premise supports high availability (HA) configurations that keep your service running through server failures, hardware faults, network outages, or data center incidents. This is achieved by running multiple mesibo On-Premise instances, where one or more standby instances automatically take over if the active server becomes unavailable.&lt;/p&gt;
&lt;p&gt;mesibo offers the highest form of high availability configuration, known as M+N redundancy, where the M is the number of active servers which will serve your users and N is the number of the standby server that will take over when one of the active servers will fail. This approach provides resiliency against any kind of failure including catastrophic events by adding standby servers across the globe. M &amp;amp; N varies depending on the type of the account, M is currently 1 for on-premise.&lt;/p&gt;</description></item><item><title>Installing mesibo on-premise as Linux service without using Docker</title><link>https://docs.mesibo.com/on-premise/install-as-linux-service/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/on-premise/install-as-linux-service/</guid><description>&lt;p&gt;If you are an experienced Linux user, you can install mesibo on-premise with web-based control panel on your Linux server directly (just like any other software) without using docker. We earlier offered Amazon EC2 AMI created using this approach. However, since many mesibo users use other hosting providers, we are making all the steps, and scripts available in this document.&lt;/p&gt;
&lt;p&gt;The Pros and cons of this approach are:&lt;/p&gt;
&lt;h3 id="pros"&gt;Pros&lt;a class="td-heading-self-link" href="#pros" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Simplified setup (networking, file system access, etc)&lt;/li&gt;
&lt;li&gt;Control mesibo using Linux service manager &lt;code&gt;systemctl&lt;/code&gt; that provides more flexibility compared to docker&lt;/li&gt;
&lt;li&gt;[Optional] web-based control panel to configure and control (start/restart/stop/update) mesibo&lt;/li&gt;
&lt;li&gt;Slight performance advantage.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="cons"&gt;Cons&lt;a class="td-heading-self-link" href="#cons" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Limited Distributions, unlike the mesibo docker image which supports almost all Linux distributions, this approach is supported only on RHEL8 (Ubuntu soon) based distributions.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="prerequisites"&gt;Prerequisites&lt;a class="td-heading-self-link" href="#prerequisites" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;It is required that you refer to and try Docker-based installation first before you attempt this.&lt;/p&gt;</description></item><item><title>Configuring On-Premise Conferencing and Group Calls</title><link>https://docs.mesibo.com/on-premise/conferencing-and-group-calls/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/on-premise/conferencing-and-group-calls/</guid><description>&lt;p&gt;mesibo live is the conferencing and group calls server included with mesibo On-Premise. It runs as a separate instance from the main mesibo On-Premise server and can be scaled horizontally by running multiple instances.&lt;/p&gt;
&lt;p&gt;You can run multiple instances of the mesibo live server depending on the load. The mesibo live automatically handles load balancing across instances and scales up or down as you add or remove more instances.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; mesibo On-Premise must be running before you start mesibo live.&lt;/p&gt;</description></item><item><title>On-Premise Database Tables Schema</title><link>https://docs.mesibo.com/on-premise/database-tables-schema/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/on-premise/database-tables-schema/</guid><description>&lt;p&gt;mesibo On-Premise gives you complete access to your data. All database tables created by mesibo and the data written to them are accessible to you directly in your own database.&lt;/p&gt;
&lt;p&gt;The tables and columns listed below are safe to read from. All other tables and columns are used internally by mesibo and may be modified or removed without notice — do not access or depend on them.&lt;/p&gt;
&lt;blockquote class="warning"&gt;&lt;p&gt;Caution&lt;/p&gt;
&lt;p&gt;Never write to any table in the mesibo On-Premise database. If you need frequent read access, set up MySQL in a master-slave replication configuration so that reads are served from the replica, keeping load off the primary. Never overload the primary database with analytical or bulk queries.&lt;/p&gt;</description></item><item><title>Loadable Modules - Extending the mesibo Platform</title><link>https://docs.mesibo.com/on-premise/loadable-modules/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/on-premise/loadable-modules/</guid><description>&lt;p&gt;mesibo On-Premise&amp;rsquo;s loadable module architecture lets you extend the platform with your own code — intercepting messages, adding custom processing logic, and integrating with any external service or backend. You can build profanity filters, message translators, AI-powered chatbots connected to LLMs or services like Dialogflow, vector database lookups, IoT and robotics control systems, analytics pipelines, and more. All of this runs inside your own infrastructure with full control over your data.&lt;/p&gt;</description></item><item><title>Loadable Modules - add your own custom features to Mesibo</title><link>https://docs.mesibo.com/on-premise/loadable-modules-new/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.mesibo.com/on-premise/loadable-modules-new/</guid><description>&lt;p&gt;Imagine, if you could have the ability to process every message between your users, or could add custom features and functionalities. For example, create chatbots, filter profanity, translate messages between sender and recipient, analyze messages with machine learning and AI tools, and more. This can open up a plethora of creative possibilities for your apps. Now with mesibo modules, all of this is possible!.&lt;/p&gt;
&lt;p&gt;Mesibo is designed “&lt;strong&gt;by Developers for Developers&lt;/strong&gt;!”. As developers, we understand that a platform is very limited unless it allows its users to build more features and functionalities on it. This is how Mesibo loadable modules come in.&lt;/p&gt;</description></item></channel></rss>