For people who ship
Links, pages and events
on your own domain
One account for the link in your bio, the page it points to and the event behind it. Deep links that open real apps, analytics that survive the click.
Free forever planNo cardNo ads on your links
12,480
clicks+18%
64%
app opens+6%
38
countries+4
42 ms
p50 redirectedge
- h1x.si/l/launchyoutube.com/watch?v=9bZk1,284
- h1x.si/l/deckfigma.com/file/h1x-pitch812
- h1x.si/l/rsvph1x.si/e/aurora-2026406
- < 50 ms
- average redirect
- 99.9%
- edge uptime target
- 330+
- cities behind it
- 0
- ads on your links
How it works
Three steps, one dashboard
The work happens before the redirect, so a click never waits on a database.
Detected app: YouTube · deep link ready
Features
Built for the click, not the form
Every rule, gate and counter is evaluated in the same lookup that resolves the link.
One hop to the destination
The edge caches the resolution, so a click never waits on the database. 302 with no-store, never a cached 301.
Rules run before the redirect
Country, device, OS, language, time window and A/B splits are decided in the same lookup as the link.
Answered from the edge
The worker runs next to the visitor, not in one far away region. The first byte arrives before a page would have loaded.
Events without a second tool
RSVP, capacity, check-in and certificates live on the same page as your links, with the same analytics trail.
Use cases
For the work you already publish
Links, pages and events share one account, so the pieces stop drifting apart.
Creators
One bio link that opens the app instead of a browser inside it.
Agencies
A page per client on their domain, with one bill and one login.
Conferences
RSVP, capacity, check-in and certificates without a second tool.
Educators
Course links, reading lists and a page that holds both.
Developers
Rules, webhooks and a REST API that returns plain JSON.
Communities
Invite links, event pages and click counts in one place.
Benefits
Fewer tools, fewer surprises
Most setups break at the seams: a shortener here, a page builder there, a ticketing tool somewhere else. h1x keeps them on one domain and one bill.
account for links, pages and events
One login, one workspace, one analytics trail. No second invoice at the end of the month.
ads or redirects we did not ask for
Your link goes to your destination. We do not insert an interstitial, a pixel or a sponsor.
always temporary, always measured
Rules, passwords and expiry stay live because nothing is cached as permanent.
What one account includes
- Short links with app deep links and click analytics
- A published page on your handle or your own domain
- Event pages with RSVP, capacity and check-in
- One analytics trail across all three
3
products, one login
1
domain to point
302
never a cached 301
0
ads on your links
For developers
A redirect you can reason about
Links resolve at the edge in a single lookup. Rules, passwords and expiry are evaluated before the redirect, and analytics are fire and forget so they never block a click.
- 302 with no-store, never a cached 301
- Rules for country, device, OS, language and time
- Signed unlock tokens for protected links
- REST API and webhooks on the Business plan
// edge worker, one lookup, no database on the hot path
const binding = await kv.get(routeKey(host, path), "json");
if (binding.link.requiresPassword && !unlocked) {
return unlockPage(binding.link);
}
const target = decide(binding.link.rules, {
country: request.cf.country,
device: "mobile",
hourUtc: new Date().getUTCHours(),
});
return redirect(target, 302, { "cache-control": "no-store" });The link, the page it points to and the event behind it are one property. Moving a link to a page, or a page to a domain, does not break the addresses you already shared.
Yes. Point a CNAME at customers.h1x.si and the domain wizard walks through the record, the check and the SSL state. The old h1x address keeps redirecting while you move.
No. There is no interstitial, no sponsor slot and no pixel we did not tell you about. Click data stays in your workspace and is never resold.
Links above the free limit stop resolving after the grace period, and the addresses stay reserved. Export the click history before you downgrade if you need it.
Every analytics view exports as CSV on Pro and above. The API returns the same rows as JSON if you would rather pull them on a schedule.
