"How do we keep this running for years?"

You've built an incredible network. Routers across three buildings, a point-to-point link to the village, local services people use every day, monitoring that catches problems before anyone notices, backups, a public website. It works. And that's exactly when the most important question arrives — the one technology can't answer: if you leave tomorrow, will any of this survive?

Be honest about the failure mode. The usual ending for a project like this isn't a dramatic technical collapse. It's quieter and sadder: the person who built it moves away or burns out, a router dies, nobody knows the password or which container does what, and within a few months the whole thing is dark. The network didn't fail because the technology was bad. It failed because it depended entirely on one person, and that person is gone.

Sustainability is the work of preventing that ending. Technology is the easy part — you've done the hard technical work already. The real challenge is building a network that's embedded in its community rather than balanced on one volunteer's shoulders. That work has three dimensions, and a network needs all three.

Financial

A network that can't pay its bills doesn't last, no matter how well it's engineered. The costs are modest but real — electricity, the internet uplink, the occasional replacement router — and they recur forever. Plan for them deliberately:

• Community contributions — small, regular fees from users to cover running costs. Even a token amount changes the relationship: people who pay for something treat it as theirs, and predictable income covers the predictable bills.
• Grants and funding — NGOs, governments, and international organizations fund connectivity projects, especially ones that can show real impact (this is where your website and monitoring data earn their keep).
• Shared costs — partner with local institutions that also benefit. A school or clinic that depends on the network has good reason to help carry its costs.

Knowledge

This is the dimension most projects neglect, and it's the one that kills them. If the knowledge of how the network runs lives only in your head, the network has a single point of failure far more fragile than any disk:

• Train local people. At least two or three community members should understand the basics — enough to reboot a router, check the monitoring, and know who to call. Bring them in while you build, not as an afterthought.
• Document everything. Configurations, passwords, network diagrams, the recurring maintenance tasks. Write it down somewhere durable and shared, not on the sticky notes and in the muscle memory that vanish when you do. The change log and documentation habits from the maintenance section are this work.
• Create a maintenance calendar. Turn your knowledge into a simple checklist of monthly and quarterly tasks that someone without your expertise can follow. A network anyone can maintain is a network that survives.

Organizational

Finally, the network needs to belong somewhere other than to you:

• Community ownership. The network belongs to the community, not to the person who happened to build it. Structure it so that's true in practice — decisions, access, and responsibility shared — not just in sentiment.
• A local champion. Identify someone in the community who takes real ownership: the person who notices when something's wrong and feels responsible for fixing it. Technology spreads through people who care, not through documentation alone.
• Regular check-ins. Even from a distance, schedule periodic reviews of the network's health and the team's confidence. The VPN and monitoring you set up make this possible without being on site.

The real finish line

The network is finished when it no longer needs you. That's the goal that ties this whole chapter together: not the moment the last router comes online, but the moment the community can keep it running, fund it, fix it, and grow it on their own. Build for that day from the start — share the knowledge, share the ownership, and design yourself out of the critical path — and you'll have built something that genuinely lasts.