How we scaled Slack to support 1000s of developers

Original Article ↗ Hacker News Discussion ↗

Expectations vs. actual topic

  • Several readers initially expected a post about Stack Overflow, not Slack, due to the original “Slack Overflow” title.
  • Some wished the system auto-generated FAQ/StackOverflow-style content from Slack logs; others mentioned existing tools (e.g., Tightknit, AnswerOverflow).

Support model, scaling, and tooling

  • Railway staff describe a unified queue for email, Slack, Discord, forums, and tickets with SLOs by plan (enterprise hour-level, pro day-level, hobby best-effort).
  • Missed SLOs trigger PagerDuty escalation; support is on a rotating on-call to spread empathy and validate internal tools.
  • They interact with customers in Slack but internally work in Discord; emphasis is on keeping teams small, close to users, and building custom automations.

Email vs. chat for developer support

  • Strong split: some “hate email” and prefer real-time chat and higher engagement; others strongly prefer email for async, searchability, and user control.
  • Critics say Slack creates stress, constant pings, and manager-like context-switching pressure; supporters argue this is solvable via muting, “save for later,” and reminders.
  • Some see email as overrun by SaaS spam, using Slack as the “human” channel; others treat email as the primary, highly filterable work medium.

Slack UX, alternatives, and cost

  • Many criticize Slack’s UI: channel sprawl, confusing threads, notification overload, awkward formatting, and bugs in the editor.
  • Comparisons:
    • Discord is praised for syntax highlighting, better free-tier features, voice/video channels, and strong bot ecosystem; some would use it over Slack at work.
    • Teams is divisive: some find it more polished than Slack; others find channel UX and meeting features poor.
    • Alternatives mentioned: Zulip, Twist, Basecamp, Matrix, various forum tools; some lament the decline of classical forums and async culture.

Syntax highlighting and tech debt

  • Multiple complaints that Slack lacks proper markdown fences with syntax highlighting, unlike Discord.
  • Workarounds like /snippet or “text snippets” exist but are seen as clunky and undiscoverable.
  • A few claim Slack’s message data model and custom markup make adding inline highlighting difficult; snippets may have been added instead of fixing core messages.

Data ownership, longevity, and search

  • Concerns about losing support history in Slack: “archived” channels sometimes feel like they disappear or are outside customer control; some report 404s, others say archived content remains searchable.
  • Several people prefer email because they can centrally search, organize, and back up communication independent of any single vendor.

Matrix, freedom, and client quality

  • Some ask why not use Matrix; response: most customers are already on Slack, and the company “builds where users are.”
  • Matrix is seen as solid on the protocol side, but client UX (especially Element) is seen as the main barrier to broader adoption, despite better data control for organizations.

Commercial tools and integrations

  • Multiple mentions of third-party products offering Slack-centric support workflows (Pylon, Unblocked, yetto.app, usepylon.com).
  • Some are surprised Railway didn’t just adopt an off-the-shelf solution instead of building custom tooling.

Product policies (VNC) and abuse

  • A question about banning VNC/virtual desktops: response is that early fraud and student misuse (bypassing school restrictions) led to a blanket ban.
  • Railway now has better fraud controls and may allow VNC in clarified legitimate cases, but the platform is focused more on repo-based deployments than raw VMs.