Rocket.Chat Hosting

Allow several minutes for the initial startup, then open your pod in a browser or desktop app. Complete the setup wizard immediately: create the administrator account, enter your organization details and follow the workspace-registration prompts before sharing the URL. The first person to complete the administrator step controls the workspace.

Use an email address you can access for Rocket.Chat Cloud registration. Registration enables services such as mobile push notifications and marketplace access; it is separate from SMTP for your workspace's own emails. The mobile app cannot complete the initial wizard. See the setup wizard guide.

No. PikaPods sets up and runs Rocket.Chat for you, including OS and app updates and HTTPS. You won't touch Docker or a server. Your files and database stay accessible if you ever want to move them elsewhere.

Official mobile push notifications use Rocket.Chat's gateway and require a registered workspace. Community workspaces have a 10,000-push monthly quota; delivery stops when it is exhausted until the quota resets or you change to an eligible plan. Starter currently includes unlimited push for its smaller user allowance. See the push notification FAQ.

For invitations, password resets and email notifications, configure your own SMTP service in the workspace's Email settings. PikaPods does not provide email sending and blocks port 25; use a submission port such as 465 or 587. Provider charges, paid Rocket.Chat features and external call services are separate from hosting.

Yes. Add your pod URL as the workspace address in the official desktop or iOS/Android app and sign in with your workspace account. Keep both client and server on supported releases: official clients can stop connecting to an end-of-life server. Use the client compatibility guide and supported-version schedule when planning access.

Set up incremental backups to S3 in your pod settings for automatic nightly snapshots, or download your files and database yourself. We keep whole-server backups for server failures, but they aren't a per-pod restore service, so your own backup is what protects your data.

You can use Rocket.Chat instead of Slack and Microsoft Teams. PikaPods runs it for you, and you can move your files and database elsewhere.

Rocket.Chat currently documents Starter for up to 50 registered users, with many premium capabilities under usage limits. Community instead allows up to 100 concurrent users, with basic messaging, fewer integrations and the monthly push quota. Advanced identity, governance and support depend on the plan. Rocket.Chat does not recommend Community for business-critical or regulated production use. Check the plan active in your workspace and the current plan comparison; hosting does not unlock all paid features.

Standard releases have a six-month support window, while LTS releases have twelve months. After end of life, the server may keep running but security fixes end, cloud services such as the push gateway and marketplace stop working, and official clients may refuse to connect. The version schedule lists each release's deadline; an old server is not a reliable way to avoid plan changes.

No. You add prepaid credit and your pods are billed by the hour from that balance, rounded up to full hours. There are no contracts or minimum terms: delete a pod anytime and billing stops. Optional automatic top-ups keep your pods running without manual payments.

You do. And you're in full control. If you ever want to download, migrate, edit or delete your data, just enable file and database access for your pod and it will be right there.