01 / EXPLORE THE BUILDING BLOCKS
Rullst Showcase
A blog and application showcase. Explore server-rendered pages and selected integration demonstrations.
Explore ShowcaseThe open-source Rust framework suite
Rullst.
Intelligent. Security-Conscious.
Designed for Effortless Productivity.
Because With Rullst, We Rule! Go beyond the endpoint. Bring your data, identity, AI and product workflows together—with one coordinated toolchain and Rust you can actually inspect.
Axum + Tokio + Tower + SQLx. Your code. Your application policy.
YOUR IDEA. A CONNECTED TOOLKIT.
Your dataModels → queries
Your boundariesIdentity + policy
Your intelligenceLocal + cloud AI
# 13.0 is a prerelease, so name the version
$ cargo install cargo-rullst --version =13.0.0-alpha.4 --locked# Then choose the Blank, API or SaaS starter
$ cargo rullst new my_appSee what comes next
├─ src/controllers/ your routes
├─ src/models/ your data
├─ src/pages/ your interface
└─ Rullst.toml your choices
$ cd my_app
$ cargo rullst dev
EDIT→BUILD→RESTART→REFRESH
Workflow illustration · SaaS starter layout · timings depend on your project
Generated code.
Not a black box.
BUILT ON FAMILIAR GROUND
AxumTokioTowerSQLx
Keep your escape hatches ↗
00 / Less imagining. More exploring.
Not just a framework.
A suite to bring your ideas to life.
Explore three independently deployed applications on Azure Container Apps. Follow the source, discover a starting point, then make it yours.
02 / MAKE ROOM FOR LEARNING
LMS Academy
Discover a learning-platform example, with a public course catalog and account entry points.
Explore the LMS03 / PUT YOUR WORK OUT THERE
Developer Portfolio
A portfolio starting point for presenting projects, skills and experience in a focused web application.
Explore PortfolioPublic demos, not production certifications. Each demo is upgraded on its own schedule and can run an earlier Rullst release than 13.0.0-alpha.4; Showcase payment fixtures are not live checkout. Use test data, not sensitive information. Availability is managed separately.
Source & deployment recipes ↗01 / More than a collection of crates
Less assembly.
More possibility.
Start with a product-shaped foundation. Keep the freedom to understand and change what happens underneath.
A starting point.
Not a starting problem.
Start from the Blank, API or SaaS starter, or copy a complete LMS, ERP, portfolio or blog example. Generate ordinary Rust, follow a coordinated development loop and inspect your application with local tools.
BlankAPISaaS
Find your starting point ↗
Keep trust boundaries visible.
Combine sessions, ownership guards, secure headers, CSRF and bounded request defenses. Your application still owns authorization and deployment policy.
Read the security model ↗Local or cloud.
One guarded client.
Named providers and capability-declared OpenAI-compatible endpoints, with offline fixtures, resource limits and explicit tool permissions.
Explore the provider boundaries ↗BUILT TO BE UNDERSTOOD
Why choose Rullst? ↗
Great tools should make you more capable.
Typed APIs, generated source, architecture rules and worked tutorials give humans and coding agents a common map. No claim that an AI-generated change is safe just because it compiles.
02 / A coordinated ecosystem
One release train.
Room to build.
Twenty packages, released together at one version. Compose the capabilities your product needs; inspect the feature gates and limits before you enable them.
01
Build & operate
02
Product capabilities
Grouped architecture map, not a dependency graph. The Experimental packages (IoT, Privacy, Supervision, Media and Labs) are optional and not shown; the maturity tiers define what each tier promises.
03 / From your first route to your next idea
Make the workflow
part of the advantage.
Start with a real use case.
Choose a starter and database. Optional persistence adds zero or more specialized capabilities—not a second mandatory database.
Zero to Hero ↗Stay in the loop.
Use supervised rebuild/restart during development. Failed builds retain the running application; successful restarts reset process-local state.
The development contract ↗Evolve deliberately.
Preview framework upgrades, apply backed-up changes and run compiler checks. Review migrations and application behavior before deployment.
Assisted upgrades ↗ THE DEVELOPER CONTROL ROOM cargo rullst dash
04 / Ambitious about the product. Precise about the proof.
Don't take our word.
Follow the evidence.
No invented rankings. No universal-fastest claim. No green badge presented as a security certification.
01 / CAPABILITIES
What's actually there?
Implementation, incomplete capabilities and roadmap boundaries in one place.
Inspect the status ↗ 02 / V12 RELEASE REVIEWWhat was verified for v12?
Historical record of the end-of-life v12 line: release evidence, corrections, bounded claims and the checks repeated for its stable release.
Open the v12 release audit ↗ 03 / PERFORMANCEWhat did we measure?
Eight benchmark groups, exact workloads and methodology—not a production-throughput promise.
Explore benchmark history ↗Current CI, coverage and OpenSSF evidence are linked from the repository verification dashboard. Results belong to their recorded commits.
Open source. Open invitation.
Your next project.
Our next breakthrough.
Build something. Question an assumption. Bring a reproduction. Improve a tutorial. You don't need a huge pull request to make a meaningful difference.
Explore boldly.
Deploy responsibly.
v13 is in prerelease: 13.0.0-alpha.4 is the 13.0 feature freeze, followed by 13.0.0-rc.1 (fixes and documentation only) and 13.0.0. Cargo never selects a prerelease on its own, so name the exact version from crates.io (=13.0.0-alpha.4) and use its matching immutable tag rather than the moving main branch. The v12 line reached end of life on 16 October 2026 with 12.3.0, and the v12 branch is frozen; move applications with the v12 → v13 adoption guide. The legacy v5 branch is no longer maintained either. Prerelease and stable describe the framework API lifecycle, not automatic approval of an application's authorization, provider configuration, operations or deployment.