← All solutions

Startups

Set it up this afternoon. Forget it until the rebrand.

The link layer is trivial right up to the moment it is load-bearing: the app store links in your onboarding email, the code on the sticker, the URL in the docs that has moved twice this year. It should take an afternoon, and then never need you again.

What this is for

Four situations, and what happens in each.

  1. 01

    A domain that looks like you own it

    go.yourcompany.com, rather than a shared shortener nobody recognises. Two DNS records, and the certificate is issued and renewed without you. It is the cheapest thing you can do to make a small company look deliberate.

  2. 02

    Links made by code

    A REST API with an OpenAPI document. The link for a release is created by the deploy that ships it; the link in a transactional email is created by the job that sends it. These are the same endpoints the dashboard uses.

  3. 03

    One link for both app stores

    An OS rule sends iOS to the App Store and Android to Google Play. Everyone else gets a page explaining why they cannot install it. One link on the sticker, in the email, and in the docs.

  4. 04

    A free tier with no timer

    Twenty-five links, analytics and QR codes, without a card. Outgrow it and the links you have already made keep working — you just cannot make new ones until you upgrade or delete a few.

An afternoon, in three moments

Set-up, first link, and the one rule you will need.

01Thursday, after standup

You point a subdomain at it

go.yourcompany.com is a CNAME and a TXT record at whoever holds your DNS. The certificate is not your problem, then or in a year.

Add the domain, paste the two records, and watch it go from verifying to live. The dashboard says which record it is still waiting on.

fixedlink.dev/dashboard/domains
The domains page with one domain live and one still verifying
One live, one mid-flight. Nothing here says "pending" without saying what for.

02Ten minutes later

The first link, and what it will look like

The onboarding email needs a link to the docs, and it will be pasted into Slack by half the people who get it.

Destination, domain, slug. The card it will unfurl with is read off the destination while you are still typing, so you find out now rather than from a screenshot in a support ticket.

fixedlink.dev/dashboard/links/new
Create, then the card arriving a beat later from the destination page.

03Launch week

One link, two app stores

The sticker, the email footer and the docs all need the same link, and it has to land each person somewhere they can actually install from.

Two OS rules and a fallback. Check where a visitor would land before you save it — the simulator runs the same logic the redirect does.

fixedlink.dev/dashboard/links/booth-qr/routing
Flipping one fact about the visitor, and the answer changing with it.

Plans

What it costs

Free while you are small. Pro when you want the domain and the API, at a flat monthly price with no per-seat arithmetic.

FreeFree
Everything you need to start sharing links.
Pro$25/mo
Your own domains, your own data, no limits.
EnterpriseTalk to us
For teams that need scale, control and a contract.

The domain takes ten minutes. The rest is one API call.