Cloudflare connected via API
Add the API token of your free Cloudflare account — the platform creates the zone, DNS records and HTTPS for every domain of yours.
Self-hosted URL shortener with an Anti-Bot filter. Smart traffic redirection and landing page protection on your own VPS — no monthly subscription.
The flow
Six links in the chain — from your own domain and server to ready analytics
Add the API token of your free Cloudflare account — the platform creates the zone, DNS records and HTTPS for every domain of yours.
Your own clean VPS (we recommend Contabo) runs an isolated Docker agent that handles the clicks. Your server, your IP.
Add your domains (three or more works best). The platform checks their reputation and rotates them for you during bulk link generation.
Every link is personal and lives for exactly three clicks by real people. Bots are sent to a neutral page by the built-in Anti-Bot filter.
One target URL, and the system returns an array of personal links: up to 25,000 at a time, spread evenly across your domains, with CSV export.
A three-stage funnel: the email open, the click by a live person and the conversion — with affiliate revenue next to it via S2S postback.
There is no need to configure each domain by hand. Generate a token in your Cloudflare profile once and add it in the cabinet: from there the system creates the zone, points a proxied A record at your server IP and turns TLS on.
Zones are created in YOUR Cloudflare account, not ours — so your infrastructure never depends on other users of the platform. The token needs three permissions: Zone · Edit, DNS · Edit and Zone Settings · Edit.
The agent is a small container: it takes the click, checks the visitor and sends them where intended, while the decision itself comes from the platform. Your infrastructure stays entirely separate from other users — your server, your IP address, your domains.
Today the agent is installed following our instruction (PDF, three languages) — a few commands you can paste even into your host's web console, with no SSH client. One-line automatic installation is in the works and will appear in the cabinet.
Every domain is checked against security registries — 8 DNSBL lists, Google Safe Browsing, VirusTotal and AbuseIPDB — and is then re-checked automatically every 6 hours. Ownership is confirmed with a DNS record.
Once confirmed, domains join the rotation: links from one batch are spread evenly across your domains, so neither the load nor the filters' attention piles up on a single name. If a domain ever gets blacklisted, the system removes its shield and takes it out of rotation on its own.
A link is created for one specific recipient. Scanners of mail services and messengers may hit it as often as they like — they get a neutral safe page, and those hits do not consume the clicks.
The link accepts three live clicks and then closes itself. The filter works on request signals — User-Agent and language headers — which cuts mass scanners well, but is not absolute protection.
A large mailing needs a separate address for every recipient. Put your target URL in the Links section — it is screened against threat databases (Google Safe Browsing, VirusTotal, PhishTank) right away, and only a clean result lets you set the amount. From there the platform generates the batch in seconds, distributing it across all your connected domains.
Up to 25,000 links are created per run; larger volumes go in several batches. The finished list is exported as a single-column CSV so you can load it straight into your mailing software.
The funnel shows three consecutive stages: the email open (via pixel), the click by a live person and the conversion from your affiliate network — all for the same period, so they can be compared with each other.
Separately you see countries on the map, browsers and device types, as well as humans versus bots. The network postback arrives on your own domain and ties the payout to a specific link — so revenue sits next to traffic in your stats.
Use cases
The three jobs the platform fits best
Every recipient gets their own link, so the stats show who opened the email and who clicked. A batch of up to 25,000 links is spread across your domains, so neither the load nor the mail filters' attention piles up on a single name.
The finished list exports to CSV — straight into your mailing software.
The same works for Telegram and WhatsApp when you message each person individually — not a group or a channel: every recipient gets a separate link. Messenger scanners get a safe page, and those hits do not consume the clicks.
Personal messages only — not for groups or channels: a link lives for three clicks.
A short link on your own domain does not eat into the SMS length, and every recipient gets their own — so you can see exactly who clicked. Automated link checks get a safe page and do not consume the clicks.
SMS opens are not tracked — the stats show clicks. The list exports to CSV for your SMS service.
Under the hood
Everything you need for professional link management
Clicks are served by your own server, never a shared one: your VPS, your IP address, your Cloudflare account. Your traffic never mixes with anyone else's, so the reputation of your domain and server depends on you alone.
Every click is broken down by country, device, browser and traffic source. See where and when your target audience arrives, instantly.
End-to-end wiring with affiliate and CPA networks: the network reports the payout to your own domain, and the platform ties it to the exact link. Revenue sits next to traffic, so ROI is counted without exporting anything into spreadsheets.
Every domain is checked automatically against dozens of phishing databases (Google Safe Browsing, VirusTotal, DNSBL). Compromised addresses are detected by the system on their own.
Your server stays safely hidden behind Cloudflare. The real IP address is never exposed, and traffic goes through protected proxies with free SSL encryption on every domain.
A built-in system for safe traffic routing. Automated bots, parsers and monitoring systems are quietly sent to a fallback page, while real users get instant access to your content.
Every destination URL is screened against threat databases — Google Safe Browsing, VirusTotal and PhishTank — when the link is created and weekly after that. The reason is simple: your links run on YOUR domain, so phishing or malware on the offer side hits your reputation and your email deliverability first. A destination flagged as dangerous gets no links.
Traffic protection
The decision is made BEFORE the visit is forwarded, on your own server. A live person reaches the destination page; automation gets a neutral one. No captcha and no required JavaScript.
An empty or truncated User-Agent, a missing browser language, known robots by list. And the "browser that is not a browser": a request claiming a modern Chrome while carrying none of the headers a real Chrome always sends. The cheapest line runs first, because a live person is waiting for the redirect.
Search crawlers and SEO scanners identify themselves through the network's reverse name — and that name is verified the other way round, through the forward record. A forged "Googlebot" does not pass: anyone can publish a name, only its real owner can confirm it.
A browser coming from a datacenter is not a person. We check the network against an autonomous-system database: hosting, clouds and server proxies never receive the destination page, however flawless the browser looks. The database lives on the platform and is updated there, so your server needs no reconfiguration.
A blocked bot does not spend a personal link's limit — all three opens stay for live people.
Every block appears in your stats, in the "Humans vs bots" block: the protection proves itself with a number, not a promise.
The visitor does not have to do anything: no captchas, no "I am not a robot" challenges — the filter decides on its own, before the visit is forwarded.
Dashboard
The four screens you will use every day: your dashboard with the balance, domain settings, creating links and reading the stats. Click a screenshot to open it in full.
Open full size
Open full size
Open full size
Open full size
Screenshots are from a demo account; names, domains and URLs in them are illustrative.
Before you pay
Three things you provide on your side. Without them the platform will not run — make sure you can do them before you pay.
A clean Ubuntu 22.04 or 24.04, 1–2 vCPU and 2 GB of memory. The agent installs with a single command — we never ask for your server password. Your server handles the redirects, not ours.
Links point at your domain, not ours — which is why the traffic reputation is yours. For large volumes we suggest three domains or more, so the load is not concentrated on one name.
The free plan is enough. You provide an API token with three permissions, and the platform sets up the zone, DNS and TLS itself — inside your own account.
Lifetime packages
Pay for volume — a prepaid package of links, no subscription. Links beyond the package come from your balance at your package rate.
Test the software on a small base
Choose planSteady volume — mailings of 3,000+ links
Choose planLarge volumes every day
Choose planHundreds of thousands of redirects
Choose planEvery link is personal: one recipient, up to 3 clicks — after that it closes itself. Links never expire: you buy volume, not a month.
No hidden fees. Prices in euro, paid in crypto. Neither links nor money on your account ever expire — nothing is lost. Beyond the package, links come from your balance at your package rate. No subscriptions, no auto-charges: campaigns come in waves, and during a pause you pay nothing — the remainder simply waits for your next launch.
Architecture
Most trackers and shorteners run on shared servers: dozens of clients share the same IPs and domains. The moment one of them runs aggressive campaigns, mail filters block the whole pool — and your deliverability along with it. That is what people call a neighbour ban. We do not have one for a simple reason: there is no shared pool.
Clicks are served by the agent on your VPS, not by our servers. There are no co-tenants, so somebody else's campaign cannot touch your domains.
Your domains sit behind Cloudflare in your own account: from the outside only the proxies are visible. You own the zone — and can disconnect a domain yourself at any time.
A personal code accepts three clicks from live people and serves scanners a safe page. That keeps the domain usable for delivery longer.
The agent on your VPS keeps no database: codes, stats and revenue are counted by the platform, which also drives the shield. On your side are the traffic, the domains and the reputation — exactly what needs to be isolated.
Get started
Signing up takes a minute, but the account does nothing on its own: the platform runs only on your infrastructure — your VPS, your domain, your Cloudflare. Connect them and pay only for the links you create.
Create your first linkNo card · Your own VPS and domain required
We use strictly necessary cookies only — they keep you signed in and protect our forms. No analytics, no third-party trackers.
Questions about setup and how the service works
Answered by AI from the site materials — it can be wrong. Check anything important with support.