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 a Consul KV toolkit. Everything is MIT-licensed, published to crates.io, and battle-tested on real workloads.
native
// the crates
6 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.
Framework-neutral admin panel for Rust
One Resource definition → a complete admin panel: auto CRUD (REST/JSON API + rendered HTML UI), served over Actix Web or Axum, backed by SeaORM (PostgreSQL / MySQL / SQLite) or MongoDB. Ships JWT-cookie auth with role-gating, opt-in per-action RBAC (adminx-rbac), TOTP MFA, and is hardened by default with CSRF tokens and per-account rate limiting. Optional add-on crates layer on audit logging (adminx-audit), file attachments with S3 / GCS / Azure backends (adminx-attachments + adminx-cloud), and full-text search (adminx-search) — plus list filters, custom actions, CSV/JSON export, and a seeding + admin CLI.
cargo add adminx --features axum,seaormDetails Lightweight job queue & task scheduler
Production-ready background jobs for Rust on Redis + Tokio. The core is web-framework agnostic; the optional dashboard works with either Actix Web or Axum. Integrated or separate worker modes, cron scheduling, delayed jobs, retries with backoff, and a built-in metrics UI. Lean by default — the CLI and worker binaries live behind a `cli` feature, so embedding qrush as a library pulls in no argument parser or log subscriber.
cargo add qrushDetails Consul KV CLI, REPL & Rust client
A pure-HTTP Consul KV toolkit built from scratch with reqwest — an interactive REPL (like redis-cli, but for Consul), a lightweight HTTP-only client library, typed JSON prefix loading, and key/prefix watches via blocking queries. Clone the client into your Actix or Axum app state for dynamic config and feature flags.
cargo add consulxDetails Searchable models for Rust — Searchkick-style
A searchable-model layer for Rust: make a type searchable, keep its index in sync as records change, and search with real BM25 relevance — over a pluggable backend, with a batteries-included in-memory engine that needs no external service. Rust has excellent search engines (tantivy, meilisearch); searchez is the missing layer above them — the analog of Ruby’s Searchkick.
cargo add searchezDetails Monitor Over Fetch — N+1 detection for Actix
Actix Web middleware + instrumentation that detects N+1 / over-fetch patterns, tracks per-request DB latency, exposes Prometheus metrics, and sends Slack alerts. Works with MongoDB (command events) and SQLx (tracing spans). Inspired by Ruby’s bullet gem.
cargo add moniof --features mongodb,sqlxDetails Cots.ai agent-governance SDK for Rust
The Cots.ai SDK for Rust. Configure an AgentClient once with your tenant_id / agent_id, then guard() every governed action through the interceptor (PEP/PDP) before it runs: allowed executes now, blocked never runs, and require_approval holds until a human decides. Framework-agnostic (reqwest + tokio only) — drop it into actix-web, axum, or a bare worker. Mirrors the @cots/sample Node SDK field for field.
cargo add cotsDetails 
// about me
I write the boring, load-bearing infrastructure
I'm Sandeep 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.