System context

This view shows the actors outside synkd and the two host options inside.

What this shows

1. Browsers use Studio or your own partysocket apps.
2. Operators use the Console, CLI, and deploy scripts.
3. An optional TLS ingress (usually Caddy) terminates HTTPS.
4. Traffic then goes to either the Node runtime or a Durable Objects fleet.
5. Both hosts run the same party classes from @synkd/server.

Why it matters

You write party logic once. Local development uses synkd up on Node. Production fleets use synkd deploy without rewriting application code.

Studio and Console are clients. They do not embed party business logic.

What to do next

• Package layers for the monorepo stack
• Fleet topology for the multi-node path
• Get started for developers