Back-end Framework for Next.js App Router
One codebase → type-safe clients, OpenAPI, and AI tools
Documentation Quick Start Performance

Vovk.ts

Vovk.ts lets you build a structured back end on top of Next.js App Router Route Handlers. The unit is the procedure — a typed function paired with its schema. From that single source, Vovk derives the HTTP endpoint, the local .fn() call, the type-safe client, the OpenAPI document, and the AI tool with execute. No separate contract layer, no glue code.

Requirements: Node.js 22+ and Next.js 15+

Install to existing Next.js project

npx vovk-cli@latest init

See: https://vovk.dev/quick-install

Why you’d use it

🧩 Stay native to Next.js (routing, streaming, proxy.js/auth patterns, deployment targets)
🏗️ Structured API layer (Controller → Service → Repository) on top of Route Handlers
📝 No separate contract layer — schema is derived from your controller code, not maintained by hand
🤖 Derive AI tools from your API surface (controllers and emitted RPC modules can be exposed as AI tools with parameters + execute)
⚡ Back-end segmentation via segments: split your API into independently configured units that each compile into their own serverless function
✅ Typed request handling via procedure(...) with { params, query, body }
🔗 Mix in third-party OpenAPI schemas as modules that share the same client/tooling pipeline (OpenAPI mixins)

What it looks like

A procedure is a typed, validated callable. Define inputs and output with procedure and call it directly on the server for SSR/PPR, server actions, or AI tool execution:

export default class UserController {
  static getUser = procedure({
    params: z.object({ id: z.string().uuid() }),
  }).handle(async (req, { id }) => {
    return UserService.getUserById(id);
  });
}

const user = await UserController.getUser.fn({ params: { id: '123' } });

Services hold business logic separately. Plain classes, no decorators — types infer from the procedure:

import type { VovkParams } from 'vovk';
import type UserController from './UserController';

export default class UserService {
  static async getUserById(id: VovkParams<typeof UserController.getUser>['id']) {
    // ...
  }
}

Add an HTTP decorator and the same procedure becomes a Next.js Route Handler. Codegen produces a fetch-powered client that mirrors the .fn() signature:

export default class UserController {
  @get('{id}')
  static getUser = procedure({
    params: z.object({ id: z.string().uuid() }),
  }).handle(async (req, { id }) => {
    return UserService.getUserById(id);
  });
}

import { UserRPC, PetstoreAPI } from 'vovk-client';

const user = await UserRPC.getUser({ params: { id: '123' } });
const pet = await PetstoreAPI.getPetById({ params: { petId: 1 } });

Annotate with @operation and procedures expose as LLM tools — pass controllers (in-process) or RPC modules (HTTP) to deriveTools:

const { tools } = deriveTools({ modules: { UserRPC, TaskController, PetstoreAPI } });
console.log(tools); // [{ name, description, parameters, execute }, ...]

What one procedure becomes

Function plus schema is a complete unit. From that pair Vovk derives:

Help us improve

vovk

Component Overview

Component Details

Skills (15)

README

Vovk.ts

Install to existing Next.js project

Why you’d use it

What it looks like

What one procedure becomes

Similar Plugins

orpc-guide

rest-api-generator

nextjs-expert

developer-kit-typescript

Help us improve

vercel

ts-dev-kit