TTopcoaton Cloudflare
GET /api/health
Client + server reactivityBrowser → Worker

One syntax, two execution boundaries.

The counter and disclosure update immediately in your browser. The search input passes its value to a shard, which asks the Worker for fresh HTML.

Browsersignal count

Instant client expressions

These controls do not make a network request.

Release confidence

2 / 10

How did that update?

Toggle a reactive attribute.

Browser → Worker#[shard]

Server-filtered component catalog

Every changed query re-renders only the results fragment at the edge.

8 matchesHTML from Worker
  • SignalsBrowser

    Local state with typed get and set expressions

  • Bind attributesBrowser

    Reactive DOM properties such as hidden and value

  • Event handlersBrowser

    Rust closures compiled into browser JavaScript

  • ShardsWorker

    Server-rendered components driven by reactive arguments

  • ProceduresWorker

    Async server functions callable from the browser

  • ComponentsWorker

    Async Rust functions that return composable views

  • CookiesWorker

    Request-scoped typed state written through response headers

  • HTMXWorker

    Explicit fragment requests and typed response headers