Topcoat, an Early-Stage Rust Web Framework From the tokio-rs Organization, Renders on the Server and Translates Marked Expressions to JavaScript

Overview

Topcoat is a Rust web framework that The Register reports was demonstrated by Carl Lerche, an Amazon Web Services principal engineer, at ScyllaDB’s 2026 P99 virtual conference. The project’s README describes it as “a modular, batteries-included Rust framework for building full-stack apps” and flags it: “Early-stage and experimental. Expect breaking changes.”

What We Know

Who is behind it. The Register says Lerche is “perhaps best known for creating Tokio, which is the most popular asynchronous Rust runtime in that ecosystem.” The Topcoat repository sits under the tokio-rs organization on GitHub and is MIT licensed, per its README.

How it renders. According to the README, Topcoat renders all markup on the server, and components can be async and query the database directly. A $(...) expression is, in the README’s words, “ordinary type-checked Rust that Topcoat evaluates on the server for the initial render and also translates to JavaScript, so it re-runs instantly in the browser.” The README adds “No wasm bundle, no client build step.” A component marked #[shard] is re-rendered on the server when one of its $(...) arguments changes, and the new HTML is swapped in place.

How it differs from other Rust web frameworks. The Register notes that Leptos and Dioxus “compile Rust into WebAssembly,” while Topcoat “compiles your Rust code into more web-friendly JavaScript.” The article says developers can write client-side logic using a subset of Rust, which Topcoat compiles into JavaScript for the browser. It also places Topcoat alongside HTMX, Datastar and Phoenix LiveView, which render pages on the server, and reports Lerche saying Topcoat is adapting their ideas to fit Rust.

Page loading. The Register says Topcoat renders all components at once rather than one by one, and that data loading does not block the page, so the server can send the head of the HTML template immediately and let the browser begin preloading assets such as CSS or images. It also credits Toasty, “a Rust-based asynchronous database object-relational mapper” from Lerche, with letting a server-side component talk to the database directly.

Other features listed in the README. The README lists a view! macro for HTML templates with Rust control flow, optional routing inferred from the module structure without a build step, and Topcoat UI, a Tailwind-based component library inspired by shadcn/ui whose components are copied into a project with the topcoat ui command. It documents integrations for htmx, Alpine AJAX and Datastar.

Views Reported

The Register quotes Lerche telling the audience that “you probably would have called me crazy” three years ago for suggesting Rust could be the best language for building web apps. The same article says Lerche acknowledged Topcoat is not for building complex applications “on the scale of, say, Figma.”

Frontend developer Ken Kohlman, who summarized the project on his “Code to the Moon” YouTube channel, said “The simplicity is incredible, and it is something that we have been sorely missing in this space,” according to The Register. The article adds that Kohlman agreed with Lerche that Topcoat is best for smaller web projects, given that it uses only a subset of Rust syntax, and that he said “There’s something to be said for having the full Rust syntax at your disposal.”

What We Don’t Know

• The Register does not report adoption figures or production users, and the README gives no performance benchmarks.
• The README’s roadmap lists planned features, including static export, validations, OpenAPI endpoints, authentication, background jobs, islands, and docs for how to deploy Topcoat, per the README.
• DevClass carried the same text under the same byline, so it is not a separate account of the talk. No independent hands-on evaluation of Topcoat was found among the sources reviewed.