From a link.To your app.

Configure app links and the SDK to resolve direct links and recover post-install destinations under supported conditions.

Free Beta. No payment required.

From click to app.

SDK result example

Destination for your app/products/42
Link parameters{ "product_id": "42" }deferred: false

A successful direct resolution. The SDK resolves the HTTPS share URL on the server; your app navigates using the returned destination.

Create the link. Handle it in your app.

Configure direct opens, store redirects, and post-install recovery for the conditions your app and domain support.

  1. 01

    Create a destination link

    Set the app path, parameters, platform stores, and web fallback.

  2. 02

    Connect to the app or store

    Configure App Links or Universal Links so your app can receive the link, with a store path available on the web.

  3. 03

    Open the destination in your app

    Navigate when the SDK returns a link. Post-install recovery depends on platform evidence and matching conditions.

Built for links you can own.

Manage links and app settings, then check domain connections and usage.

Direct and deferred links

Resolve a direct link received by your app or return a matched post-install destination. Your app handles navigation.

Service domain connections

Use a service domain after an operator manually connects its DNS, HTTPS, and routing. Custom-domain connections are not available in the current Beta.

Recover the clicked version

A successful match uses the version recorded at click time. Disabled, deleted, or expired links and inactive domains are not recovered.

Setup diagnostics

Check DNS, HTTPS, and app association files. Last-7-day event analytics is not enabled in the current deployment.

Connect your app. Handle the result.

Android and iOS SDK sources, with Flutter and React Native bridges using the same native code. Integrate them using the repository's platform guides.

  • Android
  • iOS
  • Flutter
  • React Native
  1. 1
    Register your project and apps

    Add your Android and iOS app details and get an SDK key for each app.

  2. 2
    Configure the SDK and domain

    Initialize the SDK with a service domain connected by an operator, then connect your app's App Links or Universal Links event handling.

  3. 3
    Test the real connection

    Use a deployed HTTPS domain and app to test direct opens, store redirects, and post-install results on real devices.

Start integrating

SDK result · successful deferred match

{
  "url": "https://go.yourbrand.com/summer",
  "target": "/products/42",
  "params": {
    "product_id": "42"
  },
  "deferred": true
}

A successful match returns this object. Without a match or when the request fails, getInitialLink() returns null. Your app handles navigation.

Start building with Free Beta.

Create a project and see link and SDK usage. Service domains become available after an operator connects them.

No payment details required.

Start Free Beta

Free Beta

Projects
2
Planned custom domain allowance · unavailable in Beta
2
Links created per month
10,000
SDK resolution requests per month
100,000

All projects share workspace limits. Monthly counts use UTC. SDK request limits are informational; exceeding them does not block resolution.

Pro · Business plannedExpansion plans for greater scale and operational features are planned. Pricing is not set, and billing or automatic charging is not connected.

Before you connect your first link.

Is post-install recovery guaranteed on iOS?

No. iOS uses best-effort matching from limited signals and returns no link when evidence is missing or ambiguous. If exact continuity across installation is required, provide a separate explicit-token or same-account flow. When the current SDK returns null, choose a default screen or guidance in your app.

How does each platform connect?

When the OS delivers an App Link or Universal Link, the SDK resolves its share URL on the server. Browser requests redirect to a configured store or web destination based on the OS; the server does not detect app installation. A valid signed Google Play referrer recovers its click. Android without a token and iOS use best-effort matching. Transient Android referrer-read failures require retrying rather than falling back to matching.

How do I prepare domains and app links?

An operator manually connects DNS, HTTPS, and routing for each service domain. Custom-domain connections are not available in the current Beta. Configure Android App Links for the actual release signing identity, or iOS Associated Domains and Universal Links. Diagnostics check DNS and app association files; separately verify post-install behavior with the deployed app on a real device.

Will I be charged automatically after the beta?

Billing is not connected, and we do not collect payment details. Free Beta is the starting offering; Pro and Business are planned expansion tiers. Pricing and commercial transition terms are not yet set.

Are SDK requests the same as installs?

No. Each valid SDK resolution attempt returning HTTP 200 is counted, including no_match results. Retries from the same installation each count once. This is neither a unique-install metric nor a billing basis. Monthly usage is recorded in UTC.