---
title: Compared with other tools
description: Sluurp beside web frameworks, backends, site generators and Vite, and what it took from each.
section: Get started
order: 6
---

# 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.js | Astro | Fresh | SolidStart | Sluurp |
|---|---|---|---|---|---|
| Runs on | Node | Node, and others | Deno | Node, and others | Bun, inside one binary |
| Pages rendered on the server | Yes | Yes | Yes | Yes | Yes (`routes/*.tsx`, Markdown) |
| JavaScript only where needed | Server components | Islands | Islands | No, the whole app hydrates | Islands |
| UI library | React | Any | Preact | Solid | React or Solid, on one signals core ([Twist](/docs/twist)) |
| Server functions (`"use server"`) | Yes | Actions | No | Yes | Yes |
| Form actions without JavaScript | Yes | Yes | Yes | Yes | Yes |
| Answer and page in one trip | Yes | No | No | Yes (single flight) | Yes |
| Preloading on hover | Yes | Yes (opt in) | No | Yes | Yes |
| A database, sign-in, files, jobs | Bring your own | Bring your own | Bring your own | Bring your own | Built in |
| Build step | Required | Required | None | Required | None |

**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

| | Supabase | PocketBase | Firebase | Sluurp |
|---|---|---|---|---|
| Database | Postgres | SQLite | Document store | SQLite |
| Runs as | Many services | One binary | A hosted service | One binary |
| Access rules | Row-level security in SQL | Rule expressions | Security rules | Rule expressions, compiled to SQL |
| Server code | Edge functions (Deno) | JavaScript hooks | Cloud Functions | Functions, hooks, jobs and agents, on Bun |
| Live updates | Yes | Yes | Yes | Yes, with lists answered in the browser |
| History of every change | No | No | No | Yes (`AS OF`) |
| Frontend and admin | Studio | Admin | Console | Admin, UI kit, pages |
| Self-hosted | Yes, with effort | Yes, easily | No | Yes, 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

| | Jekyll | Hugo | Docusaurus | Starlight | Sluurp |
|---|---|---|---|---|---|
| Written in | Ruby | Go | Node, React | Node, Astro | Rust and TypeScript |
| Pages | Markdown, Liquid | Markdown, Go templates | MDX | Markdown, MDX | Markdown, TSX |
| Components in pages | Includes | Shortcodes | React | Astro and any UI | Islands |
| Search | Plugins | Plugins | Algolia or a plugin | Built in (Pagefind) | Built in |
| Sitemap and feeds | Plugins | Built in | Plugins | Sitemap built in | Built in |
| Drafts, redirects, 404 page | Yes | Yes | Yes | Yes | Yes |
| Versioned docs, i18n | Plugins | i18n built in | Both built in | i18n built in | i18n built in |
| Dynamic pages beside static ones | No | No | No | No | Yes |
| Export to plain files | The only way | The only way | The only way | The only way | `sluurp 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](/docs/server-components#markdown-pages), and it makes `/llms.txt` for AI readers.

## Vite

| | Vite | Sluurp |
|---|---|---|
| Dev server | Yes | Yes, the same server that runs production |
| Hot reload | Module swaps (HMR) | Module swaps, and server pages redrawn in place |
| TypeScript and JSX | esbuild or SWC | Bun |
| CSS | PostCSS; Tailwind as a plugin | Tailwind built in |
| Production build | Rollup or Rolldown | Bun's bundler, when the server starts |
| Plugins | Hundreds | [Plugins](/docs/plugins) for features and file types, from a registry |
| Install | Node and npm | One 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.
