base on A full-stack Next.js app with multi-tenancy. # Next.js Multi-Tenant Example A production-ready example of a multi-tenant application built with Next.js 15, featuring custom subdomains for each tenant. ## Features - ✅ Custom subdomain routing with Next.js middleware - ✅ Tenant-specific content and pages - ✅ Shared components and layouts across tenants - ✅ Redis for tenant data storage - ✅ Admin interface for managing tenants - ✅ Emoji support for tenant branding - ✅ Support for local development with subdomains - ✅ Compatible with Vercel preview deployments ## Tech Stack - [Next.js 15](https://nextjs.org/) with App Router - [React 19](https://react.dev/) - [Upstash Redis](https://upstash.com/) for data storage - [Tailwind 4](https://tailwindcss.com/) for styling - [shadcn/ui](https://ui.shadcn.com/) for the design system ## Getting Started ### Prerequisites - Node.js 18.17.0 or later - pnpm (recommended) or npm/yarn - Upstash Redis account (for production) ### Installation 1. Clone the repository: ```bash git clone https://github.com/vercel/platforms.git cd platforms ``` 2. Install dependencies: ```bash pnpm install ``` 3. Set up environment variables: Create a `.env.local` file in the root directory with: ``` KV_REST_API_URL=your_redis_url KV_REST_API_TOKEN=your_redis_token ``` 4. Start the development server: ```bash pnpm dev ``` 5. Access the application: - Main site: http://localhost:3000 - Admin panel: http://localhost:3000/admin - Tenants: http://[tenant-name].localhost:3000 ## Multi-Tenant Architecture This application demonstrates a subdomain-based multi-tenant architecture where: - Each tenant gets their own subdomain (`tenant.yourdomain.com`) - The middleware handles routing requests to the correct tenant - Tenant data is stored in Redis using a `subdomain:{name}` key pattern - The main domain hosts the landing page and admin interface - Subdomains are dynamically mapped to tenant-specific content The middleware (`middleware.ts`) intelligently detects subdomains across various environments (local development, production, and Vercel preview deployments). ## Deployment This application is designed to be deployed on Vercel. To deploy: 1. Push your repository to GitHub 2. Connect your repository to Vercel 3. Configure environment variables 4. Deploy For custom domains, make sure to: 1. Add your root domain to Vercel 2. Set up a wildcard DNS record (`*.yourdomain.com`) on Vercel ", Assign "at most 3 tags" to the expected json: {"id":"999","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"