Cloud support, billing, and escalation paths.

Use support for

• Cloud availability or auth/key issues
• Billing or account questions
• Cloud token-connection problems
• Operational follow-up after 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? Individual at $19/mo gives you unlimited requests, unlimited inference tools (slack_catch_me_up, slack_triage, slack_smart_search, slack_workflow_brief, continuity_shadow_report, continuity_asana_discrepancy_report), and optional scheduled posting for one workspace. Small team at $49/mo flat adds shared workflow profiles for up to 5 operators.
• When should I self-host? Choose self-host if you want 20 tools with full runtime control. Saved workflow profiles and slack_catch_me_up run locally in OSS; hosted adds scheduled runs while your machine is off, delivery to Slack or a signed webhook, and shared team profiles.
• 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 credentials are ephemeral by default and stored encrypted only with your consent. Asana OAuth credentials use encrypted tenant-bound storage.
• 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.