Home Developer Reference Platform Architecture

Platform Architecture

Last updated on Apr 04, 2026

import MermaidChart from '@site/src/components/MermaidChart';

Platform architecture

LinkMe runs as a compact managed edge stack. Every request flows through a small set of services, which keeps deployments predictable and lets SDKs rely on well-defined behaviors.

High-level flow

<MermaidChart chart={graph LR User[User / Device] --> Entry[Global edge entrypoint] Entry -->|Admin UI| Portal[Portal] Entry -->|Links & config| Resolver[Link resolver] Resolver --> Data[(Managed datastore)] Portal --> Data} />

Global edge entrypoint

  • Terminates TLS, enforces routing rules, and fronts both the admin portal and public link resolver.
  • Hosts Universal Links/App Links association files (apple-app-site-association, assetlinks.json) so mobile OSes can trust your domains.

Link resolver service

  • Resolves short links, applies platform routing rules, and records click analytics.
  • Exposes REST endpoints such as /:slug, /d/:slug, /qr/:slug, and the JSON helpers under /api/*.
  • Maintains device fingerprints (cid, IP hash, UA hash) for deferred deep linking claims.

Portal

  • Provides the admin experience for apps, domains, SDK keys, and reporting.
  • Issues API keys, allows toggle of features such as pasteboard support, and surfaces click analytics.
  • Offers marketing pages and articles under /resources/* for discoverability.

SDKs

  • Ship per platform (Android, iOS, React Native, Flutter, Web, Node).
  • Handle initial link opens, in-app listeners, deferred claims, and optional analytics events.
  • Communicate only with the Edge endpoints—no direct datastore or Portal access is required.

Deployment model

  • Managed infrastructure keeps the edge entrypoint, link resolver, and portal running in lockstep.
  • Custom domains CNAME into the edge so certificates can be provisioned automatically.

Data & observability

  • Click and link metadata stay inside the managed datastore powering both portal insights and the resolver.
  • Health probes hit GET /api/health and expect { ok: true }.
  • Logs stream centrally for troubleshooting and incident response.

Use this page with the REST Endpoints & OpenAPI doc to understand how the platform responds in production without exposing internal implementation details.