How it works

Everything happens over SSH. There is no dashboard to log into and no password to lose — your key is your account.

1. Get an address

The button on the front page gives you a one-line command. Run it, and the session allocates a /32 from our block, shows you the address and waits while you pay.

$ ssh 55vmkhueycvq@get.kikopod.com

Register a second SSH key while you are there. There is no account recovery, by design: an address that can be recovered by email is an address that can be taken by whoever holds the inbox. Two keys is the whole safety net.

2. Point a domain at it

One A record at your registrar, then tell us about it. We check the record actually resolves to your address before serving the name — that check is the proof of ownership, so there is no token to copy back.

# after the A record exists
$ ssh 185.104.32.x domain add www.example.com

HTTPS is issued on the first visit and renewed without you thinking about it.

3. Put something on it

Upload files, and we serve them:

$ rsync -a ./public/ 185.104.32.x:
$ git push 185.104.32.x:site HEAD:main
$ sftp 185.104.32.x

Every deploy is a versioned release swapped in atomically. If it goes wrong, rollback puts the previous one back in one command.

Or skip us entirely

The same address can point at hardware of your own instead. One command prints a WireGuard config; bring it up and the address is routed to that machine — every port, TCP and UDP, inbound and outbound.

$ ssh 185.104.32.x wireguard > kikopod.conf
$ wg-quick up ./kikopod.conf

The config routes only traffic whose source is your address, so the rest of that machine's networking is untouched. You get a public address, not a VPN that swallows everything — which also means anything listening on that machine becomes reachable, so set up its firewall before you bring the tunnel up.

The address follows the tunnel. Bring it up and the address is yours within a second. Take it down and we serve your files again a few minutes later. Do that as often as you like — there is nothing to tell us either way, and a config you have never brought up leaves your address exactly where it is.

Reverse DNS

Your address answers to a name you choose, forward-confirmed. Mail servers and sysadmins notice.

$ ssh 185.104.32.x ptr mail.example.com

Tell us something

There is no support inbox and no ticket form. There is a command, over the same connection you already have:

$ ssh 185.104.32.x say "IPv6 would be useful"
Sent. It is message #41 and it reached a person, not a queue.

It arrives already attached to your account and your address, because the key that sent it says who you are — so there is nothing to prove and no ticket number to quote back at us. Your agent can send one too, with its own key.

Everything else

The reference has the rest: releases and rollback, key management, the WireGuard state machine in detail, the limits, and what we deliberately do not do. Or type help over the same connection, and help wireguard for all of one command.