Some of this is going to sound strange, and it isn't for everybody. If you've never once felt uneasy that the tools you depend on aren't really yours - that you're renting your future from people who can change the terms or pull the rug whenever it suits them - you can stop right here, no hard feelings, have a good one. The rest of this is for the people who felt that in their chest just now. You know who you are.
Short version: a few weeks ago I walked into a hackathon not knowing what a VPS was. I walked out having built my own. And the part worth your time isn't the box - it's what I could see because I didn't come up through code.
Wait - what's a VPS? What's a box?fair question
Fair question, I had it too about a month ago. You know how everything you build ends up trapped inside some app or login somebody else controls and can change or lock whenever it suits them? A box is the way out of that: a small computer you rent for a few dollars a month, always on, out on the internet, and yours, with you holding the only key. Your work lives there instead of in someone else's account. The proper name is a VPS, "virtual private server," which is exactly why nobody remembers it. So we just call it a box.
I came up through a completely different door.
The Army taught me two things, thirty years ago, long before any of this. First, security: I ran arms rooms and handled hazmat, where you assume - always - that someone is going to try you, and you learn in your bones that a boundary is only real when it's built right. A locked cage. A key that opens exactly one thing and nothing else. Then they reclassified me to signal - 31S - and I learned how communication actually moves: modems, links, the plumbing of getting a message from here to there intact. Security and signal. Hold onto both of those.
So here's the thing sitting in plain sight that I actually want to hand you. My box is small - about six gigs of memory, no graphics card, twelve dollars a month. By any serious standard that is nowhere near enough to run an AI, and everybody in that room knew it. That's exactly why it works.
I didn't put a brain in the box. I made the box a switchboard - a pure router - and I left the brains outside it: borrowed, swappable, connected on demand, including the very AI subscription you already pay for. The box doesn't think. It routes. It coordinates. It remembers. And it's mine.
Rent the AI. Own the wiring. There’s no locking you out of what you already hold.
That's the whole trick, and it's the part nobody's saying out loud. It was never about owning the biggest engine - it's about owning the wiring, which, it turns out, is the thing they trained me to do thirty years ago; a switchboard is just signal work with newer gear. Let the horsepower live anywhere, on anyone's hardware - you rent it, you swap it, and no one can hold it over you. Cheap on purpose. Small on purpose. Yours to keep, on purpose.
And it's a gift. The whole build is published - Apache-licensed, free to take and fork - my name on it not to fence it off but so the thread back to where it came from never gets cut. A link is a lineage. That's the one line I'll defend to the wall.
None of this happens without Victor Vorski. He built The Gathering in the forests of Portugal - hundreds of people, dozens of organizations, a genuinely new kind of room - and this year he's carrying it to the redwoods. He opened the door and said come see, and he's here at the US Gathering with his own Camp Audax. Go find what he's bringing. I forked my own direction from his invitation - not away from him, toward what I needed - and the first thing I want to do now that mine works is wire it back to his and help. You build your own ground so you finally have something worth carrying back to the table.
That's the shape of it. If you're one of the people this is for, the rest is below, and all of it is yours.
Part two — the wires
Here's what one small box actually holds.
Not a platform you join. Not a login someone can revoke. A plain server you control, where everything runs on it, for you. Four things, wired from commodity parts:
A real front door that lets Claude Code — the app, the one with hands on the system — reach your box as a scoped guest, on the subscription you already pay for. No middleman, no identity company, nobody between you and your own tools. The model stays rented and outside; your files stay in the box.
The same box serves your site. One bill, one owner, no monthly hostage situation. (This page runs on exactly that.)
The parts you're protecting are structurally unreachable; you open only the part you want people in. A guest reaches exactly what you offer and nothing more — no rifling through the bathroom cabinets. Security built into the walls, not watched at the door.
You don't call the techy kid to run the wires. Claude Code runs them — the app that can actually operate the box, not the chat window. You bring what you already know from your own life; the box does the rest.
Cost
~$12/mo, headroom included. Put a second group on the same box, sealed from the first, and it's six each.
Iron
~6 vCPU, 11 GB RAM, no GPU — and that's the point, not a compromise. A router, not a brain.
License
Apache-2.0. Free for anyone on Earth to run and fork — attribution intact.
The point
Coordination you own, for people who were told they couldn't afford a seat at the table.
Two groups, one box, each walled off from the other — the same wall that seals my seats apart seals a whole other community's work from mine. That's the version that matters: a group gets its own private nervous system for a few dollars a month, not a rented login on somebody else's platform.
Three ways in — pick your altitude
Take it at the level that fits you.
Here's the repo. Fork it, stand up your own, done. github.com/Techniq42/fls-membrane →
The repo plus Claude Code — the app, running on the subscription you already pay for is the whole kit. You don't run the wires; Claude Code runs them. That's the part nobody told you was possible.
Never used GitHub? Good. Start here.the on-ramp
You keep hearing the words - "your own box," "sovereign," "the membrane" - and they sound like they belong to somebody else. They don't. A box is just the rented little computer described up top, and here is how you get one of your own without knowing how to code.
You don't run the wires. The AI runs the wires.
Here's the part nobody says out loud: you are not going to type scary commands into a black screen and understand them. You're going to copy a few things, paste them to an AI, and it does the technical part while you watch and learn. The skill you need isn't coding. It's being willing to follow along and not panic when something looks weird. You've got that already.
What you'll need: three cheap accounts
A box to rent (a "VPS"). A company rents you the little always-on computer - roughly $6-12 a month. VPS just means "the rented box." Your AI can even help you pick one and sign up.
An AI that can do the work. A Claude subscription - the same one a lot of people already pay for. This is the thing that runs the wires for you, step by step.
Five minutes of safety first. Before you hand the box to the AI, do the short safe-setup: the hosting account, the master password, one key for the AI. Plain words, no terminal fear: the safe start →
A free GitHub account. GitHub is just where people keep recipes for software. Free, about ninety seconds to make. You'll barely touch it - your AI does.
The recipe: the "repo" (that's the word)
Each recipe on GitHub is called a repo. Ours is free, open, and yours to copy - it's called fls-membrane. You do not have to read it or understand it. It's there so your AI can read it for you. When you're ready, it lives here: github.com/Techniq42/fls-membrane - and the plain-language instructions are in the file called the README right on that page.
How it actually goes: point, paste, watch
Once you've got the three accounts and your box, here's the whole dance. Open your AI, and paste it this - word for word - filling in the one blank:
Copy this to your AI
That's the magic wand. The AI reads the recipe, hands you each step, and you paste what it gives you into your box. Something breaks? Tell it what you saw; it fixes it. That's not failure - that's just how everyone does it, including the people who look like they know what they're doing.
When your box is up, you connect it to the rest of us. Tell your AI: "now help me sync my box with the shared coordination so it can pass notes with the others." That's the whole point - your box and everyone else's can talk, pass notes back and forth, without merging into one thing and without you giving anything up. Yours stays yours. Theirs stays theirs. They still talk.
When you get stuck: you won't be alone
Everybody gets stuck. That's Tuesday, not failure. Ask your AI first - it clears most walls by itself. Past that, there's a whole fire of people doing exactly this, and we gather in person this October in the redwoods at Camp Synthesis. Come get unstuck with your hands on it.
Bring it to the fire. Come build your own with us, in person, at Camp Synthesis, our camp inside The Gathering US at Camp Navarro in Mendocino County, California — October 15–18, 2026, around an actual fire, where we talk the whole thing all the way through. Space is limited — room for only a handful more camps.
Field notes
Get the field notes when they land.
The whole build is in the repo and it’s yours right now, no email required. This is just the occasional note as it grows, and word when there’s a seat at the fire. Nothing else.
Stand up your own. Carry the attribution. Pass the ground forward.
This little box is one node in a bigger web. See what owning your own wires makes possible for a whole community, or wander the rest of the constellation →