Pricing

Free. You pay your providers.

Chickpea is Apache 2.0 software with no per-seat pricing, no metering, no account, and no license key. The only bills are the ones you already have: your model provider, and the Cloudflare account or host the deployment runs in. Chickpea adds no markup and sees none of it.

What Chickpea costs

Nothing. There is no plan to buy, no trial that expires, no seat count, and no support contract attached to the software. Deploy it, fork it, run it for your company, sell what you build on it; the license is Apache 2.0. There is no sign-up with the project and no key to request: the deploy is self-serve, and the Deploy to Cloudflare button is the whole checkout.

Plans

One plan, and it is the whole product:

PlanPriceSeatsTeammatesRequestsFeaturesSupport
Self-hosted$0 a month, foreverUnlimitedUnlimitedUnlimited, no meteringAll of them, no gatesPublic issues and discussions on GitHub

No trial period, no usage tiers, no enterprise edition held back.

There is no hosted plan. Chickpea is not a service you subscribe to; it is software you run.

What is included

  • As many named teammates as you want, each with its own handle, instructions, memory, connected accounts, GitHub repositories, schedules, and pinned model.
  • All 35 connector presets, plus any HTTP API or MCP server you add yourself.
  • Anthropic, OpenAI, OpenRouter, and Cloudflare Workers AI as model providers, chosen per teammate.
  • Scheduled work, the Admin panel, management from Slack, and the management MCP server for coding agents.
  • The security model: channel-scoped visibility, confirmation before consequential actions, credentials that never reach the model.
  • The source, under Apache 2.0, and the documentation.

Limits

Chickpea sets no limits of its own. The ones that exist come from where it runs:

  • One deployment serves one Slack workspace. A second workspace is a second deployment.
  • On Cloudflare, the Workers Paid plan is required; the Free plan cannot hold the bundle.
  • Named handles such as @support are Slack user groups, which need a paid Slack plan and a workspace policy that lets members create user groups. The first teammate, @Chickpea, needs neither.
  • On Node, state is SQLite on one host, and schedules do not run; multi-instance Node is not provided.
  • Model usage is bounded only by the rate limits and budget of your provider account.

What you pay instead

Two bills, both to accounts you already hold:

  • Your model provider, for the tokens your teammates use: Anthropic, OpenAI, OpenRouter, or Cloudflare Workers AI. Every teammate is pinned to its own model, so a triage teammate can run a cheap fast model while the one that writes runs a strong one. That pin is the main cost control you have.
  • Cloudflare, for the account the deployment runs in. The current bundle needs the Workers Paid plan ($5 a month at the time of writing) because it exceeds the Free plan's Worker size limit; Workers, Durable Objects, D1, and Workers AI usage bill to that account at Cloudflare's published rates. On Node, the bill is whatever your host costs.

What bills, and to whom:

ResourceBilled byWhenChickpea markup
Model tokensAnthropic, OpenAI, OpenRouter, or Cloudflare (Workers AI)Every request a teammate answersNone
Workers Paid planCloudflareMonthly, required for the bundle sizeNone
Workers, Durable Objects, D1, Workers AI usageCloudflarePer use, on your accountNone
Coding sandbox containerCloudflareOnly if you turn it onNone
Node hostYour providerWhatever the host costsNone
Slack paid planSlackNeeded for named handles (user groups)None
Managed connectors (optional)ComposioOnly if you opt inNone

Named teammates such as @support are Slack user groups, which need a paid Slack plan; the first teammate, @Chickpea, does not. The optional coding sandbox is the one feature with its own Cloudflare bill and is off by default. Requirements and costs in the documentation lists every resource that bills.

What a 25-person team pays a month

An estimate from published prices. A request is one mention that reads a thread, maybe calls a tool, and answers.

UsageRequests a person a weekRequests a monthChickpea licenceCloudflare planModel tokensTotal a month
Light5541$0$5$32$37
Medium202,165$0$5$130$135
Heavy505,413$0$5$325$330

Assumptions:

  • Cloudflare Workers Paid at $5 a month. Durable Objects, D1, and the cron trigger stay inside the plan's included usage at this volume.
  • Model usage at $0.06 a request on a mid-tier model, paid to the provider directly. Pick a frontier model for some teammates and that line goes up; pick a small one and it goes down.
  • Slack: named handles need a paid Slack plan, which a team of this size already has.

The comparison pages put the same team next to each alternative's published pricing.

Questions people ask

Is there a free trial?

There is nothing to trial. The software is free to run for as long as you like, with every feature, and it never expires or asks for a card.

Is there a paid plan or an enterprise edition?

No. One edition, Apache 2.0, with everything in it. Support is the public issue tracker and discussions on GitHub; there is no support contract to buy.

What will I actually be billed for?

Your model provider, for the tokens your teammates use, and Cloudflare (Workers Paid, plus usage) or whatever host runs the Node deployment. Named handles need a paid Slack plan. Chickpea adds no markup and sees none of it.

Can I run it for my company or resell what I build on it?

Yes. Apache 2.0 permits commercial use, modification, and distribution, including building a product on top of it.

Last checked

Facts on this page were checked against the source on September 4, 2026. This page is also available as markdown at /pricing.md.

More

About · ContactPrivacy · llms.txt