Live · Codense product

Every deep link, tested where it actually opens.

Create, track and validate the deep links behind your app marketing — universal links, app links, store fallbacks and deferred attribution — checked on real platforms every release. From the browser, from a desktop app on the release checklist, or from the app on the phone in your hand.

Product

Diver

Built for

app teams whose deep links work in the demo and break in the wild.

Visit diver.mthy.dev

diver.mthy.dev

Link checks

every release

app.example/checkout iOS 18 · Universal Link · opens app pass
app.example/checkout Android 15 · App Link · opens app pass
app.example/offer/spring not installed · store fallback pass
app.example/ref/partner-7 deferred attribution · 24h window pending

Recent checks 97.22%

72 checks ago now

Web app: Live
Desktop app: Live
Mobile app: Live
Data residency: EU only

Why it exists

The problem we got tired of

Every app team we met tested deep links the same way: install, tap, hope. Then a campaign shipped a link that opened the store instead of the offer, and nobody knew for a week. Diver exists so the link is tested before the campaign is — and so the marketer who made the link sees exactly what the engineer sees when it fails.

What it replaces

4 subscriptions, or one.

Each of these is a tool teams buy separately, with its own alert rules and its own bill. That is the problem, not the feature list.

Link shorteners
Attribution SDKs
QR generators
Manual deep-link test matrices

Diver

Deep links

One dashboard, one alert engine, one bill. 4 subscriptions become one, and the alerts finally agree with each other.

Was: 4
Now: 1

What it does

The parts that matter

Not a feature list. The handful of decisions that make it different from assembling the same capability out of four subscriptions.

Tested where it opens, not where it is written

Each link is resolved on iOS and Android, with and without the app installed, and the result is kept per platform and per campaign — so "it works on my phone" stops being the test plan.

Marketing and engineering see the same link

The link a marketer creates in the browser is the link the engineer sees fail on a device: same identifier, same history, same screen.

One product, three surfaces

A browser SaaS for the team, a desktop app for the release checklist, and a mobile app that tests a link on the device you are holding. Kotlin underneath, Vue on the web.

Under it

What it runs on

Kotlin Vue PostgreSQL Hetzner (DE)

Next up

What comes after this

In the order we expect to ship it. Say if you need one sooner.

01 Campaign attribution reports Planned
02 Team roles and link approvals Planned
03 A public API for creating links Planned

Ask for early access

The same hands

What building this taught us to sell

Every capability below is one we practise on our own production before we bill anyone for it.

Quality

Product engineering

From a whiteboard to something your users can break.

We build and ship product software end to end — domain model, API, interface, pipeline, on-call runbook. Small teams, short feedback loops, and a codebase your...

Quality

Quality engineering

Confidence, expressed as a pipeline.

Quality is not a phase at the end of a project — it is how fast you can change something and still sleep. We build the...

Quality

App development

Native when the platform matters. One codebase when it does not.

iOS and Android apps, designed before they are built. Swift and Kotlin when a product needs the platform underneath it; Flutter or React Native when one...

Also ours

Other products

Live

Monitoring

Detectly

Six monitoring tools in one, hosted entirely in the EU.

Uptime, API checks, recorded browser flows, visual regression, sitemap scanning and cron heartbeats — behind one dashboard, one alert engine and one on-call chain,...

Production

checks every 60s