Building the unglamorous pieces every Rust backend needs.
I build production-grade infrastructure crates for Rust — the unglamorous pieces every backend needs: an admin panel, a job queue, database observability, and docs tooling. Everything is MIT-licensed, published to crates.io, and battle-tested on real workloads.
// the crates
Four crates, published in the open
Each one solves a real backend problem, ships with docs, and is available on crates.io under the MIT license.
v0.2.6A modern admin panel framework for Rust
Zero-config CRUD, schema-driven forms, JWT + session auth and RBAC, built on Actix Web and MongoDB with a responsive Tailwind UI.
cargo add adminxDetails 
v0.6.1Lightweight job queue & task scheduler
Production-ready background jobs for Rust on Actix + Redis. Integrated or separate worker modes, cron scheduling, delayed jobs, and a built-in metrics dashboard.
cargo add qrushDetails 
v0.1.0Monitor Over Fetch — N+1 detection for Actix
Actix middleware + instrumentation that detects N+1 / over-fetch patterns, tracks per-request DB latency, exposes Prometheus metrics, and sends Slack alerts. Inspired by Ruby's bullet.
cargo add moniof --features mongodb,sqlxDetails vlatestMarkdown to static documentation
A Rust generator that compiles Markdown into a clean static HTML docs site — split-panel layout, Arch / JSON / Text tabs, multi-language support, and full-text search. No backend, no database.
git clone https://github.com/srotas-space/archDetails // about me
I write the boring, load-bearing infrastructure
I'm SNM Maurya, a systems and backend engineer who spends a lot of time in Rust. Most of my open-source work lives under the srotas-space organization — the pieces I kept re-writing across projects, extracted into crates anyone can use.
The goal is simple: give Rust backends the same batteries-included ergonomics you get in Django, Rails or Laravel — an admin panel, a job queue, database observability, docs tooling — without giving up Rust's speed and safety.
// how I build
A few principles behind the code
Type-safe by default
Rust's type system does the heavy lifting — fewer runtime surprises, safer refactors, and APIs that are hard to misuse.
Production performance
Small memory footprints, sub-millisecond hot paths, and honest benchmarks. Built on Actix Web and tested under load.
Docs that respect you
Every crate ships a real README, docs.rs pages, and runnable examples. Getting started should take minutes, not hours.
Open in the open
MIT licensed, developed on public GitHub, and published to crates.io. Issues, forks and pull requests are always welcome.
Use it, star it, or send a PR
Everything is MIT licensed and developed in the open. Contributions, bug reports and ideas are genuinely welcome.