Skip to content
All systems

SuiteWright Chat

Coming soon

Team chat on your own servers — for conversations that cannot leave the company

Self-hosted team messaging for organisations whose conversations cannot sit on someone else's servers — direct messages and group chats with files, reactions, read receipts and search that stays fast as the history grows. Runs on infrastructure you control rather than a provider's. Phone app only today; there is no web client yet. In development.

Most teams do not need another chat app. The ones who do usually need it because their conversations cannot sit on someone else’s servers. The engineering that makes that worth doing is not the chat bubbles — it is the messages table.

It is partitioned by month so it stays fast as it grows, indexed for trigram search so finding a message from March does not scan a year, and idempotent on send so a retry on a bad connection posts once. There is a mobile app. There is not a web client yet, and saying otherwise would be the easiest lie on this site.

What it replaces

The jobs that eat the week

  • Company conversations living in a consumer chat app on someone else's serversThe same conversations on infrastructure you control
  • Search that crawls once the history gets longFinding a message from March without scanning a year
  • A message sent twice because the connection dropped mid-sendA retry recognised as the same message
  • Staff leaving and taking the conversation history with themHistory that belongs to the organisation

Questions

Frequently asked

Why not just use an existing chat app?

For most teams, you should. This exists for organisations that cannot put their conversations on someone else's servers — a legal, regulatory or client requirement rather than a preference. If that does not describe you, the honest advice is to use something off the shelf.

Is there a web version?

Not yet. There is a phone app for iOS and Android, and no web client — saying otherwise would be the easiest lie on this site. If a desktop client is what you need, say so, because it changes the timeline.

Will search still work when we have years of messages?

That is the part the engineering went into. The message history is organised so it stays fast as it grows rather than degrading quietly once there is a year of it, which is where most self-hosted chat gets painful.

When will it be available?

It is in development and not deployed anywhere yet. Get in touch to be told when it is ready, or to talk about what you would need from it.

SuiteWright Chat is still in development

Early pilots shape what ships. If this is close to what you need, it is worth a conversation now rather than at launch.