kikopod

Your own public IPv4. Everything over SSH.

One address, yours alone. Put a site on it, give it your name, or route it home — all from one connection. No dashboard, no password, nothing to log into. Which is exactly why an agent can run it as well as you can.

$ ssh ••••••••••••@get.kikopod.com

It is yours for ten minutes.

€15 a month · what that includes

This is the whole of it

Real sessions, not screenshots of a control panel. Count the lines.

$ ssh ••••••••••••@get.kikopod.com
k i k o p o d · dedicated-IP static hosting
You’re connected. Here’s your dedicated IP:
185.104.32.x
registration key: ••••-••••-••••-••••
contact email (enter to skip):
All set. Your dedicated IP is 185.104.32.x.
Deploy with: sftp 185.104.32.x (or rsync, or git push)

That is the whole purchase. No account to create, no form, no dashboard to be shown around. The address is allocated and already answering before you pay for it, and the key you connected with is the account from then on.

And the parts you stop thinking about

Nothing to log into
Your key is the account. No password to lose, leak or reset, and no recovery email for someone else to take.
Built for a shell, so built for an agent
Every command is ssh <ip> <verb>, and help lists them all. If it can run ssh it can run the pod — a person, a script, or an agent with a key of its own. The machine-readable version is at /llms.txt, and say reaches us over the same connection — no inbox, no ticket form, for you or for it.

And a good deal more. help lists it, and the list keeps growing.

No two pods look alike

Every pod draws its own mark, tinted from the address it lives on. Yours turns up on your holding page, your 404, and anywhere else it belongs.

  • 185.104.32.7
  • 185.104.32.41
  • 185.104.33.9
  • 185.104.33.118
  • 185.104.34.66
  • 185.104.34.203