Self-Hosted Deployment: Where SyncRivo Runs
SyncRivo does not offer self-hosted, private-cloud or on-premise deployment. It is a managed service hosted in the US on Google Cloud (us-central1).
When SaaS isn't an option
For some organizations, routing messages through any third-party cloud is prohibited by policy, regulation or contract. SyncRivo does not offer a self-hosted deployment for these environments. It runs only as a managed service hosted in the US on Google Cloud (us-central1). If your requirements allow a commercial US cloud service, the sections below describe how message data flows so your security team can assess it.
How the managed service handles your data
- 1
Hosting
Managed service hosted in the US on Google Cloud (us-central1). No customer-selectable region and no self-hosted option.
- 2
Network
Platforms deliver events to SyncRivo over HTTPS, and SyncRivo calls each platform's API over HTTPS. Inbound webhooks are signature-verified.
- 3
Credentials
Provider OAuth tokens are encrypted at rest. Sign-in to the dashboard is with Google or email and password, with optional MFA (TOTP, passkeys).
- 4
Message storage
Message content is not stored on the normal relay path; only message IDs are kept to keep threads, edits and reactions in sync. An optional retry queue temporarily holds undelivered messages.
How message data flows through SyncRivo
App installs and admin approval
Each platform is connected by installing the SyncRivo app for that platform, which your admins approve (for example Microsoft admin consent or a Slack workspace install). Microsoft Teams channel messages require the app to be installed to each team. Your first channel bridge is typically live during onboarding, once your Slack/Teams admins approve the app.
Relay path
When someone posts in a bridged channel, the platform sends the event to SyncRivo, which verifies it, translates formatting and mentions, and posts the message to each connected destination. Files pass through memory and are not stored. Messages are real time and typically arrive within seconds; delivery is event-driven, with no polling for channel messages.
Admin controls and logging
Admins can switch attachments, reactions, in-place edits, in-place deletes, retries and sender name display on or off per connection, and an organization can be suspended to stop relaying. SyncRivo keeps an activity log and security event history (JSON export).
Platform-specific behavior
Here is how the managed SyncRivo service connects to each messaging platform we support. Each platform's event delivery and OAuth app model shapes what your admins need to approve.
| Platform | Behavior | Known limitation |
|---|---|---|
| Slack | Events API delivers events to SyncRivo's managed endpoint; the SyncRivo app is installed in your workspace. | Messages posted by bots and apps are not relayed. Relayed messages show an APP label. |
| Microsoft Teams | Bot Framework delivers channel events to SyncRivo's managed endpoint after admin consent. | The app must be installed to each team for channel messages. SyncRivo is not FedRAMP authorized. |
| Google Chat | Chat app events are delivered to SyncRivo's managed endpoint. | Posting as the original sender, DMs and directory sync need a domain-wide delegation grant. |
| Zoom Team Chat | Webhook events are delivered to SyncRivo's managed endpoint; the app is installed from the Zoom App Marketplace. | Messages are posted from the app, not as the original sender. |
| Cisco Webex | Webhook events are delivered to SyncRivo's managed endpoint; the app is available on Webex App Hub. | Emoji reactions are not synced on Webex. |
Frequently asked questions
- Can SyncRivo be deployed on-premise or in a private cloud?
- No. SyncRivo is offered only as a managed service, hosted in the US on Google Cloud (us-central1). There is no self-hosted, private-cloud or on-premise package.
- Who should not use SyncRivo because of hosting?
- Organizations whose policy prohibits routing messages through a third-party commercial cloud service. SyncRivo is not FedRAMP authorized and is hosted in a commercial US Google Cloud region, so it is not suitable for workloads that require FedRAMP, ITAR or air-gapped environments.
- What does the managed service include?
- Bridging between Slack, Microsoft Teams, Google Chat, Webex and Zoom Team Chat (channels, threads, edits, deletes, files, @mentions and reactions where the platform supports them), cross-platform DMs and group DMs created with chat commands, directory sync, cross-organization partner connections, per-connection admin switches and a web dashboard. A BAA is available for Enterprise customers, and a DPA and sub-processor list are available.
- How does SyncRivo handle platform API authentication?
- Each platform is connected through its own OAuth app install, approved by your platform admins. Provider OAuth tokens are encrypted at rest by SyncRivo, data is encrypted in transit with TLS, and inbound webhooks are signature-verified on all five platforms.
Related integration guides
Three-Platform Bridges
Connect three enterprise messaging platforms simultaneously with SyncRivo's cross-platform bridges.