The cloud, without the cloud
A community mesh network that can spread across continents with no data centres โ it runs on commodity hardware and the systems people already own, and it belongs to the people who run it.
โฆMake Cloud affordable with community Meshโฆ
A working internet connection ยท a generous heart ยท an unused or lesser-used PC / mobile / tablet โ that's all this needs.
a living mesh: laptops, workstations, spare GPUs โ anywhere on earth
Why
Commercial clouds concentrate expensive machines in data centres and rent them back to you โ metered by the second, priced across hundreds of SKUs, with egress fees that tax you for leaving. CloudLess inverts the model: the machines a trusted group already owns federate into one mesh with replication, failover, and web management built in.
โ๏ธ Commercial cloud
- Unpredictable metered bills; ~30% spend wasted on idle resources
- Egress fees โ a lock-in tax on your own data
- Your data lives in someone else's data centre
- Whole FinOps teams exist just to read the invoice
๐ธ๏ธ CloudLess mesh
- Zero marginal cost โ the hardware is already yours
- No egress fees: data moves inside your own mesh
- Privacy-first: data never leaves group hardware
- A ledger of who gave and who used โ no bills, just balance
No masters. As the network grows there are no privileged or central nodes to capture or fail โ coordination is by gossip among equals, and information is scattered across the mesh and retrievable from anywhere. No one owns the switch, because there is no switch.
Cloud AI is the first service on the mesh โ a standard chat-completions API with routing and failover, where cloud cost and privacy pain are highest. Storage, compute, and data services ride the same mesh next.
Products & services
Grouped the way a cloud catalog is โ except every service runs on your group's own hardware.
๐ง AI & Machine Learning
- Chat & completions API ยท live
- Embeddings ยท planned
- Speech to text / text to speech ยท planned
- Vision & OCR ยท planned
- Image generation ยท planned
- Vector search ยท planned
- Fine-tuning ยท planned
โ๏ธ Compute
- Batch jobs ยท planned
- Scheduled jobs ยท planned
- Containers ยท planned
- Functions ยท planned
- Media transcode ยท planned
๐๏ธ Storage
- Model commons (hash-verified) ยท in progress
- Object store ยท planned
- Backup & archive ยท planned
- Artifact registry ยท planned
๐จ Data & Messaging
- Queues & events ยท planned
- Key-value store ยท planned
- Time-series ยท planned
- Workflows ยท planned
๐ Networking
- Gateway, load balancing & failover ยท live
- Encrypted mesh membership ยท live
- Private overlay (cross-continent) ยท planned
- Internal naming ยท planned
๐ Security & Identity
- Members & API keys ยท live
- Cluster CA & mutual TLS ยท live
- Join tokens ยท in progress
- Encryption at rest + Data Guard ยท planned
- Signed audit log ยท live
๐ Management & Governance
- Web console (embedded, zero-install) ยท live
- Monitoring & health ยท live
- Usage & fair-use quotas ยท live
- Contribution ledger ยท live
- Cost calculator ยท live
- Idle-capacity alerts ยท live
๐ Onboarding
- One-command mesh (
up) ยท live - Auto runtime detection ยท live
- Join links / QR from console ยท live
- Signed release binaries ยท planned
Progress by area
| Area | Implemented | Tracker |
|---|---|---|
| Core platform โ onboarding, encrypted mesh, failover gateway, console | 4 / 4 โ | repo โ |
| Epic A โ Secure Mesh (CA, mTLS, join tokens, revocation, passkeys, signed audit) | 3 / 6 | #1โ#5, #52 โ |
| Epic B โ Model Commons (hash-verified store, cache, safe-format guard, runtime supervisor) | 5 / 5 โ | #6โ#10 โ |
| Epic C โ Accounts (per-user keys, usage, quotas) | 3 / 5 | #11โ#15 โ |
| Epic D โ Evaluation & Paper (benchmarks, churn tests) | 3 / 4 | #16โ#19 โ |
| Epic E โ Network & Onboarding (overlay, QR joins, releases) | 2 / 4 | #20โ#23 โ |
| Epic F โ Beyond Inference (speech, images, batch, storage, queues) | 0 / 12 | #24โ#35 โ |
| Epic G โ Encryption & Data Guard (at-rest, locality, shredding) | 0 / 8 | #36โ#43 โ |
| Epic H โ Billing Freedom (ledger, calculator, idle surfacing) | 3 / 3 โ | #44โ#46 โ |
| Epic I โ Community Fabric (share controls, reciprocity, geo map, locality) | 2 / 4 | #47โ#50 โ |
| Epic J โ Mobile Nodes (agent, thermal guard, 5%โ70% cap, mobile portal) | 0 / 5 | #53โ#57 โ |
| Epic K โ Open Platform & Polyglot (open API, Python & JS SDKs, plugins) | 5 / 5 โ | #58โ#62 โ |
| Epic L โ Test & Quality (regression suite, e2e mesh test, pre-merge gate, tests-required policy) | 2 / 7 | #84โ#90 โ |
| Epic M โ Data Durability & Recovery, must-do (replication, self-healing repair, encrypt-first, restore & backup, tiered storage) | 7 / 7 โ | #92โ#97, #108 โ |
| Epic N โ Mesh Expansion & Node Hosting, primary growth path (homelab community first; free-tier, grant & institutional seeds) | 0 / 4 | #98โ#101 โ |
| Epic O โ Speed by Divide & Conquer (parallel fan-out, racing, model sharding, chunked transfers, transfer compression, speed-aware scheduling) | 6 / 7 | #102โ#107, #109 โ |
| Epic P โ Mesh Cloud Offerings (compute, storage, data fabric, transit/edge, AI fabric, queue, identity, ops, devops, data lake, edge relay) | 0 / 11 | #110โ#120 โ |
| Epic Q โ End-User CLI (chat, piping, scripting) | 6 / 6 โ | #121โ#126 โ |
| Epic R โ Frictionless Joining (pre-flight checks, guided setup) | 3 / 7 | #127โ#133 โ |
| Epic S โ Security Operations & Attack Resilience (vuln scanning, tamper alerting, incident response) | 7 / 7 โ | #134โ#140 โ |
Per-feature detail with individual issue links lives on the Features tab of every node's built-in console.
Release tracker
What's landing in the project, straight from the merge queue โ latest on top, updated the moment a change merges. Every entry links to the full change and review discussion.
| Merged | Change | |
|---|---|---|
| Loading latest mergesโฆ | ||
Run a node
Three steps. Your computer joins the community mesh, shares only what you allow, and earns you service in return.
Step 1 โ Get Cloudless running. Pick your system โ we've highlighted the one you seem to be on:
- Open Terminal โ press โ+Space, type Terminal, press Return. A window appears where you can type commands โ that's all it is.
- Install Go (one-time) โ download the macOS installer from go.dev/dl and run it, like any app.
- Copy-paste this into Terminal and press Return.
git clonecreates its owncloudlessfolder โ don't make one yourself first, or you'll end up nested inside an extra empty folder of the same name:git clone https://github.com/asifontheline/cloudless cd cloudless/cloudless go build -o cloudless ./cmd/cloudless ./cloudless up
If your Mac offers to install "command line developer tools" the first time, click Install and re-run the first line.
- Open PowerShell โ press the โ Windows key, type PowerShell, press Enter. A window appears where you can type commands โ that's all it is.
- Make sure you're in a folder you own. PowerShell sometimes opens into
C:\Windows\System32or another system folder you don't have permission to write to โ paste this and press Enter to jump to your user folder first:cd $HOME
Every command below assumes you're here. If anything later fails withPermission denied, you're probably back in a system folder โ runcd $HOMEagain and retry. - Install the tools (one-time) โ paste this and press Enter:
winget install Git.Git GoLang.Go
- Close this PowerShell window completely and open a new one. This step is easy to
miss but required โ Windows only picks up
gitandgoon PATH in a fresh window; typing the next commands in the same window that ran the install will fail withgit : The term 'git' is not recognized.... - In the new window, first
cd $HOMEagain (a fresh window can land somewhere new too), then copy-paste this and press Enter.git clonecreates its owncloudlessfolder โ don't make one yourself first, or you'll end up nested inside an extra empty folder of the same name:cd $HOME git clone https://github.com/asifontheline/cloudless cd cloudless\cloudless go build -o cloudless.exe ./cmd/cloudless .\cloudless.exe up
Still not recognized after a fresh window? Search Git Bash in the Start menu (installed alongside Git) and run the same commands there instead โ it works regardless of PowerShell's PATH.
If cloudless.exe is
"blocked by your organization's Device Guard policy" โ that message shows even on personal,
non-work machines; it's Windows' Smart App Control feature blocking an unsigned binary (release
binaries aren't code-signed yet โ tracked in
#23).
Check Windows Security โ App & browser control โ Smart App Control: if it says
Evaluation, you can turn it off there (a restart is required for the change to actually take
effect, even though the toggle updates immediately). If it says On, Microsoft does not allow
turning it back off without reinstalling Windows โ in that case, run cloudless inside
WSL instead,
which isn't subject to this Windows-executable-specific policy at all:
wsl --install # after the restart it asks for, open the "Ubuntu" app, then inside it: sudo apt update && sudo apt install -y golang-go git git clone https://github.com/asifontheline/cloudless cd cloudless/cloudless go build -o cloudless ./cmd/cloudless ./cloudless up
- Open a terminal โ Ctrl+Alt+T on most desktops, or find Terminal in your applications.
- Install the tools (one-time, Go 1.22+):
sudo apt install golang-go git # Debian / Ubuntu sudo dnf install golang git # Fedora / RHEL
- Copy-paste this and press Enter.
git clonecreates its owncloudlessfolder โ don't make one yourself first, or you'll end up nested inside an extra empty folder of the same name:git clone https://github.com/asifontheline/cloudless cd cloudless/cloudless go build -o cloudless ./cmd/cloudless ./cloudless up
When it starts, it prints a link โ open it in your browser. That's your control panel: private to you, on your own machine.
Today this is a one-time copy-paste build (~2 minutes). One-click downloads with signed installers are in-build (#23) โ this step will become a single download.
Step 2 โ Choose how much to share. It starts at a safe 5% โ you won't notice it, your machine stays cool and responsive. Got an idle spare box? Slide it up in the panel, to a maximum of 70% (never 100%). Personal phone? Leave it low.
Step 3 โ Use it. That's it โ you're on the mesh. Chat with AI right in the panel, or point any standard chat app at the address shown there. If any node drops mid-request, another takes over automatically.
Optional โ open your node to the wider internet
You only need this if machines outside your home or office should reach your node directly. Skip it otherwise โ everything above works without it.
- Machine with a public address (e.g. a rented server): nothing to do โ it's already reachable.
- Home internet: in your router's settings, forward port
7946to your computer โ a one-time, ~3-minute setup. (Router pages usually live at192.168.0.1; to learn your public address, search "what is my IP".) - Mobile data or shared-building internet: those networks can't forward ports. The one-click overlay โ in-build (#20) โ will connect nodes across any network with no router setup at all.
Fine print: the share ceiling is 70%, never 100%, so your machine
always stays responsive. On phones a thermal & battery guard pauses sharing if the device warms up or runs
low (in-build
(#54)). Contribution is metered on the ledger and earns you service in return. Prefer the command line?
cloudless up -share-cpu 70% sets your share directly.
Sign in โ no passwords to remember
When you open your console the first time, you register in one tap using a passkey โ your device's fingerprint, face, or PIN. There's no password to invent, forget, or have stolen.
- Register: open
http://127.0.0.1:8080/โ Create account โ confirm with your fingerprint / face. Done. A secret key is created and stored safely on your device โ it never leaves it. - Sign in: next time, just touch the sensor. No typing.
- More devices: add your phone or laptop by scanning a code โ each gets its own passkey.
- Lose a device? Revoke it from any other device; a one-time recovery code (saved at signup) restores access if you lose them all.
Passkeys are the phishing-resistant standard (WebAuthn) built into every modern phone and browser โ the same thing banks use. Passwordless sign-in is in-build (#52).
Contribute, licensing & donations
Contribute โ in any language
The code, the board, and the roadmap are all public, and you don't need to know Go to contribute. Build in any language against the open API; Python is first-class. Full how-to in the contributor guide.
main by a queue every 2 hours โ parallel work
worldwide, and main never breaks.Contributor guide โ
Contribute in any language, and how the branch โ PR โ validate โ merge-queue flow works.
Open protocol โ
The language-agnostic API contract โ build clients, services, and backends in anything.
Source code โ
The full platform, Apache-2.0. Clone it, run up, join the mesh.
Open board โ
Every feature is a public issue with acceptance criteria โ our open Jira.
Donations & support
Cloudless is currently owned and maintained by asifontheline โ a labour of love, built in the open. Any help maintaining it would be greatly appreciated.
The most valuable help is participation: run a node, contribute in any language, review pull requests, or spread the word. If you'd like to support the project financially or partner with it, please get in touch via GitHub.
Copyright, licensing & reuse
ยฉ 2026 asifontheline. The Cloudless software is licensed Apache-2.0 โ free to use, run, modify, and self-host under that licence. Full terms in copyright & donations.
Duplicating or offering a Cloudless-based service. Individuals and companies are welcome to replicate, host, or build on Cloudless and reuse this site's content, provided that:
- you inform and partner with cldless.com before operating a public Cloudless-branded service, so efforts stay coordinated and the community isn't fragmented;
- you uphold the base principles without compromise โ open-source components only, privacy-first, cooperative and master-less by design, safe-by-default resource sharing, honest security, and the project's own vocabulary (no impersonation of other providers);
- you do not misrepresent affiliation โ the "Cloudless" / "CloudLess" name and the cldless.com identity belong to the project; don't imply official endorsement without a partnership.
These brand and coordination terms sit alongside โ and do not restrict โ the rights the Apache-2.0 licence grants over the code itself. All trademarks and product names referenced belong to their respective owners.