Axum + Diesel boilerplatekbve
The KBVE core Rust crate — an Axum and Diesel boilerplate for building backend APIs and micro-services, with auth, Supabase, and gate features.
Link only what you need
Bundles authentication, markdown, wallet, referral, and gate modules behind Cargo feature flags so each service links only what it needs.
- gate / gate-auth — the kbve-gate auth-proxy sidecar.
- supabase / kv — Supabase plus a Valkey-backed KV layer.
What it gives you
Features
Axum + Diesel base
HTTP routing plus async Diesel (diesel-async, bb8 pool) for backend micro-services.
Authentication
Argon2 password hashing and JWT (jsonwebtoken) handling.
supabase / kv
Supabase integration and a Valkey-backed key-value layer via jedi.
gate / gate-auth
An auth-proxy WebSocket surface (the kbve-gate sidecar) fronting services like n8n, Grafana, and Studio.
image-gen, wallet, referral, markdown, lot
Additional optional modules for the KBVE platform.
legacy-sync-db
The older synchronous Diesel modules (guild, models, runes, schema, spellbook).
Questions
Frequently asked
What is the kbve crate?
It is the KBVE core Rust crate — an Axum and Diesel boilerplate that provides shared building blocks for producing backend APIs and micro-services across the KBVE ecosystem.
What features does the kbve crate expose?
Cargo feature flags gate optional capabilities including supabase, kv (Valkey-backed), image-gen, wallet, gate-auth, and gate (an auth-proxy WebSocket surface), plus a legacy-sync-db path for the older Diesel synchronous modules.
What is the kbve gate feature for?
The gate and gate-auth features provide an authentication-proxy surface built on Axum WebSockets and reqwest streaming, used as the kbve-gate sidecar that fronts services such as n8n, Grafana, and Studio.