External Integrations

Architecture Context

High-level system context for external integrators. This page is supplementary; endpoint behavior remains defined by the runtime API implementation.

Platform Providers

  • Cloudflare: Workers, Pages, R2, CDN, KV, Queues, Cron.
  • Neon: transactional PostgreSQL source of truth for write-heavy domains.
  • Turso: edge-replicated SQLite for low-latency read-heavy device workflows.
  • Clerk: user/org auth and tenant identity context.

Applications

  • API: Cloudflare Workers + Hono endpoints (public, tenant, admin, device).
  • Web: advertiser portal and onboarding surfaces.
  • Admin: internal operations and moderation console.
  • Docs: external and internal integration documentation.
  • TV Player: Android TV runtime for playlist playback and telemetry.

Core Data Flows

  • Campaign updates -> Neon -> queue workflows -> decisioning projections in Turso.
  • Devices fetch playlists/config from Turso (and fallback paths) with media from R2/CDN.
  • Runtime telemetry writes to Turso events and feeds downstream analytics pipelines.
  • Clerk webhooks synchronize user/org membership data into Neon identity schema.