BeanPool is a decentralized mutual credit protocol and native mobile app that lets neighborhoods trade goods and services, federate inter-community trade without fiat money, and build resilient local wealth.
The value a community creates should stay in that community. That principle has a name, and it shapes every rule in the protocol — read what a post-extraction economy means
No lookalike tracking, data harvesting, or get-rich guru algorithms.
Beans are mutual credit for real trade — never pumped on exchanges.
No dopamine-loop doomscrolling — only real local offerings and neighbors.
No interest, no banks, and no middlemen. 100% of circulation funds your Commons.
Bootstrap your community node with Docker or install the native mobile app.
A zero-sum community exchange where value flows directly from real services between real people — click any step to explore how it works.
Deploy a lightweight sovereign node with Docker on any server or Raspberry Pi. Your community owns its data, ledger, and rules.
Cryptographic Ed25519 keys generated on your device. Your 12-word phrase restores your account anywhere. On the phone app you can also link a sign-in account, so your community node can help you back onto a new device.
Start at zero. Earn your credit floor through completed trades with diverse members, unlocked by keeping active community offers live.
Trade with neighbouring towns via Keynesian bilateral clearing connectors, while progressive circulation fees fund democratic local projects.
Not a speculative token. Not a corporate startup. A complete protocol for community sovereignty.
Trade between towns and nodes without fiat currency. Inspired by John Maynard Keynes’ Bancor and his clearing union, BeanPool Connectors let autonomous community nodes trade peer-to-peer. Beans never cross the border: each pair of nodes keeps a bridge ledger of what they owe each other in work, capped independently by each side, so neither community’s local circulation is drained. Opt-in per node.
On the phone apps your key is held in the operating system's secure storage, and you can put an optional biometric lock on the app itself. In the browser app it is held in that browser's own storage on your device. Either way it never leaves your device, and your offline 12-word phrase is the backup that depends on nobody. On the phone app you can also link an Apple, Google, Facebook or GitHub sign-in so your community node can help you back onto a new device — that path is custodial, and your node's operator could use it.
Credit lines are earned through verified multi-party trades — never bought or granted arbitrarily. Carrying a debit balance requires maintaining live active offers, ensuring all credit is backed by ongoing community commitment.
BeanPool never tracks where you are, in the background or otherwise. You decide where each post, enterprise and event sits on the map — use your location once, at the moment you place it, or drop the pin by hand. Enterprise and event pins can be marked Approximate, which rounds the spot to roughly 100 m. Pins are public: anyone who opens your community's map can see them.
A modest progressive circulation incentive (demurrage) on idle surplus balances encourages active local exchange and continuously feeds a Community Commons pool for member-voted civic projects.
A dedicated operator control plane for multi-node networks: live telemetry, automated encrypted snapshot backups (harvester), tamper-resistant audit logs, and peer health monitoring.
Direct messages between two members are end-to-end encrypted: your community's node carries them but cannot read them. Enterprise discussion threads and event chats are readable by that community's node by design, so the people running the community can moderate them — the app says so on every one of those threads.
Watch step-by-step explainer videos on mutual credit economics, Keynesian trade connectors, node deployment tutorials, and mobile app pairing.
Join decentralized community discussions, share marketplace listings, debate economic parameters, propose local projects, and connect with node operators.
Discover active communities running BeanPool nodes connecting people near you.
BeanPool is published as a Docker image for Intel/AMD and ARM64, so a node runs on a small server, a Mini PC, a NAS or a Raspberry Pi. These four commands fetch the compose file, create the network the node uses, pull the published image and start it. You name your community and set its contact details afterwards, in the node's own settings app — there is nothing to configure before it boots.
git clone https://github.com/beanpool-org/beanpool.git && cd beanpool
docker network create beanpool-shared
docker compose pull
docker compose -p beanpool up -d
Stay in the LoopGet notified about new releases, federation updates, and network milestones.