Use support for
- Cloud availability or auth/key issues
- Billing or account questions
- Cloud token-connection problems
- Operational follow-up after deployment review
Support
Cloud support, billing, and escalation paths.
Support for the hosted product stays on the hosted surface. This page also answers the practical buyer questions that come up after pricing or deployment review.
Use deployment review for
- Managed rollout planning
- Workspace onboarding sequencing
- Plan/usage fit questions
- Turnkey Launch or Managed Reliability review
Buyer questions
- What does paid add? Pro at $9/mo unlocks unlimited AI tools (smart_search, catch_me_up, triage) and the scheduled morning catch-up DM (rolling out Q2 2026). Team at $49/mo flat adds shared workflow profiles, audit log, and 5 workspaces.
- When should I self-host? Choose self-host if you want 21 tools with full runtime control. Workflow profile primitives ship in OSS — the AI brain stays hosted because it needs Vectorize + Workers AI.
- How should I think about Slack's official MCP path? Use official vs managed when the question is transport ownership versus rollout and continuity.
- Where is the trust proof? Use /status, docs, account, and privacy.
Security and data handling
- Slack tokens use explicit storage modes: ephemeral by default, persistent only with consent.
- Slack responses are processed per request and not retained.
- Cloudflare Web Analytics is enabled on the hosted web pages only and does not change MCP request handling.
- Use security and procurement for the buyer-facing controls summary.
Use GitHub only for self-host
The public repository remains the source for open-source installs, self-host issues, npm/Docker usage, and repo-native bug reports.
Operating note
Operated by Revasser. Self-host support stays on GitHub; managed rollout, billing, and Cloud support stay on this hosted surface.