---
title: "SaaS Microservices"
description: "A SaaS dashboard that talks to 2 API microservices defined in Nitro and Hono, all running under the same domain."
url: "https://vercel.com/templates/next.js/saas-microservices"
links:
  repository: "https://github.com/vercel/examples/tree/main/microfrontends/saas-microservices"
  demo: "https://saas-microservices-dashboard.vercel.app/"
  deploy: "https://vercel.com/new/clone?demo-title=SaaS+Microservices&demo-description=A+SaaS+dashboard+that+talks+to+2+API+microservices+defined+in+Nitro+and+Hono%2C+all+running+under+the+same+domain.&demo-url=https%3A%2F%2Fsaas-microservices-dashboard.vercel.app%2F&demo-image=%2F%2Fimages.ctfassets.net%2Fe5382hct74si%2F6ZaOIxsZSx9wPCzsIk7BM4%2F2aa6badf3e82121e2638a7b2980e68ee%2FScreenshot_2025-08-13_at_3.38.52%C3%A2__PM.png&project-name=SaaS+Microservices&repository-name=saas-microservices&repository-url=https%3A%2F%2Fgithub.com%2Fvercel%2Fexamples%2Ftree%2Fmain%2Fmicrofrontends%2Fsaas-microservices&from=templates&skippable-integrations=1&monorepo=1&root-directories=apps%2Fdashboard%2Capps%2Fapi&project-names=saas-microservices-dashboard%2Csaas-microservices-api&microfrontends=1"
---

# SaaS Microservices

A SaaS dashboard that talks to 2 API microservices defined in Nitro and Hono, all running under the same domain.

# SaaS Microservices

This is an example SaaS project with 2 API services defined as microservices.

## Getting Started

```sh
pnpm install
pnpm dev
```

Open http://localhost:3024 to view the dashboard. The dashboard will make API calls
to the `api` service for the information to display in the dashboard.

## How It Works

There are 2 separate applications in this example:

- `dashboard` - A [Next.js](https://nextjs.org/) application to show the UI. This application also controls the `microfrontends.json` configuration to route API paths to the other microservices (see below).
- `api` - An [Express.js](https://expressjs.com/) backend serving data displayed in the dashboard.

These all run under the same domain. Paths to each application are routed using Vercel's [microfrontends](https://vercel.com/docs/microfrontends) support:

```mermaid
graph TD
    Request --> Vercel{Vercel}

    Vercel -->|"/api/*"| Api[api]
    Vercel -->|"Everything else"| DashboardApp[Dashboard]
```

## Running Locally

To run all applications together, run:

```sh
pnpm dev
```

A [local development proxy](https://vercel.com/docs/microfrontends/local-development) is automatically run to stitch requests from each application to the local instance of each service.

A single or subset of applications can also be run:

```sh
pnpm dev:dashboard
pnpm dev:api
pnpm turbo run dev -F api -F dashboard
```

## Related Templates

### [Express.js on Vercel](https://vercel.com/templates/other/express-js-on-vercel)

Simple Express.js + Vercel example that serves html content, JSON data and simulates an API route.

### [Next.js Multi-Zones Starter](https://vercel.com/templates/next.js/microfrontends-multi-zones)

Split a single Next.js application by path into multiple applications for faster build times and independent development.

---

## Additional documentation

The [Vercel Knowledge Base](https://vercel.com/kb) contains guides and answers to common questions about Vercel, including deployment, framework configuration, domains, caching, and troubleshooting.