Your own VPN. On a server that is yours, not a company's.
A free skill for your AI coding agent turns a small server you rent into a VPN only your people use — your own address, not one shared with thousands of strangers.
Your clicks + ~10 min of install · new domain: 15 min to a few hours · account review, if any: a few hours
Not included: the server and the domain, billed by your providers.
- You
- a hosting account and card, a domain, invite Homeport to it, scan the QR on each device, remove the invite at the end
- Refund
- automatic if the check fails; otherwise on request within 14 days
- Covers
- the setup, not your network
- At launch
- DigitalOcean only
Host: $6/month before tax (DigitalOcean, 27 Sep 2026). Domain: from about $10/year; renewals can cost more. Runs in an AI coding agent on your computer. Tested with Claude Code; Codex CLI, Gemini CLI and Cursor read the same skill format but haven't been tested yet. No coding agent? The other path is for you. No Homeport account.
- You
- a hosting account and card, an access key (revoked later), a domain you buy and point, the WireGuard app per device
In Claude Code's prompt, not a terminal, one at a time:
/plugin marketplace add antongavrilov88/homeport-skill/plugin install homeport@homeportThen say “set up my own VPN”, or type /homeport:homeport.
From a terminal, updating, or git clone
From a terminal, the same two steps:
claude plugin marketplace add antongavrilov88/homeport-skillclaude plugin install homeport@homeportTo update, run both lines, then restart Claude Code. The first line alone only refreshes the catalog.
claude plugin marketplace update homeportclaude plugin update homeport@homeportOr copy the skill instead of the plugin, in a terminal. Start it with /homeport; update with git -C ~/.claude/skills/homeport pull.
git clone https://github.com/antongavrilov88/homeport-skill ~/.claude/skills/homeportCodex CLI, Gemini CLI and Cursor read the same open Agent Skills format, but are untested with Homeport so far. In a terminal, clone the skill into your agent's skills folder:
git clone https://github.com/antongavrilov88/homeport-skill <your agent's skills folder>/homeportFor Codex CLI that folder is ~/.agents/skills/homeport.
If you try one, open an issue and say how it went.
A coding agent runs on a computer.
A hosting account with your card, an access key for your agent, and a domain (usually from about $10 a year; renewals can cost more) that you point where your agent says. Your agent tells you what to click, one step at a time, and why.
- Account
- The server is yours: Homeport can't switch it off or look inside it, and if Homeport vanished tomorrow it would keep running.
- Card
- Your card goes to your host, which bills you at its listed price: no middleman, no markup, and Homeport never holds your card.
- Access key
- It lets your agent rent one server for you; revoked at the end, nothing from this chat can touch your account later.
- Domain
- Registered to you, so only you can renew or move it. Keep it apart from anything personal: it's the disguise.
- In your name
- Hosts check the card and sometimes an ID. Homeport never suggests an account in someone else's name.
You revoke the key together at the end. On DigitalOcean, your agent creates the server; on another host, you create it. Every step you do by hand
The REALITY keys are made on your machine and the WireGuard keys on your server; they never pass through Homeport. The installer, real certificates and watchdog are handled for you, and the DNS records too once your domain points at DigitalOcean. The server installs itself; your agent finishes the checks when you're back.
Install the official WireGuard app and scan the first QR, which your agent sends you with a short handout to pass on. Later devices come from your panel. Family devices work the same way — they scan, you don't have to be in the room.
- Each device
- Its own key, made on your server. Lose a phone? Delete that one device in the panel; the others keep working.
Nothing is marked done on trust. The check script tests every service, the certificate on your domain and the panel. On the two-server layout it also sends traffic through the tunnel. Then your first device opens a page while Homeport watches its handshake on the server.
What actually gets installed
- Cover
- Xray serving VLESS + XHTTP + REALITY on 443/tcp, behind a real site on your own domain with a real certificate. A prober that knocks gets the site — because it is the site. It protects the two-server link and phones using a VLESS app. On one server, WireGuard devices connect as plain WireGuard.
- Devices
- Plain WireGuard, official apps. Nothing custom to install on a phone or a laptop.
- Panel
- A small web panel on the server: add a device, get a QR, see bytes and last-seen. The panel and push alerts are in English; everything your agent says to you, and the handout you pass on, are in your language.
- Watchdog
- A service that checks the tunnel every 30 seconds, restarts what it can and alerts your phone. On two servers it also moves everyone to a spare route.
- Split routing
- Two-server layout only: an nftables set decides who goes through the tunnel, and a domain list you edit leaves directly from the relay. Seeded with the payment networks that usually object — add your own bank.
- Layouts
- One server abroad by default, or a two-machine relay when devices sit behind heavy filtering. Same installers either way.
The full design — including the one signal it deliberately does not win
Rather not do these steps yourself? From January 2027, Homeport's agent does the rest once you've done your part: the account and the card, a domain you buy and point at DigitalOcean, and one invite.
Every VPN you've been sold is someone else's server. This one is yours.
Most commercial VPNs put many customers on one address, so you inherit their reputation: banks, shops and streaming services flag the address as "VPN" and you get captchas, refused logins and toggling the app on and off. That's the shape of the business. Your own server gets rid of the strangers, but it still sits in a data centre, and some services flag that too.
A server of your own is one IP, used by the people you know. No VPN company sits in the middle, and Homeport logs nothing about what you open. It costs what one small server costs, shared by everyone you add, not a fee per person.
One honest limit: some carrier and corporate networks restrict VPN traffic altogether, and no setup on your side changes that. Homeport tells you when the network, not the setup, is the problem.
Same VPN either way. The difference is whose problem it is when something goes wrong.
Rather not do it yourself? That is what the $29 buys: you do four things only you can do, and from there it stops being yours to worry about. Homeport builds the server, installs everything, tests it end to end and hands you a QR code. If something breaks later, you message me instead of reading a forum.
- What Homeport does
- Creates the server on DigitalOcean, generates the keys, installs, gets certificates, sets the DNS records if your domain points at DigitalOcean, checks it all, sends your first QR and a handout to pass on. For your part, it tells you what to click and why.
- Time
- Your clicks, then about 10 minutes while it installs. A new domain takes 15 minutes to a few hours to go live, and a new hosting account is sometimes reviewed for a few hours.
- Guarantee
- No guarantee, because there is no invoice. Same scripts, same checks — the only thing you do not get is someone to blame. If you get stuck, you can hand it over.
- What Homeport does
- Server, DNS records, keys, install, certificates, monitoring, panel, checks, your first device and QR, plain-English notes to pass on. Then it walks you through removing the invite yourself.
- Time
- Your part: the account and the card, a domain you buy (usually from about $10 a year; renewals can cost more) and point at DigitalOcean, one invite, a QR per device, then removing the invite. The rest happens without you. The same waits for a new domain and a new hosting account apply.
- Guarantee
- It is not finished until it has been tested working.
Prices, what's included and the buttons: see the two cards at the top
Illustration — the agent opens in January 2027
Verification runs on the server and from outside it: services up, the config valid, a real certificate on your domain, the panel, and on the two-server layout traffic through the tunnel — this is the script, and you can re-run it yourself any time.
Setting it up for someone else? Same flow — you pay, they get the QR.
Card declined?
It happens — some hosts reject prepaid or debit cards, or a card from a bank they don't know. You can still rent a server. Three ways round it, in the order I'd try them.
A friend or relative whose card the provider accepts rents the server. The host bills them monthly. They can keep paying it, or you pay them back.
The guide keeps a dated list of hosts that take PayPal, crypto or local methods. None are tested with Homeport yet, so check before you pay.
They work — and they're last on this list for a reason.
Fees, identity checks, and they come and go. I don't partner with any of them or take a cut — check one yourself before trusting it with a card.
One developer, building in public.
I'm Anton Gavrilov, a developer. I build Homeport in public — the skill, the guide and the agent — and write about what works and what doesn't along the way.
The skill is free and stays free; the paid part is only for people who'd rather be walked through it — I don't run servers for anyone, don't hold cards, and don't want your keys.