multitenant

Automate multi-tenant hosting in Next.js with subdomain routing and proxy configuration.

52|Updated Jul 12, 2023
One-click install
npx skills add https://github.com/finom/vovk --skill multitenant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multitenant
Source: https://github.com/finom/vovk/tree/main/packages/claude-plugin/skills/multitenant
Command: npx skills add https://github.com/finom/vovk --skill multitenant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Host multiple tenants from a single Next.js app using subdomain routing, enabling each tenant to have separate backend segments and frontend routes while sharing a single codebase.

Core Features & Use Cases

  • Multi-tenant architecture with per-tenant backend segments, per-tenant frontend pages, and a proxy that wires requests to the correct tenant.
  • DNS wildcard and local development setup to route subdomains to the same app, with a reserved-path guard to prevent root-host conflicts.
  • Changes automation: switch from a single client to segmented clients via vovk.config.mjs and configure per-tenant overrides in the proxy.

Quick Start

Create a tenant segment, configure proxy overrides and segmented client, then run the dev server to verify subdomain-based routing across root, admin, and per-tenant frontends.

Frequently Asked Questions about multitenant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I host multiple tenants from a single Next.js app using subdomain routing?

Subdomain routing is automated by configuring vovk.config.mjs for segmented clients, updating proxy.ts with per-tenant overrides, and creating tenant-specific frontend pages and API segments to host multiple tenants from one Next.js app.

What is multi-tenant architecture with subdomain routing in Next.js?

Multi-tenant architecture via subdomain routing allows a single Next.js app to host multiple tenants, providing each tenant with separate backend segments and frontend routes while sharing a single codebase and proxy wiring.

How do I set up DNS wildcard and local development for subdomain routing?

DNS wildcard and local dev setup route subdomains to the same Next.js app, requiring a reserved-path guard to prevent root-host conflicts across root, admin, and per-tenant frontends during local development and production.

Can I use dynamic and static subdomains for per-tenant backend segments in Next.js?

Yes, you can use dynamic and static subdomains to route requests to per-tenant backend segments and frontend pages, with a proxy wiring requests to the correct tenant based on the subdomain.

Do I need to update vovk.config.mjs to switch from a single client to segmented clients?

Yes, switching to segmented clients requires updating vovk.config.mjs and configuring per-tenant proxy overrides in proxy.ts to ensure the multi-tenant architecture routes requests correctly.