Slack meters two things now: the seat and the agent message. Business+ is $18 a seat a month and includes 15 Slackbot messages per member per week; Pro includes none past the preview, Enterprise+ is unlimited at $45. At 10 seats that is $180 for 650 agent messages, $0.28 each, while a free self-hosted server caps the team at 250 queries a month.
Team chat TCO: seats vs agent messages
interactiveEvery default is a modelling assumption printed beside its input, not a reading from your account. Seat prices are Slack’s 15 Nov 2026 list prices; the server price is a DigitalOcean 4 GiB / 2 vCPU droplet; the per-message cost is a mid-tier model at $2 in and $10 out per million tokens with 20% retries.
Arithmetic only. It ignores Slack’s 50% first-three-months promotion, Flex Credits rate card, annual prepayment, VAT and support plans, and it assumes your agent volume per member stays flat as the team grows.
Two meters on one invoice
For ten years the price of team chat was seats multiplied by months. Nothing else moved, and a finance lead could predict the line item a year ahead.
That arithmetic stopped working this week. A self-hosted Slack alternative called agentes-chat collected 1,400 GitHub stars in six days after its first commit on 9 November, with 247 forks and 209 open issues already filed. Developers are shopping for an exit from per-seat chat. The bill they find on the other side is not necessarily smaller, because the thing being metered has changed.
Three pricing models now compete for the same team, and each one meters something different. Slack bills the seat and hands each member a weekly agent allowance. Mattermost bills the seat for a self-hosted server, and its free mode caps agent queries for the whole deployment. agentes-chat charges nothing for the software and lets the model bill land on you, with a budget attached to every agent.
What the 2026 price sheets actually say
Slack publishes four plans in US dollars. The seat price is the number everyone quotes. The agent allowance is the number that decides the invoice.
| Plan | Per seat / month | Agent allowance | Agent messages at 10 seats | Per included message | Message history |
|---|---|---|---|---|---|
| Free | $0 | Slackbot preview only | 0 | — | 90-day limit |
| Pro | $8.75 | Slackbot trial or preview | 0 | — | Unlimited |
| Business+ | $18.00 | 15 per member per week | 650 | $0.2769 | Unlimited |
| Enterprise+ | $45.00 | No weekly or lifetime limit | uncapped | — | Unlimited |
Two rows in that table do the damage. Pro, the cheapest paid seat at $8.75, treats the agent as a preview: once the trial messages are gone, Slackbot stops until the workspace upgrades or turns on metered consumption through a connected Salesforce org. That upgrade is the real entry price.
Business+ has an actual allowance, but it is weekly and it is per member. Fifteen messages is roughly three a day, so a member who debugs with the agent before lunch can be out by Thursday.
Enterprise+ is the only tier where the message limit disappears. Slack's own comparison table marks Slackbot as usage-based on Free and Pro, usage-limited on Business+, and unlimited on Enterprise+, and the help article says members of Enterprise+ organizations are not subject to weekly or lifetime message limits. That difference costs $27 a seat a month on top of Business+.
The 15 messages, measured in a working week
“Each member of a Business+ workspace can send 15 messages to Slackbot per week, starting Monday and ending Sunday. Once you reach your limit, you won’t be able to send new messages to Slackbot until it resets at 12 a.m. Monday in your time zone.”
Slack Help Center, Slackbot limits and credit usage
A month holds 4.33 weeks, so one member's allowance is 65 messages. Ten members get 650, which is the number in the fourth column of Table 1.
Put the same week in work terms, because this is where a boutique agency or a two-person product team gets caught. Two agent questions a day per person is 433 messages a month at ten seats: comfortably inside the plan. Five a day is 1,083: 433 messages past the line, every month, in the same seats, with no new hire to explain it.
What happens at the line is not a published price. Slack routes the overage through Salesforce Flex Credits and splits the meter into Standard actions (search, MCP tool calls, messages) and Advanced actions (deep research, third-party slide and document creation).
The rest is sent to a rate card rather than a number, and automatic task runs are capped separately at 15 a day. So the overage exists, is billable, and cannot be computed from the pricing page before you sign.
What surprised me was the shape of it rather than the size. The cap is generous enough to survive a demo and tight enough to bind in week three, and the plan above the cap costs more than twice as much.
What a free self-hosted server actually includes
Mattermost is the serious open-core option for teams that want the workspace on their own hardware, and its free tier is called Entry. The limits are published, which is more than most self-hosted pitches manage.
| Line | Mattermost Entry (free mode) | Mattermost Professional / Enterprise | agentes-chat (self-host) |
|---|---|---|---|
| Agent queries | 250 per month, whole server | Licence removes it | Your token bill |
| Channel message history | 10,000 across all channels | Licence removes it | Your disk |
| Push notifications | 10,000 per month | Licence removes it | Your push relay |
| Calls | 40 minutes | Licence removes it | Your TURN server |
| Playbook runs | 5 per month | Licence removes it | Not applicable |
| Software price | $0 | Annual prepaid, quote only | $0, AGPL-3.0 |
| Support | Community | Next business day | GitHub issues |
Read the first line of that table twice. A free Mattermost Entry server allows 250 agent queries a month for the entire deployment, not per seat. Ten Business+ seats include 650 messages a month between them. The free server therefore covers the agent volume of about four seats, and it caps message history at 10,000 messages across every channel, which ten people sending 30 messages a day use up in about a month.
agentes-chat sits on the other side of that line. Its repository says self-hosting is free and always will be, under AGPL-3.0 with no licence key, running on Docker Compose and Postgres, and that each agent carries a role, an owner and a budget so every model call is recorded against it. The meter is the model call, not the query, which means there is no ceiling to negotiate and no allowance to exceed.
Mattermost Professional and Enterprise are priced by quote and sold as annual prepaid seats. That is not a flaw, it is a procurement path, and it takes a purchase order and a few weeks. A team that needs the answer today is choosing between Slack and the token bill.
The line item nobody puts in the spreadsheet
Infrastructure is the cheap part. A DigitalOcean Basic droplet with 4 GiB of memory and 2 vCPUs is $24.00 a month, and weekly backups add 20%, which lands the stack at $28.80 before a single message is sent.
Your hours are the expensive part, and they are missing from almost every self-hosted comparison I have read. Somebody upgrades Postgres, rotates a token, restores a backup to check that it restores, and debugs the push notifications that stopped on Android after an OS update.
Two hours a month at $60 an hour is $120, which is more than six Business+ seats by itself. The box then costs $148.80 a month, and the number you should compare against Slack is that one, not the droplet price.
| Admin time cost | Self-host per month (2 h) | Break-even vs Pro | Break-even vs Business+ | Break-even vs Enterprise+ |
|---|---|---|---|---|
| $0/h (your time is free) | $28.80 | 3.3 | 1.6 | 0.6 |
| $30/h | $88.80 | 10.1 | 4.9 | 2.0 |
| $60/h | $148.80 | 17.0 | 8.3 | 3.3 |
| $90/h | $208.80 | 23.9 | 11.6 | 4.6 |
Read the middle row. If your hours are free, the box beats Business+ at 1.6 seats. At $60 an hour it beats it at 8.3. At $90 an hour, 11.6. Your hourly cost is the single most sensitive input in the whole comparison, and most posts leave it out because it is the one that ruins the story.
Money break-even is also not usable break-even. Past 8.3 seats the box is cheaper in cash, and past roughly four seats of agent demand the free query cap is already binding, so you are buying a licence or paying tokens on top of the server.
The same 10 seats at three usage levels
| Usage per member (10 seats) | Messages / month | Slack Business+ at $180 | Free Entry at $28.80 | Self-host + tokens | Self-host + tokens + 2 h admin |
|---|---|---|---|---|---|
| Light (2 a day) | 433 | 433 sent, 0 over | 250 cap, 183 short | $44.92 | $164.92 |
| Slack default (3 a day) | 650 | 650 sent, 0 over | 250 cap, 400 short | $52.98 | $172.98 |
| Heavy (5 a day) | 1,083 | 1,083 sent, 433 over | 250 cap, 833 short | $69.10 | $189.10 |
The trade is now explicit. Slack's cash is flat and its agent headroom is fixed. The self-hosted side starts at $28.80 and grows with usage.
Once you price two hours of admin, the cost difference narrows to almost nothing at the light end: $164.92 against $180 for the same seats. At the heavy end the self-hosted column is $189.10 for 1,083 messages, or $0.1746 each, while Slack still charges $180 for the 650 it includes and hands the other 433 to Flex Credits.

Meter your own week before you pick a plan
You cannot choose between two meters without knowing which one binds first. These three snippets count agent messages per member per ISO week, pull the same number out of Postgres, and audit the 28-day window Slack uses to decide whether a member counts as active for billing.
Three snippets: weekly meter, SQL view, seat audit
copy-readyCount agent messages per member per week, pull the same number out of Postgres, and audit who was actually active in Slack's 28-day billing window.
from collections import Counter
ALLOWANCE = 15 # agent messages per member per week on Slack Business+
EVENTS = [] # append (member_id, datetime) from your bot handler
def week_key(ts):
year, week, _ = ts.isocalendar() # ISO week, Monday based
return "%d-W%02d" % (year, week)
def usage(events):
return Counter((member, week_key(ts)) for member, ts in events)
def over_allowance(report, allowance=ALLOWANCE):
return {key: n for key, n in report.items() if n > allowance}
-- Agent messages per member for the current ISO week.
-- date_trunc('week') starts on Monday, the same day Slack resets Slackbot.
select
member_id,
date_trunc('week', sent_at) as week_start,
count(*) as agent_messages
from agent_messages
where sent_at >= date_trunc('week', now())
group by member_id, week_start
having count(*) > 15
order by agent_messages desc;
-- Slack bills a member who takes any action inside a 28-day window.
-- Run the same window on your own stack before you argue about seats.
select
member_id,
min(sent_at) as first_seen,
max(sent_at) as last_seen,
count(*) as messages_28d
from agent_messages
where sent_at >= now() - interval '28 days'
group by member_id
order by messages_28d desc;
Both queries assume a table called agent_messages with member_id and sent_at. Rename the columns to match yours; nothing else changes.
The 28-day window matters more than people expect. Slack's fair billing policy counts a member as active if they take any action inside a 28-day period, and credits prorated unused time when they go quiet.
So a seat that looks permanent on the invoice is a rolling activity count. Run the seat audit on your own stack and you will usually find two seats paying for somebody who left in September.
Who should buy the seat, and who should skip the box
Self-hosting pays when five things are true at once. Ten or more seats, because below that the fixed cost dominates every other line. Agent volume that either fits 250 queries a month or justifies a licence. One hour of admin a month rather than five. A reason to keep messages on your own hardware that survives an audit question. And somebody who can be called at 2 a.m. when the container will not start.
Three of five is a good candidate. Fewer than three and you are buying a hobby, and the invoice will never say so.
The seats pay for themselves in the other configuration: a small team, a light agent habit, and nobody who wants to own the mail server's cousin. That is most teams under ten people. It is not a compromise, it is the cheaper plan.
The Honest Catch
Every seat price here is a list price read on 15 November 2026, and Slack is running 50% off the first three months on Pro and Business+, which halves year one and changes nothing in year two. If you are modelling a single year, the seats look cheaper than this article says.
The per-message cost of $0.0372 is arithmetic, not a measurement: 12,000 input tokens at $2 per million, 700 output tokens at $10 per million, plus 20% for retries. Swap in a cheaper model and the self-hosted column falls by a factor of five; swap in a frontier model with tool loops and it rises by the same factor. The calculator puts it on a slider for exactly that reason.
Admin hours are the softest number in the article. I used two, because that is what one container with Postgres and a backup cron takes in a month when nothing breaks. Nothing breaking is not a plan, and a bad month is ten hours.
Flex Credits pricing is not published in per-message terms, so the Slack column carries a hidden overage that you cannot compute from the page. Annual prepayment discounts are unpublished too. To be honest, the comparison is a map, not a bill.
No first-person production testing is claimed. The vendor terms were read from the vendors' own pages on 15 November 2026, the modelling assumptions are printed beside every input, and the script that produced every figure in this article is checked into the repository so the arithmetic can be re-run against new prices.
Frequently asked questions
How many agent messages does Slack Business+ include?
Fifteen per member per week, resetting at 12 a.m. Monday in the workspace's time zone. At 4.33 weeks a month that is about 65 messages per member and 650 for a ten-seat workspace, which is $0.2769 per included message at the $18 seat price.
What happens after the 15 messages run out?
Slackbot stops for that member until Monday unless the workspace enables Flex Credits through a connected Salesforce org. Flex Credits meter Standard and Advanced actions against a rate card rather than a published per-message price, and automatic task runs are capped at 15 a day regardless of plan.
Is Slack Pro enough to run an AI agent?
No. On Free and Pro, Slackbot is available as a trial or preview only, and once those messages are used the agent stops until you upgrade or turn on metered consumption. If the agent is the reason you are buying chat, the real entry price is $18 a seat, not $8.75.
How many agent queries does a free Mattermost server allow?
Mattermost Entry allows 250 agent queries a month for the whole deployment, alongside 10,000 channel messages of history, 10,000 push notifications a month and 40-minute calls. The documentation notes that some of those limits take effect in a future release.
When is self-hosting cheaper than Slack?
In cash, a $28.80 server breaks even at 1.6 Business+ seats. Price two hours of admin at $60 an hour and the break-even moves to 8.3 seats; at $90 an hour it moves to 11.6. The free agent cap of 250 queries a month usually binds before the money does.
Can I run an agent chat server without paying a software licence?
Yes. agentes-chat is AGPL-3.0 with no licence key and states that self-hosting is free and always will be; Mattermost Entry runs in free mode with published limits. Both still need a server, backups, upgrades and somebody to answer the pager.
Does Slack bill for inactive members?
Slack's fair billing policy counts a member as active if they take any action within a 28-day period, and credits prorated unused time when they stop. Deactivating seats rather than leaving them idle is the difference between a seat you use and a seat you rent.
The seat-versus-usage split reappears everywhere else in the stack. The n8n Cloud versus Make comparison prices the same fight in operations and executions, the cost-per-session teardown puts a number on the token side of every agent message, and the annual-versus-monthly break-even covers what a twelve-month commitment does to these columns. If the chat server is not the whole bill, the Vercel versus Cloudflare TCO comparison prices the hosting half.
Methodology & Disclosure: Seat prices and agent allowances were read on 15 November 2026 from the Slack pricing page and Slack's Slackbot limits and credit usage article, the Mattermost editions and offerings and subscription documentation, the DigitalOcean droplet price list, the Anthropic model pricing page, and the agentes-chat repository. Token counts, retry overhead, admin hours and the hourly cost of those hours are modelling assumptions, printed beside their inputs and defaulted in the calculator so you can replace them. Every figure and the chart are generated by scripts/make_team_chat_tco_figure_20261115.py from data/team_chat_tco_20261115.json, so no number in a table was typed by hand.
No first-person production testing is claimed, and no vendor paid for placement. Any partner link on this publication carries rel="sponsored nofollow". Review rules live in the Editorial Methodology and verified corrections are logged in the Corrections Log.

Leave a Reply