What does “unlimited” actually mean here?

It means Discoflare imposes no limit. There is no message retention window, no mailbox count, no record cap, and no seat meter in the software. The only ceiling is the Cloudflare plan you deploy onto and the storage you are willing to pay Cloudflare for.

So what does it cost?

The software is $0 and MIT licensed, with no Discoflare subscription of any kind. You pay Cloudflare directly for the Workers, D1, R2, KV, Workflows, Containers, and Workers AI usage your workspace generates, and RealtimeKit separately if you enable voice huddles.

What do I need to run it?

A Cloudflare account with R2 enabled. Cloudflare asks you to complete R2 subscription checkout even if your storage remains within its free tier. Workers Paid is needed only when you enable Agent Computer and its Container backend. A domain is needed only for a custom workspace address or workspace email.

Where is workspace data stored?

Messages, mail, databases, tasks, and members use D1. Agent Computer files live in Durable Object SQLite; attachments, raw email, and large artifacts use R2. Short-lived connection tickets use KV. All of it lives in the Cloudflare account used for deployment, not in an account we control.

How does mail work without a mail vendor?

Incoming email is routed to the Worker through Cloudflare Email Routing and becomes a conversation in a shared mailbox; replies go out through the Cloudflare email binding. Internal notes stay inside the workspace, and read, send, and manage access is granted per mailbox to humans or agents.

What runs the agents?

Agents use Workers AI through the deployment’s own AI binding. Each Agent has a durable Computer backed by Durable Object SQLite and uses Cloudflare Containers for Linux execution, which is why the Workers Paid plan is required.

How are agent actions controlled?

In agent conversations, risky commands pause until an authorized member approves or rejects them. Agents are workspace members rather than sign-in identities, and configuring them requires workspace administration permission.

Can I try it before deploying?

Yes. The public sandbox is the official pilot workspace. Use it to get a feel for Discoflare before creating your own deployment.

How do I get updates?

Updates are applied in place against the same Cloudflare resources, so a workspace upgrades without migrating to a new deployment. Tagged releases in the repository are the source of what has shipped.

Open source · MIT licensed · $0 per seat

One workspace for humans and agents.

Chat, mail, databases, tasks, and AI agents—self-hosted in your own Cloudflare account. No seats, no retention window, no assistant tier.

Deploy to Cloudflare Open the sandbox

The software is free. Cloudflare usage is billed by Cloudflare.

Unlimited: message history; No 90-day cliff
Unlimited: mailboxes & addresses; On your own domain
Unlimited: databases & records; Typed fields included
$0: per seat, forever; MIT licensed

Five products, one deployment

Everything your team pays four vendors for.

Chat, mail, databases, tasks, and agents share one membership, one permission model, and one database. Nothing is a separate SKU, because there are no SKUs.

Chat that borrows from both

Slack-style channels and threads with Discord-style voice huddles. Every message you have ever sent stays searchable—nothing is hidden behind a retention upgrade.

D1 · Durable Objects

Mail on your domain

Shared mailboxes read as channels and email conversations as threads. Add as many addresses as your team needs without buying a seat for each one.

Email Routing · Email Sending · R2

Databases, not another subscription

Build workspace databases with typed fields, inline editing, filtering, and sorting. Add records until your Cloudflare plan says stop—not until a plan tier does.

Tasks that actually run

Boards with labels, dependencies, and checklists, where each run is a durable Cloudflare Workflow—resumable, cancellable, and recorded with its result.

Workflows · Durable Objects

AI with no per-seat add-on

Agents are workspace members running on Workers AI through your own binding. No vendor key, no assistant tier—you pay Cloudflare for the inference you use.

Workers AI · Containers

Your account, your data

The Worker, database, files, and live connections run in Cloudflare infrastructure you own. Update in place, read the source, fork it under MIT.

Workers · KV · R2

What runs it

Nine Cloudflare services, declared by the project and provisioned in the account you choose. There is no origin server, no vendor database, and nothing else in the path.

Workers: The workspace itself. One Worker serves the app, the API, and every live connection.
D1: Messages, mail conversations, records, tasks, members, and permissions.
R2: Attachments, raw email, and large Agent artifacts.
KV: Short-lived connection tickets.
Durable Objects: Live connection state and ordered realtime delivery.
Workflows: Task runs that survive interruption, cancellation, and retry.
Workers AI: Agent inference through the deployment’s own binding.
Containers: Linux execution for each durable Agent Computer.
Email Routing and Sending: Inbound mail into shared mailboxes, and outbound replies.

Compare

What you stop paying for.

The usual stack meters people, history, and features separately. Discoflare meters none of them, because the deployment is yours.

CapabilityThe usual stackDiscoflare

Message history

Slack’s free plan hides anything older than 90 days

Every message stays in your D1 database

Team size

Slack, Notion, and Google Workspace bill per user, per month

Invite the whole company. The software bill does not move

Mailboxes and addresses

Google Workspace charges a mailbox per person; alias counts are capped by plan

Shared mailboxes and addresses on your domain, granted per member

Databases and records

Notion prices structured work per member and gates it behind tiers

Databases, custom fields, and records with no product-imposed ceiling

Slack AI and Notion AI are per-seat add-ons on top of the seat

Workers AI usage billed by Cloudflare. Nothing per seat

Where the data lives

In the vendor’s account, under the vendor’s export rules

In your Cloudflare account, in resources you can back up and delete

The source

Closed. Product direction is controlled by the vendor

MIT licensed. Read it, run it, change it

Comparisons describe how these products are packaged and billed, not their quality. Unlimited means Discoflare sets no limit—your Cloudflare plan and storage spend are the ceiling.

Ownership

Nothing of yours runs on our side.

Plenty of tools promise “your data, your rules” and still keep a vendor control plane in the path. Discoflare Admin runs inside your own Cloudflare account. Discoflare.com may go offline without interrupting workspace chat or data.

You own

The Cloudflare account and every resource the workspace runs on
The Worker, the D1 database, the R2 buckets, and the KV namespace
Every message, mailbox, record, task, and file in the workspace
The domain and the workspace hostname
The AI binding, and every token of inference billed to you
The source, under the MIT license, forkable without permission

Discoflare owns

The source code and tagged releases published on GitHub
This website and its guided installer, which holds a Cloudflare OAuth token in your browser session for one hour and never in a database
An anonymous deployment heartbeat the workspace owner can switch off

None of these sit between you and a deployed workspace. The account-local Admin is optional for repository operators, and the source deploys the same workspace software without discoflare.com. The authority boundaries and heartbeat are itemised on the trust page.

Chat

Every message you ever sent is still here.

Public and private channels, threads, reactions, mentions, presence, pins, and files. History has no expiry date, because the database is yours and nobody upsells you your own archive.

deployment checklist

2 matches

MemberEarlier

The deployment checklist and rollback steps are attached to the release thread.

3 replies in thread

AgentToday

Found the thread and linked the verification steps.

In #operations

Workspace history stays searchable in your own database.

Mail

Mailboxes without a per-person mailbox bill.

Point your domain at the workspace and email becomes conversation. A mailbox reads as a channel, a conversation as a thread, and internal notes never leave the building. Add the addresses your team needs—support, billing, hello—without adding seats.

support@yourdomain.com

Shared mailbox

dana@acme.co

Can we move the renewal call to Thursday?

Internal note — Dana is on the enterprise trial, loop in Maya before replying.

The mailbox is a channel. The conversation is a thread.

Databases

Structured work, with the record cap removed.

Build databases with typed custom fields, edit records inline, filter and sort them, and gate schema changes by permission. They live in the same D1 database as everything else, so there is no tier to upgrade when the table grows.

Accounts

3 of 1,248

AccountStageOwner

NorthwindTrialMaya

Acme CoRenewalAlex

VertexOnboardingJun

No row limit, no per-editor fee.

Agents

Agents are members, not integrations.

Mention an agent in a channel or send it a direct message, and it answers in place. Each channel and thread keeps its own memory. They run on Workers AI through your own binding—no vendor key, no per-seat assistant tier, just the inference you actually use.

product-launch

Member

@releasebot what is still unresolved here?

releasebot

Two review comments are open and the changelog entry is missing.

Answered from this channel's own memory

Tasks

Hand off work that outlives the message.

Boards with labels, dependencies, and checklists, where assigning an agent is not the same as starting it. Every run executes as a durable Cloudflare Workflow—resumable after interruption, cancellable while running, and recorded with its configuration, progress, and result.

Update the changelog

Run 04

Configuration snapshotted

Running tools in Agent Computer

Review

Run state is durable and can be cancelled while active.

Models

Pick the model. Pay Cloudflare for it.

An Agent profile stores a Workers AI model ID, not a vendor key, so the workspace never depends on an outside AI account. Switch per Agent. Below is the range available on the deployment's own binding—from a model that costs cents per million tokens to a frontier one.

Model	Input / M tokens	Output / M tokens	Good for
@cf/zai-org/glm-4.7-flash	$0.06	$0.40	Cheapest useful default
@cf/openai/gpt-oss-20b	$0.20	$0.30	Balanced everyday agent
@cf/meta/llama-4-scout-17b-16e-instruct	$0.27	$0.85	Reads image attachments
@cf/openai/gpt-oss-120b	$0.35	$0.75	Stronger reasoning
@cf/nvidia/nemotron-3-120b-a12b	$0.50	$1.50	Long, structured work
@cf/deepseek-ai/deepseek-v4-pro-0813	$1.32	$3.96	Hardest tasks
@cf/zai-org/glm-5.3	$1.40	$4.40	Frontier tier

Cloudflare's published Workers AI rates, September 2026. The full catalogue and current prices are on Cloudflare's pricing page; your deployment's picker shows every model its binding supports.

Agent boundaries

An Agent starts with access to nothing.

Agents are workspace members, and membership is the whole of their authority. Each one also gets a durable Computer: files live in its Durable Object, while Linux commands run through an isolated Container backend.

No inherited identity

An Agent never receives a browser session or a human login. A member’s OAuth or social sign-in gives an Agent no repository, shell, credential, or deployment access.

Access is granted, never assumed

An Agent cannot enter a private Channel it has not joined, and every Mail action requires an explicit mailbox grant. Each Channel, Thread, and Task Run keeps its own isolated memory.

Risky work stops for a human

Risky conversational commands pause until an authorized member approves or rejects them. Approving one command is not the same as accepting a whole Task result.

The full boundary, including what an Agent still cannot reach, is in the Agents guide.

Cloudflare deployment

Your workspace. Your account.

Chat, mail, databases, tasks, and agents deploy as one Nuxt Worker connected to the Cloudflare services declared by the project. Updates apply in place against the same resources.

Deploy with Discoflare Deploy with GitHub

The GitHub method connects source to Workers Builds. You configure and verify every account-specific Cloudflare resource, binding, secret, hostname, and migration manually.

$ Deploying Discoflare

✓ Worker uploaded

✓ D1 database connected

✓ R2 and KV connected

✓ Durable Objects ready

Your workspace is live.

01
Install Admin
Cloudflare OAuth creates one small account-local control Worker.
02
Create the workspace
Admin provisions the first workers.dev workspace with D1, R2, KV, and its Owner setup link.
03
Start chatting
Create the Owner and enter the workspace without configuring Access, a domain, email, or Containers.
04
Add capabilities
Enable Agent Computer, Huddles, custom domains, and email later from Workspace Settings.

Pricing

There is no price list.

No seats, no tiers, no upgrade prompt when the archive grows or a tenth teammate joins. Discoflare is free and open source, and you pay Cloudflare directly for the infrastructure your workspace uses.

Self-hosted

$0/ seat / month / forever

MIT licensed, no Discoflare subscription
Chat, mail, databases, tasks, and agents included
Unlimited members, history, mailboxes, and records
In-place updates on the same Cloudflare resources
You pay Cloudflare for usage, and only Cloudflare

View source

So what does Cloudflare bill?

The base workspace can start without Workers Paid, but R2 must be enabled on the account. Agent Computer adds the $5 per month Workers Paid minimum because it uses Container execution.

Resource	Included	Rate after that
Workers requests	10 million per month	$0.30 per additional million
Worker CPU time	30 million CPU-ms per month	$0.02 per additional million
D1 rows read	25 billion per month	$0.001 per million
D1 rows written	50 million per month	$1.00 per million
D1 storage	First 5 GB	$0.75 per GB-month
R2 storage	First 10 GB-month	$0.015 per GB-month, egress always free
KV reads	10 million per month	$0.50 per million
Workflow steps	500,000 per month	$0.80 per additional 100,000
Agent Computers	25 GiB-hours memory and 375 vCPU-minutes per month	Container execution is billed per 10ms while running
Agent inference	10,000 neurons per day	$0.011 per 1,000 neurons, or the per-model token rate

Cloudflare's published rates, September 2026—confirm current pricing on Cloudflare's pricing pages. A workspace of a few dozen people usually stays inside most of these allowances; the two lines that actually move with a team are Agent inference and file storage. Voice huddles are billed separately through RealtimeKit.

FAQ

Before you deploy.

Stop renting your workspace.

Deploy Discoflare Star on GitHub