ManagedRocket.Chat
Your own Rocket.Chat instance in Frankfurt am Main. We run MongoDB and the realtime services, apply updates and are reachable when the chat stalls.
Short answers
What usually comes up before the start.
More about the data center in Frankfurt am Main where your instance runs.
A good fit: Nextcloud for files and collaboration, from the same operations team.

What we look after in your Rocket.Chat
When Rocket.Chat acts up, it is usually MongoDB or the realtime connections. We watch both, and the person on the phone knows your instance.
Your own chat instance
No shared platform: your Rocket.Chat runs isolated on its own resources. Optionally with an HA setup and blue-green deployments.
Planned updates
We roll out updates in a controlled way and close critical security gaps promptly. On request you can skip individual releases.
Messages stay in Frankfurt
Chat history, files and omnichannel data on dedicated hardware at FirstColo in Frankfurt am Main, ISO 27001, DPA on request.
Chat availability in view
We monitor realtime, presence and upload paths and step in before channels or omnichannel fail for your team.
Encrypted backups
Daily full backups including database, configuration and uploads at a second site in Germany.
Admin, LDAP & SSO
Your own domain, SSL via Let's Encrypt, LDAP/SAML/OAuth and full admin access. You manage users and channels, we run the stack.
Your Rocket.Chat, without looking after MongoDB
You want to use channels, apps and integrations, not run MongoDB and the realtime services yourself. We handle installation or migration, updates, monitoring and support for your Rocket.Chat.
Self-hosted Rocket.Chat otherwise means MongoDB, realtime services, push delivery, patches and backups. With us your instance runs isolated on its own resources in Frankfurt am Main, with your own domain and full admin access.
You manage users, channels and integrations. MongoDB, realtime services, push delivery, patches and backups are on NETZFABRIK, in Frankfurt and GDPR compliant.
Where do you stand?
Start fresh or move an existing instance: we do both.
I already run Rocket.Chat
We migrate your existing instance including message history, channels, accounts and uploads. We schedule the cutover with a maintenance window and the DNS switch.
I am starting fresh
You get a dedicated instance under your own domain, for example chat.yourcompany.com, ready within a few days.
Operated on our own infrastructure
Your instance runs in an ISO 27001 data center in Frankfurt am Main, connected through our redundant DE-CIX backbone. At NETZFABRIK, operation, updates and monitoring have been done by the same team since 2014.
- ISO 27001
- GDPR compliant
- DE-CIX
- Encrypted backups
- IPv4 & IPv6
- Frankfurt am Main
- Managed monitoring
- Dedicated hardware
- Since 2014
- Around-the-clock standby
- Located in Germany
- DPA
Run it yourself or hand it over?
Self-hosting means running MongoDB, realtime and updates yourself. As a managed service we take over the full Rocket.Chat operation for a fixed monthly price.
| Self-hosted | NETZFABRIK Managed | |
|---|---|---|
| Installation & setup | Set up the server, Rocket.Chat and reverse proxy yourself | We install your instance or migrate the existing one |
| MongoDB & realtime stack | Run the MongoDB replica set, realtime and presence yourself | We run MongoDB, realtime and presence |
| Updates & security patches | Track and apply releases and security fixes yourself | We apply updates and patches in a controlled way |
| Backups & uploads | Back up database, uploads and configuration yourself | Daily encrypted backups, restore handled by us |
| Omnichannel operation | Configure and maintain livechat and queues yourself | Omnichannel runs, you enable it in the admin panel |
| Scaling as the team grows | Plan and expand hardware yourself as you grow | We expand CPU, RAM and storage without a plan change |
| Location & GDPR | Own the location and data processing yourself | Frankfurt am Main, ISO 27001, DPA on request |
| Your ongoing effort | Maintenance, on-call and outages are on you | We take over operation, monitoring and support |
Three plans by team size
From an entry-level plan for small teams to an enterprise instance: choose your plan, including managed monitoring. Response times follow the priority level P1 to P4, the same in every plan.
Choose a plan
More users or an HA setup? Then we put the hardware together based on your numbers.
Response times for your Rocket.Chat
In the event of a system outage, we respond in under 15 minutes, 24/7, 365 days a year.
- Critical (P1)< 15 min
Total outage or suspected security incident. Please call.
24/7 on-call
- High (P2)< 1 hr
Important function disrupted, operations run with limits.
Mon to Fri, 9 am to 6 pm
- Normal (P3)< 4 hrs
One workstation affected or there is a workaround.
Mon to Fri, 9 am to 6 pm
- Low (P4)< 1 business day
Questions, requests and anything that can be planned.
Mon to Fri, 9 am to 6 pm
Contractually fixed in the SLA. The DPA is available before signing.
Questions about Rocket.Chat with us
Admin access, migration, growth and integrations: what teams ask before they start.
General & operation
Can I run Rocket.Chat under my own domain?
Where is my Rocket.Chat data stored?
Do I get my own Rocket.Chat instance?
Administration & features
Do I have full admin access to Rocket.Chat?
Can I use Rocket.Chat Omnichannel?
Are there limits on users or channels?
Migration, backups & scaling
Can you migrate my existing Rocket.Chat instance?
How are backups of my Rocket.Chat instance created?
Can my Rocket.Chat instance scale as the team grows?
Do you offer a high-availability (HA) setup for Rocket.Chat?
How is file storage for uploads handled?
Integrations, notifications & licenses