Runable vs Nuxt

Runable and Nuxt both provide a structured Vue experience. Their main difference is who owns the server.

The difference in one sentence

Nuxt provides a complete application around Nitro. Runable adds a Vue application to a backend that you choose and operate yourself.

Nuxt                          Runable
┌──────────────────────┐      ┌───────────────────────────────┐
│ Vue application      │      │ Your backend                  │
│ Nuxt                 │      │ Express, Fastify, Hono…       │
│ Nitro                │      │ └─ Runable ─ Vue application  │
└──────────────────────┘      └───────────────────────────────┘

Quick comparison

Features with the same name do not guarantee identical APIs. Always check the Runable reference before reusing Nuxt code.

Choose Nuxt

Choose Nuxt when you want an integrated solution and Nitro fits your architecture.

Nuxt is generally a better fit when:

Choose Runable

Choose Runable when the backend is a foundational decision that must not be replaced.

Runable is generally a better fit when:

What changes in server code

With Runable, you own the HTTP entry point:

// server.ts
import Express from "express";
import { express } from "runable/adapters/express";

const server = Express();

server.get("/api/users", usersController);
server.use(express());

server.listen(3000);

You decide middleware order, API routes, observability, and server startup. The adapter initializes Runable and handles requests that reach it.

What remains familiar

A Nuxt developer will recognize several conventions:

Decide quickly