DocsAbout
On the shoulders of giants
The open-source projects Sluurp is built on and the work that inspired it. Sluurp would not have been possible without them.
Sluurp is one binary, but very little of it started with us. It stands on years of open-source work by people who shared what they built, and on products whose ideas showed the way. Sluurp would not have been possible without them. Thank you.
What Sluurp is built on
Language and server. Rust, with Tokio for running everything at once, Axum, Hyper, Tower and reqwest for HTTP, Rustls and ring for TLS and cryptography, the RustCrypto crates (AES, SHA, P-256, Argon2 and more), and Serde for every format in between.
JavaScript and TypeScript. Bun hosts Sluurp: it runs server code and React apps, bundles them with hot updates, and is the sluurp bun and sluurp bunx commands. Sluurp’s Rust core runs inside it as a Node-API addon, made with napi-rs. Oxc parses, transforms and checks every file Sluurp serves, and Rolldown bundles npm packages into them. Wasmtime runs WebAssembly.
Data. SQLite, through rusqlite: the database under every app. sqlite-vector searches by meaning. Apache Arrow moves rows to plugins.
Swarms. openraft for agreement between nodes, LTX for the pages they replicate and back up, and rcgen for their certificates. The design learned from dqlite, LiteFS, Litestream, celld, CockroachDB and Docker Swarm.
CSS. Tailwind CSS. Sluurp’s stylesheet engine is a Rust implementation of Tailwind v4, and it is checked against Tailwind’s own tests.
Everything else in the binary. Lettre for mail, git2 for Git, pulldown-cmark for Markdown, the image crate for pictures, Wry and Tao for desktop windows, notify for watching files, tracing for logs, and clap for the command line.
In the browser
The UI kit. Built with React and Base UI, it follows shadcn/ui and Radix in its components and their behaviour, with Lucide icons. It learned from Vaul, Sonner and Embla, and from Apple’s Human Interface Guidelines.
Reactivity and pages. Apps are written in React; Sluurp’s live data and signals (@sluurp/react) owe much to SolidJS and Preact signals. Server components follow React Server Components, and routes and islands are modelled on Fresh. The docs’ try examples compile in the browser with Sucrase.
Charts, documents and words. d3, Recharts as a model, pdfmake, Temml for maths, Pretext for text layout, Rough.js, Hyphen, Natural Earth through world-atlas, and Fontsource.
Ideas we learned from
- PocketBase, Supabase and Firebase: a whole backend that an app just talks to.
- Deno, Vite and Express: how code should be served, run and routed.
- Storybook: stories for every component.
- Shopify’s admin UI extensions: how plugins add to an admin.
- Elasticsearch and Kibana’s query language: search that existing tools can talk to.
- Stripe: payments, and documentation people enjoy reading.
- Bun’s docs: how these pages are laid out and written.
- typia: types turned into checks.
- AdGuard’s filter syntax: outbound rules.
- GSAP, Lottie, Rive and Spline: motion.
- Figma, Webflow, Notion and Linear: what good tools feel like.
- llama.cpp: the reference Sluurp’s embeddings follow, for models like Nomic’s.
How it is tested
Playwright drives the browsers, and axe-core checks every screen for accessibility.
If we use your work and you are missing here, tell us: it is an oversight, and we will fix it.