RelayZapEvery client inbox, in one chat channel.
Get the signal where your team already is.
In production, running our own company. We can screen-share it today.
See it step by step

The problem
A dozen inboxes don't scale.
Your team hops between mailboxes, important mail is noticed late, and the tools that promise visibility charge per seat just to show you what's arriving.
What we provide
Self-hosted email-to-chat monitoring. Mail never leaves your walls.
Any mailbox
Gmail (OAuth), Zoho Mail and any IMAP mailbox — as many as you manage.
Into the chat you use
Mattermost natively, Google Chat by webhook, or any webhook.
Per-client routing
Each client's mail to its own channel, or pooled into one.
Nothing silently dropped
Delivery tracked with cursors and de-duplication, so each message arrives once.
Attachments handled
Uploaded to the channel or summarised.
Multi-tenant and encrypted
Organisations, members and roles kept isolated; credentials encrypted at rest with rotatable keys.
Admin dashboard
Status, counts and an event log for every mailbox.
Built on open source
Docker
Mattermost
Works with
Gmail
Zoho Mail
Any IMAPMattermost
Google Chat
Any webhook
What it replaces
Visibility without per-seat inbox apps or workflow builders.
No per-mailbox automation to build and maintain, and no per-seat inbox subscription — RelayZap only monitors and relays, on your own servers. Replies still go from your normal mail client.
- Instead ofZapier / Make mail workflowsYou runRelayZap on your servers
- Instead ofPer-seat shared-inbox appsYou runMail in your team chat
- Instead ofHopping between inboxesYou runOne channel per client
What's included
Three steps. Then it runs itself.
- Deployed on your servers with Docker Compose — no RelayZap cloud
- Your mailboxes connected (Gmail, Zoho Mail, IMAP)
- Routing set up to Mattermost, Google Chat or your webhook
- Unlimited team members — no per-seat fees
- Run, patched and monitored by us
Status
LiveIn production, running our own company. We can screen-share it today.
