Kevin Rose open-sources Ember: your own Slack on Cloudflare's free tier in a minute

The corporate messenger has long been a line item that nobody notices until the team grows to about a dozen people and the per-seat bill suddenly becomes a visible expense. Kevin Rose, the founder of Digg, is offering a workaround: he has open-sourced a project called Ember, which, by his account, can be deployed to Cloudflare's free tier in about a minute.

An important caveat up front: for now this is just an announcement in a single post on X, with no technical documentation in the text itself. Everything below relies on what Rose stated directly, plus what is known about the Cloudflare platform.

What has been claimed

According to the author, Ember is a self-hosted Slack analog. The post names four things:

• deploying to Cloudflare's free tier takes about a minute;
• the project works with Slack-compatible payloads;
• there is a built-in AI assistant;
• media attachments are supported.

The most interesting part is compatibility with the Slack format. If it is implemented the way it sounds, existing integrations such as webhooks, CI notifications, or monitoring alerts could work with minimal rework: the address changes, while the message structure stays the same. How deep this compatibility goes, and whether, for example, interactive blocks and slash commands are supported, can't be determined from the post. That is the first thing to check in the repository.

Why Cloudflare

Deploying on Cloudflare's free tier means there is no infrastructure to administer: no server to update, no bill for a virtual machine. The code runs at the network edge, and state is stored in the platform's services. For a small team, a side project, or an internal community, that is a serious argument.

But free tiers have limits. Cloudflare Workers, for example, has historically had a daily request limit, and storage and compute are capped too. In a chat, where every message, history load, and notification is a request, you can hit the ceiling faster than you'd expect. It's best to check Cloudflare's documentation for current figures, since they change.

The AI assistant is a separate question. The post doesn't say which model it runs on or where it executes. If it runs on the platform's own services, their quotas apply too. If the assistant connects via an external API key, then "zero dollars" ends exactly where tokens begin. That is not a criticism but a practical question for calculating the real cost.

Who might find it useful

There are three scenarios.

Small teams and communities. If you need a chat with history, attachments, and bots, and don't want yet another paid service, Ember looks like a quick way to try it.

Bot and integration developers. A Slack-compatible format lets you test integrations in your own sandbox, without cluttering a work workspace or running into the limits of someone else's API.

Anyone exploring the "AI inside the messenger" pattern. A ready-made open-source skeleton with an assistant can be taken apart to see how a model is wired into the message stream. That is sometimes more useful than documentation.

Limitations and what to check

Before moving a real team to Ember, it's worth answering a few questions:

• How mature is the project? This is freshly published code, not a product with support, an SLA, and a history of incidents.
• How are authorization, access rights, and data storage handled? For internal communication this matters more than any feature.
• Is there export and migration from Slack?
• What happens when the free limits run out?

The takeaway is simple. Ember is not a replacement for Slack in a corporate environment but an interesting open experiment: a messenger that runs with almost no cost and no infrastructure of your own. If you build bots, run a small community, or just want to see how a chat is put together on a serverless platform, open the repository and deploy it on a test account. The minutes it takes will be just enough to understand whether it's worth going further.