> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usedynamite.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Read /start/capabilities before choosing an integration. Use the deployed server’s tools/list for current tool inputs.

# System architecture

> The package boundaries, request surfaces and ownership model behind the standalone Dynamite service.

Dynamite is a standalone personalization service. It owns runtime delivery, durable workspace data, releases, setup jobs, preview sessions, MCP credentials and analytics. Ion is an authenticated client, not a second runtime host or direct database reader.

## Package map

| Package / app | Responsibility |
| - | - |
| `packages/adaptive` | Typed manifests, providers, bounded selection, browser profiles and DOM adapters |
| `packages/personalization-server` | Workspaces, releases, setup/authoring, runtime HTTP, enrichment, analytics, memory, MCP and storage |
| `packages/personalization-ui` | Shared editor components and preview client behavior |
| `packages/dynamite-client` | Versioned authenticated Ion integration client |
| `apps/personalization` | Hono/Bun service composition, authentication, tRPC, extension and marketing routes; React dashboard |
| `apps/personalization-extension` | Chrome real-site authoring/preview bridge and visitor tools |
| `apps/landing` | Pre-rendered marketing pages |
| `apps/docs` | Static documentation, search and agent-readable reference exports |
| `apps/personalization-playground` | Fictional local demo sites; not customer production state |

## Request surfaces

| Surface | Authentication / trust | Role |
| - | - | - |
| `/dynamite.js` and CDN bundle | Public shared code | Installer |
| `/personalization/runtime/:id/*` | Exact registered origin for live; scoped bearer for preview | Config, decisions, events and enrichment |
| `/trpc/*` | Dashboard user and organization; origin checks | Authenticated product operations |
| `/api/extension/*` | Extension authentication and scoped sessions | Real-site editing/preview |
| `/mcp/dynamite` | Scoped bearer key plus live access validation | Agent authoring and measurement |
| `/api/ion/v1` | Signed, short-lived service identity | Ion client integration |
| `/*` | Public static files | Human and agent documentation |
| `/health` | Operational read | Storage and decision-model readiness |

## Serving boundaries

The standard browser decision is one bounded server-side choice call for all relevant slots. Editorial candidate choices can join that call. Setup/research and generative variant authoring run separately from visits. They can be slower and use different model credentials without entering the page's decision deadline.

The CDN hosts shared script assets and release metadata. The application service continues to own configuration, decisions, authentication, billing and data. A static script deployment does not migrate workspace storage or publish new customer content.

## State and process ownership

Dedicated Postgres stores durable production records. Local development can use files when no database is configured; analytics then uses memory. Preview sessions, active setup execution, caches and some scheduling state remain process-local.

Keep one active execution owner. Horizontal replicas or overlapping active deployments are not safe merely because the data is in Postgres. A draining/standby rollout must transfer background ownership deliberately after checking work and connections. Retain the legacy volume for pre-cutover recovery.

## Ion integration

Ion uses a versioned client with a 60-second HMAC-signed identity bound to the service origin. The shared secret stays server-side. Organization/user checks remain in Dynamite and, where required, its fixed Ion callback. Shared adaptive, UI and client artifacts are exported together with source commit and hashes. Server implementation and private workspace records are not client artifacts.

See [storage and security](https://docs.usedynamite.com/internals/storage-and-security.md), [development](https://docs.usedynamite.com/internals/development.md) and the [source map](https://docs.usedynamite.com/reference/source-map.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.