Provides foundational building blocks such as objects, actions, permissions, workflows, an admin interface, and an MCP server
hq — Next.js Admin dashboard Template
By aiwah-labs
HQ is an open-source template from Aiwah Labs for self-hosted business infrastructure, combining objects, actions, permissions, workflows, an admin interface, and an MCP server so teams and AI agents can collaborate in the same system. The README explicitly marks it as an early preview, not yet production-ready, with APIs subject to change.
Explore the design
Compare the page layouts and mobile experience. Open any screenshot for a closer look.
Actual screenshot captured by the server browser.
All pages & views 3
Screenshots show visual appearance; interactive behavior may differ.
What stands out
A quick read of the recorded project description.
Includes two runnable example modules, CRM and Projects/Tasks, rather than placeholder code
Can connect to MCP clients such as Claude Desktop, Cursor, and OpenClaw via MCP configuration
Permissions distinguish between human roles and agent scopes, and high-risk actions require human confirmation before execution
Supports self-hosted deployment, with data stored in your own database and logic in your own codebase
The README explicitly marks it as an early preview, with APIs subject to change, and does not recommend production use
Template Details
HQ is a self-hosted business infrastructure template positioned as an operating system for teams and AI agents to work together. It provides foundational capabilities such as objects, actions, permissions, workflows, an admin interface (Workshop), and an MCP server, along with two runnable example modules, CRM and Projects/Tasks, for users to read, copy, or delete. The README's suggested usage is to clone the repository and hand it to a coding agent to adapt to your own business, with data stored in your own database and business logic kept in your own codebase.
Regarding the tech stack and runtime environment, the README requires Node 22, pnpm 10, and Docker. After starting locally, access it at http://localhost:3002 and log in with [email protected] / password. The repository also provides commands such as pnpm doctor to check the environment, pnpm db:studio to browse the database, and pnpm mcp to start the MCP server. For deployment, it provides setup-server.sh, first-deploy.sh, and setup-nginx.sh scripts, and requires filling in DATABASE_URL, SESSION_SECRET, and INTERNAL_API_SECRET in .env.prod.
It is particularly important to note that the README states at the outset that this is an early preview, not suitable for production, and that APIs will change, and recommends following releases. The documentation does not provide information on performance, concurrency, security audits, or long-term maintenance commitments, nor does it list specific dependency versions, so these aspects cannot be judged from the available materials.
Is it right for your project?
Use Cases
- Teams that want to build internal business systems in a self-hosted manner while retaining control over data and code
- Scenarios where AI agents need to access their own business data and actions via MCP
- Developers who want to quickly adapt existing example modules (CRM, Projects/Tasks) into their own business modules
- Needs to orchestrate repetitive operations into workflows that run on a schedule, on events, or on demand
- Processes that require setting separate permissions for people and agents, and adding human approval for high-risk operations
Suitable For
- Developers with experience using Node, pnpm, and Docker who are willing to deploy and maintain it themselves
- Technical teams planning to hand the repository to a coding agent for secondary development
- Users who need to evaluate an early preview project and can accept the risk of API changes
- Engineers who want to reference the CRM and Projects/Tasks examples to design their own module structures
Getting started & customization
Use these recorded setup notes alongside the repository instructions for your chosen version.
- 1
The local environment requires Node 22, pnpm 10, and Docker
- 2
After cloning the repository, run pnpm install, pnpm db:local:bootstrap, and pnpm dev:platform in sequence, then access http://localhost:3002 and log in with [email protected] / password
- 3
You can use pnpm doctor to check the environment, pnpm db:studio to browse the database, and pnpm mcp to start the MCP server
- 4
For deployment, first run setup-server.sh, then clone to /opt/hq, copy .env.example to .env.prod and fill in DATABASE_URL, SESSION_SECRET, and INTERNAL_API_SECRET, then run first-deploy.sh and setup-nginx.sh
- 5
The README states that the project is an early preview, not yet production-ready, and that APIs will change; before deploying, follow releases and DEPLOY.md
License & source material
Usage conditions & limitations
Free to use · keep license noticeThis entry covers the free version under the MIT license in the public repository; the free scope is the code of that version and does not mean external services or third-party assets are free.
Must comply with when using
- You may use, modify, commercialize, and distribute the code of this version for free.
- When distributing copies or substantial portions of the code, retain the original author's copyright notice and the full MIT license notice.
- The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.
Additional costs & items to verify
- Demo images, fonts, icons, and other third-party assets must be checked against their respective licenses and cannot be judged solely by the code's MIT license.
- External services such as domains, hosting, databases, payments, or AI may incur separate charges.
- The README explicitly states that this is an early preview version, not yet production-ready, and that APIs will change, so it is not suitable for direct production use.
- Running locally requires Node 22, pnpm 10, and Docker to be installed in advance; it cannot start if the environment does not meet these requirements.
- The default local login credentials are [email protected] / password, intended only for the development environment, and must be changed before deployment.
- When connecting to an MCP client, you need to provide the MCP_BOT_API_KEY environment variable yourself.
- Before production deployment, you must fill in configurations such as DATABASE_URL, SESSION_SECRET, and INTERNAL_API_SECRET in .env.prod.
View Original Text Basis
Permission is hereby granted, free of charge
Original License Text
> **Early preview.** Not production ready. APIs will change. [Watch releases](https://github.com/aiwah-labs/hq/releases).
Original README
You'll need Node 22, pnpm 10, and Docker.
Original README
Open http://localhost:3002 and log in with `[email protected]` / `password`.
Original README
"env": { "MCP_BOT_API_KEY": "your-key" }
Original README
https://github.com/aiwah-labs/hq/blob/main/LICENSEhttps://github.com/aiwah-labs/hq/blob/main/README.md# Fill in DATABASE_URL, SESSION_SECRET, INTERNAL_API_SECRET
Original README
Compiled by DeepSeek based on repository license and README ·2026-10-14. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.
Project checks & description sources
Template Information
- Source platforms
- GitHub
- Documentation and maintenance reference score
- More documented · 88 / 100
- Technologies
- Next.js · React
- Website type
- Admin dashboard · Starter
How this score is calculated
Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.
What to verify for this project
- Repository update recorded
- 2026-04-20
- Screenshot last checked
- 2026-10-14
A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.
The catalog identifies Next.js as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.
Use a selection guide →How this description was prepared
AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.
Review declaration: codex-user-requested-batch-review-20261015 · 2026-10-15
Inspect the recorded source material
SHA-256: 71464c846df05df56188bb9e58932e27950fb22cf7118e7a9961d03375dd71f2
2026-10-14T17:10:16.867Z
Source file / repository<p align="center"> <img src="./docs/assets/hq-banner.png" alt="HQ — the operating system where your team and your AI agents work together" width="100%"> </p> # HQ > **Early preview.** Not production ready. APIs will change. [Watch releases](https://github.com/aiwah-labs/hq/releases). **The operating system where your team and your AI agents work together.** HQ is a template for self-hosted business infrastructure. Clone it, hand it to a coding agent, and shape it to what your business does. Your data stays in your database. Your logic lives in your codebase. [Quick start](#quick-start) · [The platform](#the-platform) · [Connect your agents](#connect-your-agents) · [Docs](./docs) · [Deploy](./DEPLOY.md) --- ## Quick start You'll need Node 22, pnpm 10, and Docker. ```bash git clone https://github.com/aiwah-labs/hq cd hq pnpm install pnpm db:local:bootstrap pnpm dev:platform ``` Open http://localhost:3002 and log in with `[email protected]` / `password`. ```bash pnpm doctor # check your setup pnpm db:studio # browse the database pnpm mcp # run the MCP server ``` --- ## The platform HQ gives you the pieces you'd build anyway — objects, actions, permissions, workflows, an admin UI, and an MCP server — so you can skip the first three months and get to the work only you can do. **Objects** are the things your business runs on. Contacts, deals, projects, whatever it is you track. Define the shape once and every part of the platform picks it up: the API, the admin UI, the agents. **Actions** are what happens to those objects. A human clicking a button, an agent calling a tool, a workflow step — they all hit the same code path with the same permissions. You write the action once. You don't write it again for each caller. **Agents** are the AI that works inside the system. They have access to your data, your actions, and your team's context. They answer messages, react to events, run on a schedule, or show up as a step in a workflow. **Workflows** chain actions together. You define them in code. They run on a schedule, on an event, or on demand. They handle the repetitive stuff nobody should have to think about. **Workshop** is where your team works from. One place for records, workflow runs, agent activity, and things waiting for approval. **MCP** is the door from the outside. Claude Desktop, Cursor, OpenClaw — any MCP client gets typed access to your actions and data. No extra plumbing. **Permissions** decide who can do what. People have roles. Agents have scopes. High-risk actions wait for a human to say yes before they run. --- ## Connect your agents ```json { "mcpServers": { "hq": { "command": "node", "args": ["/path/to/hq/apps/mcp/dist/server.js"], "env": { "MCP_BOT_API_KEY": "your-key" } } } } ``` Drop that into Claude Desktop, OpenClaw, Hermes, or any other MCP client. Your actions show up automatically. --- ## Build your domain HQ ships with two example modules — a CRM and Projects/Tasks. Real working code, not stubs. Read them, copy what's useful, delete the rest. - [Add an object](./docs/add-object.md) - [Add an action](./docs/add-action.md) - [Add a workflow](./docs/add-workflow.md) - [Add an agent](./docs/add-agent.md) - [Build a full module](./docs/example-modules/README.md) --- ## Deploy ```bash curl -fsSL https://raw.githubusercontent.com/aiwah-labs/hq/main/scripts/setup-server.sh | bash git clone https://github.com/aiwah-labs/hq /opt/hq cd /opt/hq && cp .env.example .env.prod # Fill in DATABASE_URL, SESSION_SECRET, INTERNAL_API_SECRET bash scripts/first-deploy.sh && bash scripts/setup-nginx.sh your-domain.com ``` Full guide in [DEPLOY.md](./DEPLOY.md). --- ## Contributing Issues and PRs welcome. See [CONTRIBUTING.md](./CONTRIBUTING.md). Security issues in [SECURITY.md](./SECURITY.md). --- MIT · Built by [Aiwah Labs](https://aiwahlabs.com) · Questions? [[email protected]](mailto:[email protected])
Explore similar templates
Compare previews and descriptions within the same stack and category.

Next.js SaaS Starter
The official Next.js SaaS starter template, integrating email/password authentication, Stripe Checkout subscriptions, a dashboard with user/team CRUD, basic Owner/Member RBAC, and activity logging.
Next.js · SaaS

Next.js Commerce
Vercel's officially maintained Next.js App Router ecommerce starter with deep Shopify integration, offering a complete product catalog, cart, and checkout flow. Core logic is modular for swapping backends, and community provider versions exist for BigCommerce, Medusa, and Saleor.
Next.js · E-commerce

Next-js-Boilerplate
A developer-first Next.js 16 starter with Tailwind CSS 4 and TypeScript, supporting both App Router and Page Router.
Next.js · Starter

tailwind-nextjs-starter-blog
A Next.js and Tailwind CSS blog starter template using Contentlayer for Markdown/MDX, with built-in SEO, code highlighting, and tags. It targets personal technical blogs and migration from Jekyll/Hugo to React, and supports one-click Vercel deployment.
Next.js · Blog

next-forge
next-forge is a Turborepo-based Next.js template maintained by Vercel, positioned as a starting point for SaaS products.
Next.js · Starter

SaaS-Boilerplate
SaaS-Boilerplate is an open-source SaaS starter template built with Next.js App Router, React 19, TypeScript, Tailwind CSS, and Shadcn UI.
Next.js · SaaS
