DocsGet started

Compared with other tools

Sluurp beside web frameworks, backends, site generators and Vite, and what it took from each.

Sluurp is a backend, a web framework, a site generator and a dev server in one binary. Each of those has good tools of its own. This page shows how Sluurp compares with them, where it is weaker, and what it borrowed.

Web frameworks

Next.jsAstroFreshSolidStartSluurp
Runs onNodeNode, and othersDenoNode, and othersBun, inside one binary
Pages rendered on the serverYesYesYesYesYes (routes/*.tsx, Markdown)
JavaScript only where neededServer componentsIslandsIslandsNo, the whole app hydratesIslands
UI libraryReactAnyPreactSolidReact or Solid, on one signals core (Twist)
Server functions ("use server")YesActionsNoYesYes
Form actions without JavaScriptYesYesYesYesYes
Answer and page in one tripYesNoNoYes (single flight)Yes
Preloading on hoverYesYes (opt in)NoYesYes
A database, sign-in, files, jobsBring your ownBring your ownBring your ownBring your ownBuilt in
Build stepRequiredRequiredNoneRequiredNone

Where the others are stronger. Next.js has the largest ecosystem and all of React’s world around it. Astro works with every UI library and has the richest tools for content. Their large communities mean more answers, templates and places to host. Sluurp runs React’s and Solid’s APIs on its own runtime, so a library that leans on React’s internals may not work.

What Sluurp took:

  • From Astro and Fresh: islands, so pages send no JavaScript unless a part needs it; Markdown pages with frontmatter; a layout per folder.
  • From SolidStart: signals that update only what changed, "use server" functions, form actions that answer in a single flight, reads that are never made twice, and preloading on intent.
  • From Next.js: routes from files, with [param] segments, and server components that read data directly.

Backends

SupabasePocketBaseFirebaseSluurp
DatabasePostgresSQLiteDocument storeSQLite
Runs asMany servicesOne binaryA hosted serviceOne binary
Access rulesRow-level security in SQLRule expressionsSecurity rulesRule expressions, compiled to SQL
Server codeEdge functions (Deno)JavaScript hooksCloud FunctionsFunctions, hooks, jobs and agents, on Bun
Live updatesYesYesYesYes, with lists answered in the browser
History of every changeNoNoNoYes (AS OF)
Frontend and adminStudioAdminConsoleAdmin, UI kit, pages
Self-hostedYes, with effortYes, easilyNoYes, easily

Where the others are stronger. Supabase has Postgres, with its extensions, replicas and the scale that comes with them. Firebase has Google’s infrastructure and scales without you thinking about servers. PocketBase is smaller and has been in production longer. Sluurp is in alpha.

What Sluurp took:

  • From PocketBase: one binary, SQLite, rule expressions, and an admin that comes with it.
  • From Supabase: row-level rules enforced in the database’s own queries, and a typed client for every table.

Static site generators

JekyllHugoDocusaurusStarlightSluurp
Written inRubyGoNode, ReactNode, AstroRust and TypeScript
PagesMarkdown, LiquidMarkdown, Go templatesMDXMarkdown, MDXMarkdown, TSX
Components in pagesIncludesShortcodesReactAstro and any UIIslands
SearchPluginsPluginsAlgolia or a pluginBuilt in (Pagefind)Built in
Sitemap and feedsPluginsBuilt inPluginsSitemap built inBuilt in
Drafts, redirects, 404 pageYesYesYesYesYes
Versioned docs, i18nPluginsi18n built inBoth built ini18n built ini18n built in
Dynamic pages beside static onesNoNoNoNoYes
Export to plain filesThe only wayThe only wayThe only wayThe only waysluurp static

Where the others are stronger. Hugo builds thousands of pages in a second and has a theme for everything. Docusaurus has versioned docs and many plugins. Starlight is the most polished docs theme. Sluurp’s docs features are enough for this site, but they are younger.

What Sluurp adds. A docs site on Sluurp can also have sign-in, a database, forms that save and live pages. Its Markdown pages calculate with their frontmatter, and it makes /llms.txt for AI readers.

Vite

ViteSluurp
Dev serverYesYes, the same server that runs production
Hot reloadModule swaps (HMR)Module swaps, and server pages redrawn in place
TypeScript and JSXesbuild or SWCBun
CSSPostCSS; Tailwind as a pluginTailwind built in
Production buildRollup or RolldownBun’s bundler, when the server starts
PluginsHundredsPlugins for features and file types, from a registry
InstallNode and npmOne binary

Where Vite is stronger. Its plugins cover every framework and file type, and nearly every frontend tool supports it.

What Sluurp took. A dev server that is ready in milliseconds, modules served unbundled while you work and bundled only for production, a clear start message and build report, and hot updates that keep the page’s state.

View as Markdown