Proa — The next era of web interfaces. Built in Rust.

Theme it, compose it, ship it.Browse Components Does it need JavaScript?Is it accessible?Can I restyle it?Single or multiple open panels, with a CSS-only build that ships no JavaScript at all.InvoiceStatusAmountINV-2041Paid$1,499.00INV-2042Pending$399.00INV-2043Paid$399.00INV-2044Refunded$399.00Header, body, footer, and caption parts that compose into dense record views.Solid, outline, ghost, and link variants across three sizes and three intents.WorkspaceUsed in your deploy URL.Server render by defaultShip islands only when neededLabels, descriptions, and error text wired to any control, in either orientation.Deploy previewPushed 2 minutes ago to main.Render41µsClient JS0kBBuilt from source in your repo.Header, content, and footer slots for the surface most product screens are built from.March 2026MoTuWeThFrSaSuSingle and range selection, month paging, and keyboard navigation, rendered as plain HTML.Weekly requests36.2k01.8k3.6k5.5k7.3k3.2kMon4.1kTue3.8kWed5.2kThu6.4kFri5.9kSat7.3kSunArea, bar, line, donut, and stacked series drawn as pure SVG on the server.Grouped one-time-code slots with separators, size variants, and a caret you can style.MEYouCan an agent add a settings page to this app?9:41AIProaYes. Every component is typed Rust in your repo, so the compiler checks the edit before it ever reaches a browser.9:41MEYouHow much JavaScript does that ship?9:42Message bubbles, avatars, timestamps, and typing indicators for assistant surfaces.Syntax highlighting done on the server, so no highlighter ships to the browser.58components, every one with a live example, a props table, and Rust you can copy.Scroll sideways or use the arrow keys to move through the component demos. Everything people want from a modern web app, without the render tax underneath it.A component system and a framework surface, not a templating engine.FrameworkFramework primitives beyond template glue.Proa keeps streaming, request data, routing, metadata, and response control inside the same typed WebContext as your components.Streaming SSR, in order or out of orderFlush HTML in document order when sequence matters, or let Suspense boundaries stream ready chunks out of order when slow data should not block the page.DataLoader-backed WebContextEvery render has typed access to request-scoped data, response metadata, route state, and loader caching through the same WebContext components already receive.Typed SSR framework semanticsLayouts, routing, metadata, static assets, forms, mutations, and progressive navigation compose through the same Rust component model instead of template glue.InteractivityAdd interactivity without giving up native SSR.Keep the page as server-rendered HTML, then opt specific controls into client behavior with typed signals and event handlers. Proa compiles only the moving pieces into JavaScript.RSJS islandsUse signal(...), bind_value, typed events, and named handlers in Rust. The compiler lowers the client behavior.Tiny per-island JavaScriptEach hydrated RSJS island emits a small vanilla-JS module plus seed state, served with a shared runtime around 1.3 KB gzipped.AdoptionKeep the stack you already have. Move one route first.Go Axum-native for Proa routing and responses, or call Proa over FFI from Node, Go, Python, Ruby, or Java.Run alongside your existing appProxy one route to Proa, leave the rest on Next.js or Rails, then compare latency and cost in production.Security by defaultAuto-escaped output, cross-origin request protection, security headers, and fixed-upstream proxying are part of the framework surface.Accessibility at compile timeWCAG and WAI-ARIA checks run during cargo build so common markup defects fail before deploy.