European Space Agency
Intergovernmental space programme
Self-hosted chat API, on your servers, under your control.
Troop Messenger’s self-hosted chat API runs on infrastructure you control, so every message, call record, file and key stays inside your network. It includes voice and video calling when self-hosted, runs on air-gapped networks, and has no rate limits on your own server.
- On-Premise
- Private Cloud
- Air-Gapped
Self-Hosted by Organisations That Cannot Use Someone Else’s Cloud
Airbus Defence and Space
Defence and aerospace manufacturing
UK Hydrographic Office, Ministry of Defence
National hydrographic and defence data
Indian Air Force
Air-gapped deployment, Udaan Messenger
What Is a Self-Hosted Chat API?
A self-hosted chat API is a chat server and set of SDKs that you install and run on infrastructure you control, so every message, call record, file and encryption key stays inside your own network.
It suits apps whose customers ask where their data lives: healthcare, financial services, government, defence, and enterprise software sold to them. It is also called an on-premise chat API.
| Runs on | Linux or Windows Server |
|---|---|
| Where | Your data centre, your AWS, Azure or GCP account, or an air-gapped network |
| Rate limits | None on your own server |
| Calling | Voice, video and screen sharing, self-hosted |
| Identity | LDAP, Active Directory, SAML SSO and MFA |
| Audit | Audit logs to your Syslog server |
| Updates | Signed offline packages for air-gapped sites |
Why Teams Choose a Self-Hosted Chat API
Your customers ask where data lives.
Enterprise and public-sector buyers want messages on servers they or you control, not a vendor’s shared cloud.
Regulations follow the data.
HIPAA, GDPR and data residency rules are simpler to meet when patient, customer or citizen data never leaves your infrastructure.
Cloud pricing grows with every user.
Per-user pricing and overage charges increase costs as usage grows.
Some networks have no internet.
Defence, critical infrastructure and secure facilities need chat that runs fully offline.
Three Ways to Self-Host.None of Them Involve Our Servers.
Deployment model
Private Cloud
Runs on
Your own AWS, Azure or GCP account, in the region you choose
Built for
SaaS vendors with cloud operations and residency rules
Data leaving your perimeter
Never
Deployment model
Air-Gapped
Runs on
A fully isolated network with no internet path, updates as signed offline packages
Built for
Defence, intelligence and classified projects
Data leaving your perimeter
Never
Deployment model
On-Premise
Runs on
Your own servers behind your firewall, on Linux or Windows Server
Built for
Hospitals, banks and enterprises
Data leaving your perimeter
Never
Same API. Your infrastructure. Complete control.
Want a ready-made messenger instead of an API? See our on-premise chat server.
Built for HIPAA, GDPR and Regulated Apps
Self-hosting does not make an app compliant on its own, but it removes a vendor from your data flow and gives you the controls auditors ask for.
01
HIPAA-compliant chat apps
Patient data stays on your servers, so Troop Messenger never handles protected health information.
02
GDPR and data residency
Choose the country and data centre where every message is stored.
03
Financial services
Keep client communication inside your regulated environment, with retention you control.
04
Government and defence
Air-gapped deployments with offline licensing.
05
Audit logs
Every admin and user action logged, timestamped and exportable
06
End-to-end encryption
An add-on that encrypts on the sender’s device and decrypts only on the recipient’s.
Your Servers.Your Data.Your Decision.
Tell us your users, deployment and compliance needs. A solutions engineer replies within two business days with a sizing and a quote.
Sizing
We recommend servers for your users and calls.
Free trial
15 days, all features, on your own server.
Quote
Self-hosted licence and support, itemised.
GET IN TOUCH
Talk to our deployment team
Tell us about your requirements and we'll get back to you shortly.
Self-hosted deployment
Self-Hosted,Without the Engineering Project
Open-source chat servers hand you the code and the operational burden. Troop Messenger’s self-hosted API installs in four steps, with dedicated deployment support and a custom SLA.
- 1
Deploy with Docker or the Windows installer
Get the runtime ready.
- 2
Register
Activate your licence, online or offline.
- 3
Configure SSL
Enable secure connections.
- 4
Apply firewall policies
Open the required ports and lock down the rest.
Every Feature of the Cloud API,on Your Own Servers.
Messaging
- 1:1 and group chat
- Read receipts and recall
- Forkout and Burnout
- Unlimited search history
Voice and video
- 1:1 and group calls
- Screen sharing
- Scheduled meetings
- Join an ongoing call
Admin and security
- SAML and LDAP SSO
- Five-method MFA
- Guest access controls
- 30+ feature controls
Add-on modules
- Notify priority and SOS broadcasts
- Units and user authorization
- End-to-end encryption
- Syslog audit export
FAQ
Frequently Asked Questions
A self-hosted chat API is a chat server and set of SDKs that you install and run on infrastructure you control, so every message, call record, file and key stays inside your own network. Troop Messenger’s self-hosted chat API runs on-premise, in your cloud account or on air-gapped networks.
A self-hosted chat API runs on your own infrastructure, giving you control over data storage, deployment, access and maintenance. Unlike cloud APIs, your application does not depend on a third-party messaging server.
Yes. Troop Messenger supports air-gapped deployments for environments without internet connectivity, with offline licence activation and signed offline update packages.
Troop Messenger supports LDAP, Active Directory, SAML Single Sign-On (SSO) and Multi-Factor Authentication (MFA) to help organisations manage user identities and access.
Licensing is based on the number of users and deployment requirements. Organisations can request a customised quotation based on their expected user capacity and infrastructure needs.
Yes. The deployment can be sized according to your expected user base and communication requirements. Server capacity and architecture can be evaluated as usage grows.
Troop Messenger offers both cloud-based and on-premise API deployment models. Migration feasibility and the transition process can be evaluated based on your existing integration and deployment requirements.
Yes. It can be deployed for enterprise requirements, with infrastructure sizing and configuration determined by expected users, concurrent connections and communication workloads.
Ready to run chat on your own servers?
