Open-source dashboard for mobile app growth — deep links, messaging campaigns, revenue tracking, and audience analytics.
Grovs helps mobile developers grow their apps by providing a single dashboard to manage deep links, send targeted push notifications, track revenue, and understand their audience. Self-host it or connect it to the Grovs managed backend.
- Next.js 15 (App Router)
- React 19
- TypeScript 5 (strict mode)
- Tailwind CSS 4
- shadcn/ui (new-york style)
- Node.js 20+
- npm 10+
-
Clone the repository:
git clone https://github.com/grovs-io/dashboard.git cd dashboard -
Install dependencies:
npm install
-
Create your environment file:
cp .env.example .env.local
Fill in the required values (see
.env.examplefor documentation). -
Start the development server:
npm run dev
Open http://localhost:3001.
You can also run the dashboard using Docker:
cp .env.example .env.local
docker compose up --buildThe app will be available at http://localhost:3036. See docker-compose.yml for configuration options.
src/
├── app/ # Next.js App Router pages
│ └── (protected)/ # Auth-required pages
├── api/ # API service functions (async/await)
├── components/
│ ├── ui/ # shadcn/ui primitives
│ ├── layout/ # App chrome (sidebar, header, nav)
│ ├── common/ # Shared utility components
│ └── auth/ # Auth-related components
├── context/ # React Context providers
├── hooks/ # Custom React hooks
├── lib/ # Utilities (API client, storage, helpers)
└── constants/ # App constants
See .env.example for all available configuration options.
Required: NEXT_PUBLIC_API_URL, NEXT_PUBLIC_CLIENT_ID, CLIENT_SECRET
Optional: Firebase, Chatwoot, PostHog, GTM (features gracefully disable when not configured)
| Command | Description |
|---|---|
npm run dev |
Start dev server (port 3001, Turbopack) |
npm run build |
Production build |
npm run lint |
Run ESLint |
npm test |
Run unit tests (Vitest) |
npm run test:watch |
Run tests in watch mode |
npm run test:coverage |
Run tests with coverage report |
npm start |
Start production server |
See CONTRIBUTING.md for development guidelines.
See SECURITY.md for our vulnerability disclosure policy.