Skip to main content
Use this guide when you want the current Introd stack running locally with as little guesswork as possible.

Repositories in scope

API

introd-api powers auth, graph services, integrations, extension APIs, and intro workflows.

Dashboard

introd-dashboard is the main product UI for search, setup, and introductions.

Chrome extension

introd-extension handles LinkedIn sync and in-page relationship context.

Docs

introd-docs is the Mintlify portal that publishes to docs.getintrod.ai.

Boot order

Start the stack in this order so the product surfaces can find each other cleanly:
  1. API service
  2. dashboard
  3. extension build
  4. docs preview
  5. optional graph-intel service for TrustRank and pathfinding work

API service

Install dependencies and run the backend from introd-api:
npm ci
cp .env.example .env
npm run dev
Use non-production credentials locally. Keep DISABLE_VITE=true for API-only runs so the backend does not attempt to serve the retired bundled frontend.

Run each surface

cd introd-api
npm ci
cp .env.example .env
npm run dev
The API defaults to http://localhost:5000 and exposes the main health probes used by the dashboard and docs examples.

Health checks

The main readiness endpoints are:
GET /health/live
GET /health/ready
GET /health/status

Graph intelligence service

Run the Python TrustRank and pathfinding service separately:
cd graph-intel
pip install -r requirements.txt
uvicorn app.main:app --reload --port 8000
The graph service powers TrustRank, pathfinding, and network search. Keep all graph queries tenant-scoped and evidence-backed.

Validation pass

Before shipping backend changes:
npm run check
npm run graph-intel:test
Before shipping docs changes:
npx mintlify validate