tokio-rs/topcoat

▲ 132 stars today★ 5,028⑂ 178

A batteries-included framework for building web apps

About tokio-rs/topcoat

tokio-rs/topcoat is an open-source project on GitHub, mainly written in Rust. A batteries-included framework for building web apps It currently holds 5,028 stars and 178 forks with 29 open issues, and was last pushed on 2026-09-22 (repository created 2026-04-03).

Project Overview

Git Homed tracks it on the Today's Trending board, currently at rank #36 with 132 new stars today.

GitHub Repository Details

Repository tokio-rs/topcoat · default branch main · size 5551 KB · watchers 40 · source: GitHub REST API and repository README

README

https://github.com/tokio-rs/topcoat/blob/HEAD/Topcoat

The full full-stack framework for Rust

[![Crates.io][crates-badge]][crates-url] [![Docs.rs][docs-badge]][docs-url] [![MIT licensed][mit-badge]][mit-url] [![Build Status][actions-badge]][actions-url] [![Discord chat][discord-badge]][discord-url]

[crates-badge]: https://img.shields.io/crates/v/topcoat.svg?style=flat-square [crates-url]: https://crates.io/crates/topcoat [docs-badge]: https://img.shields.io/docsrs/topcoat?style=flat-square [docs-url]: https://docs.rs/topcoat/latest/topcoat [mit-badge]: https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square [mit-url]: https://github.com/tokio-rs/topcoat/blob/main/LICENSE [actions-badge]: https://img.shields.io/github/actions/workflow/status/tokio-rs/topcoat/ci.yml?branch=main&style=flat-square [actions-url]: https://github.com/tokio-rs/topcoat/actions?query=workflow%3ACI+branch%3Amain [discord-badge]: https://img.shields.io/discord/500028886025895936.svg?logo=discord&style=flat-square [discord-url]: https://discord.gg/tokio

Topcoat is a modular, batteries-included Rust framework for building full-stack apps. It prioritizes simplicity and productivity. See Learn Topcoat to get started, or the Roadmap for what's coming next.

Early-stage and experimental. Expect breaking changes.

```rust,ignore use topcoat::{ Result, router::{Router, RouterBuilderDiscoverExt, page}, view::{View, component, view}, };

[tokio::main]

async fn main() { topcoat::start(Router::builder().discover().build()).await.unwrap(); }

[page("/")]

async fn home() -> Result { Ok(view! { <!DOCTYPE html> hello(name: "World") }) }

[component]

async fn hello(name: &str) -> Result { Ok(view! {

"Hello, " (name) "!"

}) }

What makes Topcoat different Client reactivity without the boilerplate Topcoat renders all markup on the server: components can be async and query the database directly, eliminating all the traditional boilerplate needed for a separate API layer. Interactivity does not have to cost a round-trip, though. A $(...) expression is 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. No wasm bundle, no client build step:

rust,ignore

[component]

async fn faq(cx: &Cx) -> Result { let open = signal(cx, || false);

Ok(view! { // Runs entirely in the browser; no server round-trip. "What is Topcoat?"

"A full-stack Rust framework."

}) }

When an update does need the server, like fresh search results, mark the component as a #[shard]. Topcoat re-renders it on the server whenever one of its $(...) arguments changes and swaps the new HTML in place:

rust,ignore

[component]

async fn search(cx: &Cx) -> Result { let query = signal(cx, String::new);

Ok(view! {

// Updates as the user types. search_results(query: $(query.get())) }) }

[shard]

async fn search_results(cx: &Cx, query: String) -> Result { Ok(view! {

(product.name)

}) }

Powerful, unsurprising HTML templates The view! macro stays true to HTML and Rust. Use familiar Rust control flow as part of your templates:

rust,ignore view! { for item in nav_items { (item.label) } }

Use the topcoat fmt CLI command to automatically format view! snippets (and other macros) across your codebase. Module-based routing Topcoat can optionally infer your route tree from your app's module structure (without a build step):

text src/ |-- app.rs -> / (and the root layout) `-- app/ |-- about.rs -> /about |-- _marketing.rs (layout, no URL segment) |-- _marketing/ | `-- pricing.rs -> /pricing |-- posts.rs -> /posts |-- posts/ | `-- id.rs -> /posts/{post_id} `-- api/ `-- health.rs -> GET /api/health

Premade components you can edit Topcoat UI is a component library based on Tailwind inspired by shadcn/ui. Components are copied into your project via the topcoat ui CLI command, meaning you can freely change their design and functionality to fit your use case:

rust,ignore

[component]

async fn delete_card() -> Result { Ok(view! { card( card_header( card_title("Delete workspace") card_description( "This permanently removes the workspace and all of its data." ) ) card_footer( attrs: attributes! { class="justify-end" }, button(variant: ButtonVariant::Ghost, "Cancel") button(variant: ButtonVariant::Destructive, "Delete workspace") ) ) }) }

Asset bundling The bundler scans your compiled binary for asset! calls, copies (or even downloads) every file into a local asset directory, and allows Topcoat to serve them efficiently with aggressive browser caching.

rust,ignore const FERRIS: Asset = asset!("./ferris.png");

view! { }

Topcoat also ships with utilities for web fonts and icons, as well as easy integrations for Fontsource (Google Fonts) and Iconify. Built-in Tailwind support Enable the tailwind feature to integrate Tailwind into your project:

rust,ignore view! { } ```

Learn Topcoat

Start here

Getting started: create a new project, install the CLI, run the dev server.
Source code formatting: topcoat fmt for macro bodies.

Rendering

The view! macro: templating syntax, control flow, conditional attributes.
[The #[component] macro](https://docs.rs/topcoat/latest/topcoat/view/attr.component.html): async functions as components, with child content.
The attributes! macro: reusable runtime attribute fragments.
The class! macro: space-separated class lists from static and conditional entries.
The live! and emit! macros: stream slow parts of a page in after the rest, with the suspense and error_boundary components built on them.

Routing

Router: pages, layouts, and API routes; manual and auto-discovered.
Module-based routing: derive the route table from your module tree.

Working with requests

Request context (Cx): the value pages, layouts, and components read from.
App context: share long-lived values across requests, keyed by type.
Memoization: #[memoize] for per-request caching and fan-out dedup.
Functions, not middlewares: the recommended way to model auth and other request-scoped concerns.
Cookies: read and write the request cookie jar, with signed, encrypted, and prefixed cookies.
Sessions: bring-your-own-storage session authentication: login/logout lifecycle, sliding expiration, and token rotation.

Asset system

Assets: declare assets in Rust, serve them with content-hashed URLs.
Fonts: bundle and serve web fonts.
Icons: download Iconify icon sets or declare your own.

Client reactivity

The runtime: signals, $(...) expressions, @ event handlers, and : bind attributes.
Expressions: the dual Rust/JavaScript expression language and its vocabulary.
Procedures: async server functions callable from the browser.
Shards: components that re-render on the server when their arguments change.

Miscellaneous

Topcoat UI: premade components vendored into your project for you to edit.
Mail: declare mail with the mail! macro, deliver through SMTP, file, or in-memory transports.

Third-party integrations

Tailwind: Tailwind CSS without Node, wired into the asset pipeline.
htmx: drive partial HTML swaps from the server with request/response header helpers.
Alpine AJAX: drive partial HTML swaps from the server with Alpine AJAX's request-header conventions.
Datastar: patch elements and signals into the page over server-sent events.

Roadmap

Planned features we'd like to bring to Topcoat. Have an idea? Open an issue.

[ ] topcoat new CLI command to bootstrap pre-configured projects
[ ] Static export
[ ] (More) reactivity (topcoat-runtime)
[ ] More Topcoat UI components, full "blocks" e.g. sign-in form
[ ] Better Toasty integration (safely create/update records from forms without listing out all the fields)
[ ] Validations
[ ] Localization support
[ ] OpenAPI endpoints
[ ] Docs for how to deploy Topcoat
[ ] Pre-rendering for static pages
[ ] Client-side navigation + prefetching
[ ] WebTransport
[ ] Image optimization / resizing
[ ] Markdown support
[ ] Easier-to-use middlewares like rate-limiting, compression, etc.
[ ] Authentication
[ ] Background jobs
[ ] Islands

GitHub Stars & Activity

5,028Stars

178Forks

29Open issues

RustLanguage

GitHub Popularity

GitHub stars5,028

Forks178

Open issues29

Primary languageRust

LicenseMIT

Stars gained today132

Created2026-04-03

Last pushed2026-09-22

Trending History

Daily boardrank #36 · ▲ 132 stars

tokio-rs/topcoat

About tokio-rs/topcoat

Project Overview

GitHub Repository Details

README

The full full-stack framework for Rust

[tokio::main]

[page("/")]

[component]

"Hello, " (name) "!"

What makes Topcoat different

Client reactivity without the boilerplate

[component]

[component]

[shard]

Powerful, unsurprising HTML templates

Module-based routing

Premade components you can edit

[component]

Asset bundling

Built-in Tailwind support

Learn Topcoat

Roadmap

GitHub Stars & Activity

GitHub Popularity

Trending History

Related GitHub Projects

clash-verge-rev / clash-verge-rev

juspay / hyperswitch

tinyhumansai / openhuman

lbjlaq / Antigravity-Manager

cloudflare / quiche

dmtrKovalenko / fff

max-sixty / worktrunk

akitaonrails / ai-memory

More Trending Repositories