Use case
Developers
Sometimes the shortener is a component rather than a product: links created by a job, read by a dashboard, or driven by an assistant, with nobody opening the screens at all.
What goes wrong
Most shorteners treat the API as a tier rather than as the product, so the interesting operations are dashboard-only or metered separately, and self-hosting is not offered at any price.
How it is done here
- 01
Call the REST API
Create, update, tag and read links, and read the analytics. It reaches every action the screens do, because both call the same code underneath.
- 02
Or hand it to an agent
An MCP server ships with it, so an assistant can create a link, tag it and read its analytics with no scraping layer in between.
- 03
Run it yourself if it matters
It is open source and runs on PostgreSQL or MySQL. Self-hosting is the only way to guarantee the click record never reaches anyone else's infrastructure.
What carries it
- REST API covering every action
- MCP server for AI agents
- API tokens
- Self-hostable, open source
Where this stops
Self-hosting is infrastructure you operate: upgrades, backups, and somebody who can read logs when redirects stop. It is a good trade for some teams and a slow distraction for others.
Try it on your own links
Five links free, every analytics field, no card.
Start for free