CapixCapabilities, not routes.

Write what your server can do. The framework handles how it's exposed.

🎯

One primitive

Capability — a typed, validated, guardable function. REST, GraphQL, WebSocket, queue, and MCP all invoke the same thing.

🔒

Errors are caught

Throw anything, get a structured HTTP response. No more silent async failures or forgotten try/catch.

⚡

Fast

26,000+ req/s on hello world. Beats Express by ~60%, Hono by 11–19%. Within 6% of Fastify across all scenarios.

🧰

Complete CLI

capix new, generate, dev, list, show, call, check, docs, client — everything you need to build and maintain an API.

The problem with Express

// This bug is silent, common, and hard to debug
app.get('/user/:id', async (req, res) => {
  const user = await db.find(req.params.id); // throws if db is down
  res.json(user);                            // never reached — client hangs
});

The Capix way

const getUser = capability(
  z.object({ id: z.string() }),
  async ({ id }) => {
    const user = await db.find(id); // throws → client gets a clean 500
    if (!user) throw errors.NotFound({ resource: 'user', id }); // → 404
    return user; // returning is responding
  },
  'query',
).guard(mustBeUser); // guards run before the resolver, every time

Get started in 5 minutes →