What Is a Community Mesh Network?

A community mesh network is a local wireless network that the people using it own and run themselves. Each household puts up a node, a small radio on a roof, a window or a pole, and those nodes relay each other's traffic. The network belongs to everyone who plugged something in, and to no company at all.

The radios are the easy half. What makes it a community mesh rather than just a mesh is the human half: who owns which box, who has roof access, who pays for the shared internet link, and how the group decides anything. This page is about that half. For the nodes-and-hops explanation, read how mesh networks work.

What Makes a Mesh Network a Community Mesh Network

Plenty of mesh networks are not community networks. The three-pack of mesh Wi-Fi units in your living room is genuine mesh technology, owned by one household and wholly dependent on one internet contract. A hotel running mesh access points across a building is mesh too. Neither is a community mesh network.

The word community is doing specific work. It means no single owner, that the people carrying the traffic are the same people using it, and that the rules come from those people rather than from a terms-of-service document. Ownership stops at the node: the radio on your roof is yours, and you can unplug it.

That last column is the one people think about least and it matters most. Companies get sold, grants end, founders move away. A community mesh is built so the network outlives any one participant, including whoever started it.

Who Actually Owns and Runs One

In most community meshes, ownership stops at the node. You buy the radio, you own it, and you agree to relay traffic for people you may never meet. The network itself is not a thing anyone holds. It is what those agreements add up to, which is why community networks get described as a commons rather than as infrastructure.

Running one is a handful of unglamorous roles, and they usually land on different people:

• Node hosts, anyone with a roof, window or balcony that has line of sight to another node. This is most members, and the only real requirement is permission to drill.
• Installers, the few who will climb, mount brackets and aim dishes. Almost every network is bottlenecked here.
• Admins, two or three people keeping addressing, routing, DNS and monitoring sane.
• Gateway hosts, members who share an internet connection with the group, usually on a separate line.
• Organizers, whoever books the room, chases the money and answers new members. The least technical role, and the one that decides whether the project lives.

Healthy networks write down who holds each role and rotate them on purpose. Unhealthy ones have one person holding all five and no plan for the week they get the flu.

How Community Meshes Make Decisions

Because nobody is in charge, a community mesh needs an explicit agreement about what a member owes everyone else. The classic one is the Pico Peering Agreement, a deliberately short document from the free-network movement: I carry your traffic across my node for free, I publish what you need to know to use it, and I promise you no particular quality of service. Freifunk in Germany built on it. Guifi.net in Catalonia uses its own Wireless Commons License in the same spirit.

Above that baseline, groups pick a structure that fits their size and their legal system. Small networks stay an informal association with a mailing list and a monthly meeting. Larger ones incorporate as a nonprofit, a cooperative, or a foundation that can hold shared assets such as a gateway contract or an insurance policy, so no individual carries that risk personally.

Write the rules before the first argument, not during it: who may join, what the shared gateway may be used for, what happens when one member saturates it, who may go on someone else's roof, and how money gets spent. Once a network outgrows the meeting room, remote voting starts to matter, which is why auditable voting tools like Folkmoot exist.

Community Mesh Networks That Actually Exist

Guifi.net in Catalonia, Spain started in 2004 when rural households could not get service from commercial providers and began linking rooftops themselves. A foundation holds the shared infrastructure, and small local ISPs operate commercially on top of it and contribute back what they use.

Freifunk in Germany is not one network but dozens of independent local ones sharing software, a legal framework and a culture. The BATMAN routing protocol used across mesh projects came out of that scene.

NYC Mesh, founded in 2014, is volunteer-run and funded by member contributions, with install parties where volunteers mount a neighbor's rooftop antenna. It is the clearest case of a mesh growing inside a dense city with expensive incumbents.

Red Hook Wifi in Brooklyn and the Equitable Internet Initiative in Detroit both train residents as digital stewards who build and maintain the network in their own neighborhood. Red Hook's became widely known after Hurricane Sandy in 2012, when local connectivity mattered more than the internet did.

Zenzeleni Networks in Mankosi, South Africa is owned by a cooperative of the villages it serves, and Sarantaporo.gr connects rural Greek villages that commercial operators had skipped. Both exist because the alternative was nothing.

What People Actually Use a Community Mesh For

The first assumption is usually wrong. People picture a community mesh as a cheaper route to the internet, and the internet gateway is the least interesting thing about it.

Traffic that stays inside the mesh costs nobody anything and never leaves the neighborhood, which makes local services the real payoff: a chat server, a file share, a local wiki, a radio stream, a bulletin board, cameras and sensors, an offline copy of maps. When the gateway dies, all of that keeps working. That is exactly the property that matters during a storm.

It also changes who can watch. Traffic between two members never touches an ISP's logging at all, which is an unusual and concrete form of data sovereignty. The operator is your neighbors, and you can go to the meeting and ask them what they log.

Shared internet access is still useful, and most networks provide it. It is just one service the group runs, not the reason the group exists.

The Money and the Labor

Money rarely kills a community mesh. Node hardware is a one-off cost carried by whoever owns the node, and the recurring costs are small and shared: transit for the gateway, a domain, a server, sometimes insurance or a rented rooftop. Groups cover it with voluntary contributions, dues, grants, or a local business sponsoring a gateway.

Labor kills them. Every network has a small number of people who will climb in the cold and answer the message that says my internet is broken. That work is unpaid, weather-dependent and never finished, and burnout in that group ends more community networks than any technical failure does.

The projects that last treat this as the central design problem. They train new installers constantly instead of leaning on the good ones. They document configuration so a stranger can pick it up. They keep hardware boring and identical so any volunteer can swap a dead unit. And they refuse growth the group cannot maintain.

Where Community Mesh Networks Fall Down

An honest list, because these are the things people discover in year two.

• It does not create bandwidth. Internet through a shared gateway is still one connection divided among everyone using it at eight in the evening.
• Geography decides everything. Wireless links need line of sight. Hills, trees and one uncooperative landlord can make a whole block unreachable however much enthusiasm exists.
• It is not automatic privacy. Your neighbors run the routers. Keep using TLS and encrypted apps. What you gain is knowing who the operator is, not a guarantee that nobody could look.
• Support expectations are hard. Members compare the mesh to an ISP with a call center, and volunteers cannot match that.
• Thin networks are fragile. A line of nodes with no alternate path is not resilient. Density is what makes self-healing real.
• Sharing may breach your ISP contract. Reselling or sharing a residential connection is often prohibited. Check before you build.

None of this is a reason not to build one. It is the difference between a network that lasts and a pile of donated routers in somebody's garage.

Starting One Where You Live

The organizational steps come before the shopping.

1. Find two other people. A mesh with one enthusiast is a hobby. Three committed households is the smallest thing that survives someone going on vacation.
2. Check line of sight first. Stand on the roofs and look. If you cannot see each other, no purchase fixes it.
3. Write the agreement before buying anything. Adopt the Pico Peering Agreement or a page of your own covering joining, the gateway, roof access and money. One evening of work, and it prevents the argument that ends projects.
4. Pick one hardware set and stick to it, so any volunteer can fix any node.
5. Start with something that works on day one. A long-range LoRa mesh running Meshtastic gives a group real off-grid text messaging cheaply and with no rooftop work, and Blackout Labs builds that kind of hardware. It is text only, but it proves the group can operate a network together before anyone climbs a ladder.
6. Add the Wi-Fi backbone one link at a time, and the shared gateway last.

For the radio-level detail, the companion guide on how mesh networks work covers nodes, hops and routing. The rest of the WOPR Systems guides cover what to run once your neighborhood has a network of its own, including moving off Google.

Frequently asked questions

Who owns a community mesh network?

Nobody owns the whole thing. Each member owns the node on their own roof or window, and the network is what their agreements to carry each other's traffic add up to. Larger networks incorporate as a nonprofit or cooperative to hold shared assets like a gateway contract, but individual nodes stay in individual hands.

How much does it cost to join a community mesh network?

It varies by network and by what your roof needs. Typically you buy your own node hardware once, as a one-off cost, then contribute to shared running costs such as internet transit for the gateway and a server. Many groups make that contribution voluntary and waive it for members who cannot pay.

Do you need to be technical to join a community mesh network?

No. Most members simply host a node and never configure anything. Networks need roofs, ladders, meeting organizers, translators and people who answer email far more than they need extra engineers. The technical roles are usually held by two or three people, and they are rarely the reason a network struggles.

What is the difference between a community mesh network and municipal broadband?

Municipal broadband is owned by a city and run by staff answerable to elected officials, usually as wired infrastructure. A community mesh is owned node by node by residents and governed by those members directly. Municipal networks have more money and reliability. Community meshes cannot be sold off by a future council.

How many people do you need to start a community mesh network?

Three households with line of sight to each other is a workable start, and at least two of them should be willing to do installs. Below that, the project depends entirely on one person's free time. Growth after the first few links usually comes from neighbors seeing the antennas and asking about them.

Can a community mesh network replace my internet provider?

Sometimes, but treat it as a second connection first. A mesh carries local traffic well and shares one or more gateway links for the wider internet, so peak-hour capacity depends on what the group has bought. In rural areas with no real provider it can be the only option, and it works.