Krate Docs

#Rendering internals

How static shells, dynamic regions, and the SSR/ISR sidecar fit together.

How the rendering modes in Rendering are implemented.

  • The Go compiler builds every page to a static shell. Server components are baked; static suspense content is baked as its resolved HTML; dynamic boundaries become splice markers (<!--suspense:...--> for Suspense regions, <!--region:...--> for standalone runtime components).
  • SSR/ISR pages carry one coarse "page" region marker around the whole body.
  • The Node (or bun/deno) sidecar renders only the regions the Go server asks for - via /__krate/regions - using the compiled page bundle (dist/.krate/server-bundles/...) or the compiled runtime-component bundles (dist/.krate/server-components/...). The Go server splices the returned HTML into the shell and streams it.
  • The Go server resolves the concrete URL to the page's canonical route (e.g. /video/abc -> /video/[id]), forwards the URL params, and keys ISR caching by route + params + query.
  • dist/.krate/manifest.json records each page's mode, and dist/.krate/server-manifest.json lists the page bundles and each page's region registry for the sidecar.

See Choosing an approach for what to use when.

Last updated: 2026-11-17

Contributors: Noinkin