Skip to content
Tilecast Docs

Architecture

Repository layout

Section titled “Repository layout”
  • Directorytilecast/
    • Directoryapps/ Product applications.
      • Directoryserver/ Go server, HTTP API, and database migrations.
        • …
      • Directorycli/ Remote tilecast CLI and its MCP server.
        • …
      • Directorydashboard/ React and TypeScript management app, Tilecast Studio.
        • …
      • Directoryplayer-android/ Kotlin and Jetpack Compose Player for Android TV devices.
        • …
      • Directoryplayer-linux/ Electron Player for Linux kiosk devices.
        • …
      • Directoryedge/ Tilecast Edge, the new Linux player: a Rust daemon, a WPE WebKit renderer, update and migration helpers, and a small user-session bridge.
        • …
      • Directorydocs/ Astro and Starlight public documentation site.
        • …
    • Directoryplugins/ Bundled plugins, one directory each.
      • …
    • Directorywidgets/ Core Widgets, one directory each.
      • …
    • Directorypackages/ Shared design tokens, the API client, application contracts, and the plugin and Widget SDKs.
      • …
    • Directorydeploy/ Docker deployment and optional network integrations.
      • …
    • Directorydocs/ Engineering references, API descriptions, and implementation contracts.
      • …

The Server is a modular monolith backed by one PostgreSQL database and one organization per installation. Studio consumes the generated OpenAPI contract through typed transport and API domain modules. Android uses a native Player; Electron and WPE hosts share the Player Runtime renderer. Read the living architecture reference for ownership boundaries and links to the exact domain contracts.

Section titled “Where to read next”

These engineering documents live with the code and are the contracts for each area. This site doesn’t repeat them.