Professional

Create expiring location links from your own systems, with one API call and no map to build.

What a key gets you today

Links from your own code — one POST /v1/links returns a URL you can put in a message, an email or a job sheet.
Live sessions up to 24 hours — a device keeps the position updated for the length of a shift. Anonymous browser sessions stop at 3 hours.
Usage you can check before an invoice quotes it — GET /v1/usage, counted per UTC day. A number nobody can verify is a number they will first check while disputing it.
A contract that is tested, not just published — the specification at /v1/openapi.json is the same definition the service answers from, and the build fails if they disagree.
Links that expire on their own — the same guarantee the free product makes. Past its deadline a link is gone to everyone who holds it; the row itself is swept within about two days, which is the storage layer's own schedule rather than ours.

What is not built yet

Listed rather than left out. Finding this during an integration is worse than reading it now.

Webhooks
Custom domains
A published SLA
A signed DPA

Each is deliberately unbuilt rather than merely unfinished: an event taxonomy invented before a customer needs one stops being a guess the moment somebody integrates against it.

What it will cost

Usage-based — around €49 a month to start, and a few cents per live session after that.

Those numbers are working figures, not a quote, and nothing here is on sale yet: there is no card form because there is no billing account behind it. They will be fixed before anyone is asked to pay, and the first customers will hear the real ones from a person.

Getting a key

There is no way to ask for one yet. Keys are issued by hand, and the request route — an address or a form — is not set up, so this page is not going to offer you one that quietly goes nowhere.

Sharing a location with a friend is free and needs no account — that is on the home page, and it always will be.