Your static site,
your own IP address.

Most static hosts share one IP across thousands of sites. kikopod gives every site its own dedicated IPv4 — no shared anycast, no shared reputation, no caught-in-the-crossfire blocklists.

Request early access

Why a dedicated IP matters

When thousands of sites share one IP and just one of them earns a takedown, a blocklisting, or an angry corporate firewall rule, everyone on that IP wears the consequences.

kikopod is the opposite of that. We hold a clean /22 of IPv4 space and assign every site its own /32 from it. Yours alone, from day one, for as long as the site lives.

• Allowlistable. A reader on a locked-down corporate network can punch one IP through their firewall and reach you.
• Reputation-isolated. The IP starts with a clean slate. Nobody else's history, nobody else's problems.
• Reachable. Networks that block Cloudflare or generic CDN ranges still reach you — because you're not on them.
• Brandable. Your IP's reverse DNS points at your domain. (Coming soon.)

How it works

1. Sign up. You receive a dedicated /32 from the kikopod pool.
2. Point your domain at it — one A record at your registrar, done.
3. Deploy via sftp, rsync, or git push, with atomic versioned releases and one-command rollback.
4. Serve over HTTPS automatically — fresh Let's Encrypt certificate, your dedicated IP.

Honest status

kikopod is in soft launch. The platform works end-to-end — this page is served by it — but we're staging access slowly to keep the IP block's reputation pristine.