Skip to content
LocusVia
Enterprise mobile journey control plane

Ship the journey.
Prove the route.

Multi-brand link estates run on one governed routing layer. Merkle-ledger audit trails record every administrative change, Journey Flight Recorder diagnostics reconstruct any journey end to end, and zero-PII edge execution keeps personal data out of public resolution.

Start building Read the quickstart
Evaluating for multiple teams? Request an architecture review
  • iOS Universal Links
  • Android App Links
  • Deterministic deferred routing
  • Journey diagnostics
journey decisionpolicy / evaluated
journeyoffer_launch
entry pointgo.acme.com/offer
device stateios / app installed
policy outcomeopen /offers/launch
fallbackapp store → web
readinessverified
contextpreserved
auditrecorded
flight recordertrace captured
route policydeterministic

One operating model

Entry point to arrival.
One routing layer.

Borrow the simplicity of one smart link, then add the controls enterprise teams need to operate it safely.

/01

Web, social, and email

Land on the promised screen

Open installed apps at the intended destination, with a deliberate store or web fallback when the app is missing.

Explore the journey
/02

Install journeys

Preserve intent after install

Carry the click-time route into first open with deterministic deferred matching and explicit privacy boundaries.

Explore the journey
/03

Physical to digital

Run QR on the same routing layer

Use one governed policy for packaging, signage, receipts, campaigns, and the destinations behind them.

Explore the journey
/04

Journey operations

Explain the route decision

Trace resolution, fallback, and SDK events across tenant and environment boundaries without stitching together separate tools.

Explore the journey

Two teams, one control plane

Built for the people
who ship it—and own the risk.

Developers get a predictable integration path. IT and platform leaders get a governable system boundary.

01 / Mobile engineering

Integrate once. Test the actual journey.

  • Managed AASA and assetlinks.json
  • iOS, Android, and React Native SDK paths
  • Device and route diagnostics
Open developer docs
02 / IT & platform

Govern brands, tenants, and environments.

  • SSO and provisioning controls
  • Fail-closed tenant and environment scope
  • Tamper-evident operational audit
Review the architecture

Firebase Dynamic Links migration

Migrate with a cutover plan.
Not a leap of faith.

Inventory the journeys you already run, map destination and fallback behavior, verify the replacement on real devices, then stage the cutover with a rollback path.

Open the migration guide Review the build path
  1. 01
    Inventory

    Domains, links, app destinations, fallbacks, and campaign dependencies.

  2. 02
    Parity map

    Direct, deferred, store, web, and unsupported-device outcomes.

  3. 03
    Device proof

    Universal Links, App Links, first-open context, and diagnostics.

  4. 04
    Staged cutover

    Observe the new path, keep rollback explicit, then retire the old route.

One clean first run

Domain.
App.
Link.
Proof.

The product and documentation use the same sequence, so teams can see what comes next.

  1. 01

    Connect the domain

    Provision TLS and serve verified Apple and Android association files.

  2. 02

    Register the app

    Bind iOS and Android identities to the correct tenant and environment.

  3. 03

    Issue the SDK key

    Keep staging and production credentials scoped and fail-closed.

  4. 04

    Publish the journey

    Pair the app destination with store and web fallback policy.

  5. 05

    Prove it on device

    Run readiness checks, follow the route, and inspect the journey trace.

Operate with evidence

Journey diagnostics

Flight Recorder shows the evaluated route, platform decision, fallback, and SDK outcome in one trace.

Deterministic deferred matching

Click-time route snapshots survive install without probabilistic guessing unless a tenant explicitly opts in.

Environment isolation

Production SDK keys, domains, and links never resolve staging data. Boundaries are enforced per request.

Ready for architecture review

Enterprise posture
without the attribution bloat.

Keep journey infrastructure focused: deterministic routing, strong boundaries, clear diagnostics, and evidence your teams can inspect.

Enterprise identity

SAML 2.0 and OIDC sign-in with SCIM provisioning for platform teams.

Tamper-evident audit

Control-plane changes are recorded in a cryptographic, append-only ledger.

Zero-PII edge execution

Public link resolution runs at the edge without collecting install-time personal data.

Fail-closed boundaries

Tenant and environment scope is enforced per control-plane and runtime request.

Read the security model

From first route to fleet-wide control

Start with a journey.
Scale with proof.

Build the first verified route yourself, or bring your architecture questions to the team.

Start building Request an architecture review