Current renderer
Prerendered HTML; controls are waiting
BLAZOR / .NET 10 / INTERACTIVE AUTO
One page. Two runtimes.
No database.
Explore what runs on the server, what runs in your browser, and when JavaScript can join in.
All visitor records are fictional. This demo generates 48 repeatable samples locally. It doesn't record your visits or create a visitor cookie.
Data generated by
Included in the initial HTML
Service calls
Persisted with the data across prerendering
Browser JavaScript
Imported after the first interactive render
Try it in this runtime
Click Run C# to see where the event executes.
JavaScript always executes in the browser. With Server interactivity, C# reaches it over the circuit; with WebAssembly, C# runs alongside it in the browser. These diagnostics are displayed only here.
FICTIONAL SAMPLE / 1 OCTOBER 2026 / UTC
Visitor sample
48 of 48 records
Sample ID Press Enter to sort | Time (UTC) Press Enter to sort | Browser Press Enter to sort | Device Press Enter to sort | OS Press Enter to sort | Mock ms Press Enter to sort |
|---|
| demo-001 | 11:43 | Chrome | Desktop | Windows | 34 |
| demo-002 | 11:26 | Chrome | Phone | Android | 402 |
| demo-003 | 11:09 | Edge | Laptop | Windows | 282 |
| demo-004 | 10:52 | Safari | Laptop | macOS | 259 |
| demo-005 | 10:35 | Safari | Laptop | macOS | 49 |
| demo-006 | 10:18 | Edge | Laptop | Windows | 429 |
| demo-007 | 10:01 | Firefox | Desktop | Linux | 180 |
| demo-008 | 09:44 | Safari | iPhone | iOS | 347 |
Read the lifecycle
- Prerender. A full page request produces HTML on the server. The mock data and counters are serialized with
[PersistentState]. JavaScript isn't available yet. - Become interactive. Auto chooses Server or WebAssembly. The component restores the sample instead of fetching it again, then rebuilds the filtered summaries.
OnAfterRenderAsyncimports the JavaScript module. - Interact. The C# counter and filters execute in the renderer shown above. Reloading samples calls the same mock service in that runtime, without an API request.
- Visit again. After the WebAssembly bundle is downloaded and cached, a new page load can use WebAssembly. An existing Server component does not switch runtimes mid-session.
Open this page in a fresh browser profile to observe the first visit. Wait for the framework downloads to finish, then use a full reload to test the cached visit. Auto can retain the runtime already in use by other interactive components.
Navigation inside this site's interactive router normally reuses its runtime and skips a new page prerender. This differs from enhanced navigation in static SSR, which fetches HTML from the server. Neither is a reliable count of unique visitors.