Home - the full story
Hero thesis (what + difference, one glance)
LnkApp is enterprise-grade link infrastructure, self-serve in minutes. Every link you publish resolves at the edge, on your own domain, and the numbers that prove it are on this page.
- Links resolve at the Cloudflare edge - 300+ cities Cloudflare published network data · quarterly
In depth
A link is a promise: something real is on the other side. LnkApp treats that promise as infrastructure — served at the edge, measured against service levels, owned on your domain.
The platform covers the full working surface: link management, custom domains, analytics, alerts and monitoring, webhooks, and a complete API. Builders integrate it, Operators run campaigns on it, Stewards audit it — the same links, the same numbers, for all three.
Nothing on this page asks you to take our word for it. Measured figures come from live telemetry and carry their source and date. Verifiable statements point to public documentation you can read yourself.
- Links resolve at the Cloudflare edge - 300+ cities Cloudflare published network data · quarterly
Persona path cards (self-selection fork)
Building on the API? Read the docs — the quickstart is two clicks away. Running links at scale? See how it works, with the analytics shown as they are. Reviewing us for your organization? Review the security posture — it is public.
In depth
The site has one story but three working entrances.
- Builders go to the docs. The API quickstart shows a link created in one call, and the reference covers the full surface. Read the docs.
- Operators go to the product walkthrough. The mechanism, the live service-level panel, and the analytics view are shown from the real dashboard. See how it works.
- Stewards go to the security page. Encryption, data lifecycle, and access controls are documented in public, written to survive a security review. Review the security posture.
Wherever you enter, the trust surfaces stay one interaction away, and pricing is public.
Mechanism explainer (the Trace: click to edge to destination)
When someone clicks your link, the request reaches the nearest edge city and the redirect resolves right there. The visitor lands at the destination without a detour to a distant origin server. That is the whole mechanism — short path, measured result.
- Links resolve at the Cloudflare edge - 300+ cities Cloudflare published network data · quarterly
In depth
Follow one click end to end.
1. Request. A visitor clicks your link — from a campaign, an invoice, a QR code. 2. Edge. The request arrives at the nearest edge location, where your redirect rules already live. Resolution happens there, close to the visitor, wherever they are. 3. Destination. The visitor lands. The redirect recorded what it needed for your analytics on the way through.
Because resolution happens at the edge rather than at a single origin, distance stops being the dominant cost. The latency figure below is measured from live redirect telemetry — percentiles from production traffic, not a benchmark run.
- Links resolve at the Cloudflare edge - 300+ cities Cloudflare published network data · quarterly
Live SLO instrument panel
This panel is not a summary we wrote — it renders live service-level metrics from the product's own telemetry surface. If you are deciding whether your traffic is safe with us, decide on the measurements, not on our adjectives.
- Service levels are measured and visible - watch them yourself product telemetry: slo_metrics via API · live
In depth
Every service level we publish is measured continuously and surfaced through the product API. This panel reads that surface directly: what you see is the current measurement, with its source and timestamp, not a marketing snapshot. There is no separate feed for the website.
Two properties matter for a reliability review:
- The metrics are live. The panel renders from product telemetry, so the figure on this page is the figure in production right now.
- The metrics stay visible. Watching them is not an evaluation-day privilege — the point of the claim is that you can keep watching after you sign up.
- Service levels are measured and visible - watch them yourself product telemetry: slo_metrics via API · live
Customer-branded link card (your domain, first-class)
Your links live on your domain, carrying your name — not ours. The data they generate is yours in the practical sense: export everything, anytime, in full. Ownership you cannot exercise is not ownership.
- Your domain, your data: export everything, anytime product: GDPR export/deletion handlers · per-release
In depth
The ownership boundary is drawn deliberately, and it is drawn around you.
- Your domain, first-class. Links resolve on the domain your audience already trusts. Your brand is on the link; ours is in the infrastructure underneath it.
- Your data, exportable in full. Every link, every record — the export is complete, and it is available whenever you want it, not as a support ticket.
- Your exit, real. If you leave, your links and your data go with you. We would rather earn the renewal than hold the keys.
- Your domain, your data: export everything, anytime product: GDPR export/deletion handlers · per-release
Start steps (signup to first link, timed)
Three steps, each timed as you go: create an account, create a link — on your own domain if you have one ready — and watch it resolve. No sales conversation stands between you and a working link. Start free.
In depth
The path from zero to a resolving link:
1. Create an account. Self-serve signup; you are in the dashboard directly. 2. Create your first link. Paste the destination and publish. If you brought a custom domain, connect it here — or start on the default and move later. 3. Watch it resolve. Click your link and see it work; its analytics record starts with that first click.
Each step on this page is timed, so the "in minutes" statement is one you watch happen rather than take on faith. Builders who prefer to start in the terminal can make their first link through the API instead — see the quickstart.
Start free.