Analytics and short links that live in your Cloudflare account
clx installs a small worker and a D1 database in your Cloudflare account. Your sites count their visits there, your short links redirect from there, and clx.cx keeps only the totals.
Free plan, no card. Open source under AGPL-3.0.
Example data, drawn by the same charts as the report in the app.
How it works
Connect Cloudflare
Paste a one-time bootstrap token. clx issues its own working token from it, then deletes the bootstrap token — or tells you to, if Cloudflare would not let it.
clx installs its worker
A worker and a D1 database appear in your account and run on your quotas — the free ones are enough for most sites.
Add a site or a link
Put a one-line snippet on your site, or make a short link on your own domain with a QR code and rules.
Two tools, one worker
Visit counter
Views and visitors of every site: by hour today, by day for 7 and 30 days; daily totals are kept for 400 days.
- No cookies, no third-party address in your pages
- Pages, sources, countries, devices, browsers, systems
- Bots counted apart: search engines, AI crawlers, monitoring
Short links
Links on a domain of yours, served by the worker in your account.
- A QR code for every link, as SVG
- Rules by country and device
- Clicks by source, country and device
Why clx
Your data stays with you
Visits, clicks and their breakdowns live in a D1 database in your Cloudflare account. clx.cx stores only totals by hour and by day.
No shared footprint across your sites
Every site gets its own path, script and collector names and snippet code, generated from a random seed. The counter loads from your own domain and reports to it, with no cookie and no third-party host: nothing in the pages ties your sites to each other or to clx.
Cloudflare’s free plan is often enough
Workers Free allows 100,000 requests and 100,000 D1 writes a day per account, shared with your other workers: for a typical account about 11,000 counted events a day at worst, usually several times that. clx warns you when the account nears its quota.
Open source
The worker, clx.cx and these pages are open under AGPL-3.0: read what runs in your account.
Where your data lives →No shared footprint, in detail →Open source →clx and 301.st →
Made for site generators and agents
Everything the app does is an API call. A site generator adds a site and puts the snippet into the page it builds; an AI agent sets clx up for a person from one page of docs.
curl https://clx.cx/v1/sites \
-H "Authorization: Bearer clx_…" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"account_id":"…","host":"example.com"}'
# → 202 { "site": { "snippet": { "inline": "<script>…", "script_tag": "…" }, … } }Plans
Free
$0
- 1 Cloudflare account
- 10 sites, 200 links
- 1 API key
API
On request, free for now
- 50 Cloudflare accounts
- 500 sites, 10,000 links
- 5 API keys
Cloudflare’s Workers Paid plan is never required on any plan. Plans in detail →
Questions
Do I need a Cloudflare account?
Yes. clx counts sites served by Cloudflare, and short links need a domain of yours there: clx.cx carries none of your traffic.
What does clx create in my account?
One worker, one D1 database, the routes of your sites and the custom domains of your link hosts, with a working token of its own. Disconnecting removes what clx created and lists anything it could not; the working token you revoke yourself in Cloudflare — clx gives you the link.
Does it cost anything?
The free plan costs nothing and needs no card; the worker runs on your Cloudflare quotas.
Can I read the code?
All of it, on GitHub, under AGPL-3.0.
Count visits and shorten links — the details stay in your account
Free plan, no card. Open source under AGPL-3.0.