Architecture

A curated map of the Vango architecture docs and what each internal document covers.

Updated 2026-05-09Edit this page

Architecture

The public programming model is only half the story. Vango also ships internal architecture docs that explain how the runtime, renderer, protocol, persistence, and security model fit together.

Document Map

The current architecture set covers:

  • system overview

  • server runtime

  • rendering and patch pipeline

  • reactivity and state

  • routing and HTTP

  • client runtime

  • protocol and sync

  • persistence and resume

  • security model

  • toolchain and dev

  • universal, macOS, and iOS surfaces

  • media capture and audio

When To Read These

Read the architecture docs when:

  • you are changing framework internals

  • you need to understand a tricky lifecycle or protocol behavior

  • you are debugging a patch, session, or persistence issue below the app-authoring surface

Canonical Source

The architecture docs live in the Vango repo:

  • Architecture Index

  • System Overview

  • Server Runtime

  • Rendering & Patch Pipeline

  • Reactivity & State

  • Routing & HTTP

  • Client Runtime

  • Protocol & Sync

  • Persistence & Resume

  • Security Model

  • Toolchain & Dev

  • macOS Desktop Surface

  • iOS Integration & App Store Compliance

  • Media Capture & Audio

Use the right document level

If you are building app code, stay on the public authoring surface first. Drop to the architecture docs when you need internals, not as a default starting point.