Host a Slack bot
Run a self hosted Slack bot without adapting it to Slack's Deno workflow hosting. Tokay detects whether the code uses Socket Mode or the Events API and gives that shape the process or endpoint it needs.
Last updated
The bot keeps the Slack model it already uses
You do not need to create a fake web server for a Socket Mode bot or convert a Bolt application into another SDK. Paste the code or push the repository, and Tokay detects the language, packages, event model, and token environment variables.
You provide the Slack tokens as secrets. Tokay encrypts them in storage and supplies them to the bot at runtime.
Each connection type gets the right Service
Tokay keeps Socket Mode bots connected as background workers, so the process stays up and restarts after a crash or machine reboot. Events API bots run as webhook Services with an HTTPS request URL and a record of each event that arrives.
Live logs show the startup connection and later bot activity. Incident and recovery email report repeated process failures.
Related bot work stays in one Project
A Redis or Postgres connection, scheduled digest, or companion dashboard can run beside the bot without another hosting plan. Tokay creates supported databases from the connections in the code and supplies the same secrets and data to the Services that need them.
Your AI agent can complete the Slack setup
A coding agent like Claude Code or Codex can deploy the bot and return the information needed by Slack. Through Tokay's GraphQL API, it can submit the source, set the write only tokens you provide, deploy the Service, and read the startup logs. For an Events API bot, it can also return the public request URL.
Point your agent to app.tokay.io/llms.txt for the deployment protocol.
Slack's own hosting is still the direct fit for workflow apps written for its Deno SDK. Tokay is for Bolt, Socket Mode, and ordinary HTTP event handlers that need a host.
Tokay has a very generous free tier with no credit card. Get started.