Community · checked 2026-10-19

Can I vibecode Slack Pro?

NOT REALLY· don't bother

Channels, threads, search and file uploads for a few people are a weekend of code, and Zulip and Mattermost already exist as ready-made servers. That's not what Slack Pro sells. You pay because everybody you work with is already in it: clients and partners in shared channels, thousands of apps posting into your channels, and push notifications that arrive on every phone. A home-built chat has none of those and carries the burden of running a server your team depends on. Build one only for a group of a dozen who all agree to move.

$8.75/moprice per seat

$105it costs you a year

multi-daybuild time

—people replaced it

Before you start

What you need on hand.

DifficultyAdvanced · Real infrastructure or OAuth work.

TimeA few days to run it and get everyone to move

Claude Code, Codex or CursorAny of them can run the prompt.
Node.js 22better-sqlite3 compiles a native module, so build tools must be installed.
A server with a domain and HTTPSA $5 VPS with Caddy works; teammates need to reach it from their phones.
SMTP credentialsFor invites and the unread digest.
Teammates who agree to switchThe slow part is people, not code.

Before you buildSlack Free shows the last 90 days of messages with 10 integrations. For a small group that talks about today's work, that may already be enough.

1. Install one agent: Claude Code, Codex, Cursor.
2. Make an empty folder and open it in the agent.
3. Paste the prompt below, press enter, and answer its questions as it builds.

The prompt

Build me a small self-hosted team chat to replace Slack Pro for a group of up to ten people. Requirements:

- Node.js 22 + TypeScript: a Fastify server with `@fastify/websocket`, and a React UI built with
  Vite. `npm start` serves http://localhost:4880; PUBLIC_URL in .env is the address people open.
- Storage: better-sqlite3 in ./data/chat.db with an FTS5 index on messages; uploads go to
  ./data/files/. Tables: users, channels (public or private), memberships, messages (thread parent,
  edited_at, deleted_at), reactions, read markers and invite tokens.
- Accounts only for people you invite: an admin creates an invite link (random token stored
  hashed, expires in 7 days); passwords hashed with `@node-rs/argon2`; sessions in an httpOnly cookie.
- Chat: public and private channels, direct messages, threads, edit and delete, emoji reactions,
  @mentions with an unread badge, and drag-and-drop uploads up to 25 MB with image previews.
- Search: SQLite FTS5 with filters for channel, person and date, limited to channels the user is in.
- Webhooks: one incoming URL per channel (a secret token) that accepts JSON `{text}`, so
  GitHub Actions or a cron job can post. Rate-limit per token.
- Notifications: web push with `web-push` for mentions and direct messages, and an email digest
  through nodemailer SMTP for anything unread after 30 minutes.
- Tests with vitest for membership checks: a user must never read a private channel's messages
  through search, history or a websocket subscription.
- No telemetry. Out of scope: shared channels with other companies, huddles and video, apps
  directory, mobile apps, end-to-end encryption, message retention rules.
- README: running behind Caddy for HTTPS, backing up ./data, and a warning that this is only worth
  it if everyone on the team agrees to move.

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.

Share on X

Max MiskowSponsoredAI agents, automations and MVPs, built for your company.Visit site ›

Then keep going

Next prompts, same folder.

The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Slack Pro.

Add a Slack import to the chat server in this folder. Requirements:

- A command `chat import-slack <export.zip>` that reads the JSON files Slack's export
  produces for public channels: users.json, channels.json and one folder of daily files per channel.
- Create channels and placeholder users for names in the export, keep the original timestamps and
  thread links, and turn Slack mentions into the new mention format.
- Keep file links as plain links with a note that the files were not exported.
- Run in dry-run mode by default, print the counts, and only write with --apply.
- Update the README, including what a Pro export does not contain.

Add slash commands to the chat server in this folder. Requirements:

- Admins register a command (name and target URL) in a settings page; when a user types
  /name args, the server POSTs JSON with the user, channel and text, signed with an HMAC header.
- The target may answer with `{text, ephemeral}`; show ephemeral replies only to the caller.
- Time out after 3 seconds with a visible error, and log each call.
- Update the README with a 20-line example bot.

Add retention rules to the chat server in this folder. Requirements:

- Per channel, an admin sets "keep forever" or "delete after N days"; a nightly job removes
  expired messages, their reactions and uploads, and rebuilds the FTS5 index entries.
- Show the rule at the top of the channel so nobody is surprised.
- A dry-run command prints what would be deleted.
- Update the README.

What you lose

Shared channels with clients and partners who already use Slack
The App Directory of more than 2,600 integrations and Workflow Builder
Reliable mobile push, huddles and screen sharing
Canvases, lists, thread summaries and huddle notes
A vendor that keeps the service up and patched

Why people still pay

A team chat is only useful if everyone is in it, and in many companies and communities everyone already is. Add the integrations that post alerts, tickets and deploys into channels, and a free tier that hides everything older than 90 days, and the $8.75 is cheap next to the cost of moving a whole team.

Moatnetwork effects integrations collaboration

Do the math

Slack Pro or your own copy?

Seats

Over

Your usage

Count my time24h ×$/h

Slack Pro, 1 yr$105

Your own copy, 1 yr$112running + build session

Paying is cheaper by$7pays for itself in 40 months

Estimate · A small VPS, a domain and SMTP at low volume. Ten Slack Pro seats on monthly billing come to $87.50 a month, so it saves money only for larger groups, not for time spent on upkeep. The build is token usage on your agent plan.

Leaving Slack Pro

Take your data, then cancel.

1 · Take your data out of Slack Pro

1As a Workspace Owner, click Admin in the sidebar, then Workspace settings > Security > Import & export data > Export.
2Pick an export date range and click Start Export; Slack emails you when it's ready, and the link opens an export page where you download the ZIP.
3On Pro the export holds messages and file links from public channels in JSON; private channels and direct messages aren't available on Pro.
4Files are exported as links, not as the files themselves: download the ones you need separately.

2 · Cancel Slack Pro

1Click Admin in the sidebar (or the workspace name) and select Manage billing.
2On the Overview tab choose Change plan details, then Downgrade to Free.
3Choose whether the change takes effect immediately or on your next renewal date.
4Click Continue to Checkout, review the details and click Downgrade Slack.

Free applies the message, file and app limits: you see only the last 90 days of messages, and free workspaces delete data after 1 year.
Guest accounts are deactivated when a workspace moves to Free.
Slack's help says that after a trial you can cancel any time and no further payments are taken, but payments already made aren't refunded.
Export before downgrading, and ask whoever needs private-channel history whether it must be kept: a Pro export can't contain it.

Checked 2026-10-19 against Slack Pro's docs: 1, 2, 3, 4, 5

The escape hatch

Don't feel like building it? These are already free.

ZulipOpen sourceApache-2.0 team chat organized by topic inside each stream, which keeps threads readable; hosted or self-hosted.★ 26k · active Oct 2026 · docker to self-host
Web, iOS, Android, mac, Windows, LinuxVisit ↗MattermostOpen sourceSelf-hosted channels, threads, playbooks and calls aimed at technical teams; paid plans add enterprise controls.★ 39k · active Oct 2026 · docker to self-host
Web, iOS, Android, mac, Windows, LinuxVisit ↗Rocket.ChatOpen sourceSelf-hosted chat server with channels, threads, guest rooms and many message bridges; paid tiers for scale and compliance.★ 46k · active Oct 2026 · docker to self-host
Web, iOS, Android, mac, Windows, LinuxVisit ↗

All 5 free alternatives to Slack Pro ›

The numbers

Slack Pro pricing

Plan	Monthly	Annual, per month	What you get
Free	$0/user	$0/user	90 days of visible message history, 10 integrations, one-to-one huddles and external messages, one workspace; data is deleted after 1 year.
Pro	$8.75/user	$7.25/user	Unlimited history, unlimited integrations, group huddles, group Slack Connect, canvases, lists, Workflow Builder, thread and huddle summaries, access logs, Google sign-in.
Business+	$18/user	$15/user	Adds SAML sign-on, SCIM, data residency, full workspace exports by application, Slackbot, AI search and daily recaps, conditional workflows, 4-hour first response.
Enterprise+	—	$45/user	Multiple workspaces, legal holds, audit logs, discovery API, information barriers, data loss prevention, HIPAA support.

Free tier: 90 days of visible history (older messages are hidden until you upgrade), 10 apps, one-to-one calls and external messages only, no canvases or lists.
Billing: Monthly or annual, per member; the page lists $8.75 a month on monthly billing and $7.25 on annual. Only members who do something in Slack in a 28-day window count as active, and the page says unused paid time is credited back.
Hidden costs: The Slackbot assistant, AI search and daily recaps are Business+ features, not Pro. New members added mid-term are billed pro rata. Payments already made aren't refunded when you downgrade after a trial.
Source: slack.com

Also on the list

Circle$89/mo · CommunityKINDA

Discord Nitro$9.99/mo · CommunityNOT REALLY

Heartbeat$49/mo · CommunityKINDA

Questions

Slack Pro, briefly

Not answered here? Tell us and we'll add it.

Ask a question ›

Free keeps 90 days of message history, 10 app integrations and one-to-one huddles and Slack Connect.

Not really. A team chat is only useful if everyone is in it, and in many companies and communities everyone already is. Add the integrations that post alerts, tickets and deploys into channels, and a free tier that hides everything older than 90 days, and the $8.75 is cheap next to the cost of moving a whole team. The prompt on this page builds the closest honest substitute.

About $8.75 a month on the Pro plan per seat, $105 a year (checked 2026-10-19).

Shared channels with clients and partners who already use Slack; The App Directory of more than 2,600 integrations and Workflow Builder; Reliable mobile push, huddles and screen sharing; Canvases, lists, thread summaries and huddle notes; A vendor that keeps the service up and patched. If any of those matter to you, keep paying.