About spoo

A link platform, built in the open.

spoo.me is open-source link infrastructure. Every component, every endpoint, every native client is free to read, run, and self-host. This is what we're building, and why.

What spoo is.

spoo.me is a complete link management stack: a high-throughput redirect service, a dashboard for managing campaigns, a public API for automation, and an ecosystem of native clients across browser, desktop, mobile shortcuts, Discord, and Telegram. All of it open source.

The platform has served over 100 million clicks across every region, and is used by independent developers, indie teams, and organizations that need link infrastructure without the lock-in of a SaaS vendor.

Why it exists.

Link shorteners follow a predictable pattern: your redirects live on someone else's infrastructure, on someone else's terms, with a quiet erosion of ownership over your own redirect data. spoo was built to flip that pattern.

The entire stack (analytics, custom domains, API access, every native client) is open source and self-hostable, so the option to leave is always one command away. Link infrastructure should behave like a public utility: transparent, portable, and never holding your data hostage.

What spoo stands for.

The principles that shape every release of the platform.

Open by default

Every component of the platform is open source: the link service and dashboard under AGPL-3.0, the SDKs and native apps under permissive licenses. Read the source, fork it, run it.

Generous by default

No ads, no selling click data, no dark patterns. The platform is funded by the people it serves, not by your data.

API-first

Every dashboard surface is backed by a documented public API. Six SDKs ship alongside the core platform. spoo is a building block, not a destination.

Yours to host

The entire stack runs on your own infrastructure with one command. Full feature parity, your domain, your database, no telemetry.

Built by one person.

Zingzy
Zingzy
Founder & maintainer

spoo is not a company with departments. Every service in the ecosystem (the redirect core, the dashboard, the SDKs, the native apps, and this site) is designed, built, and operated by one developer.

It is not built alone, though. 12 contributors have landed fixes and features across the open-source repos, and the community on Discord shapes what ships next.