Build and run Dashloom
Dashloom is an open-source AI product intelligence platform. Its data layer establishes trustworthy facts; specialized agents explain change, recommend action, and prepare recurring reports.
Local development
npm install
npm run devOpen the local address shown by the development server. The public product page currently uses fictional demonstration data.
Database schema
npm run db:migrate:localThe migrations define workspaces, products, connectors, metrics, competitors, client portals, AI providers and skills, analysis runs, usage events, subscriptions, reports, and retryable deliveries. Production credentials are never stored in source configuration.
Dashboard and agent presets
Dashloom defines Indie Hacker, SaaS Revenue, SEO Growth, Cloudflare Operations, and Agency Client dashboards. Each view is paired with a specialized agent while sharing the same normalized workspace data.
Community AI configuration
Community deployments can configure a server-side OpenAI-compatible endpoint, encrypted API key, and model selection. Managed Cloud usage is recorded separately and enforced by server-owned plan entitlements.
Cloudflare Queues
Connect approximate realtime backlog and paused-delivery evidence with a Queues Read token. Follow the least-privilege setup guide.
Public guides
Cloudflare Analytics · Cloudflare Pages · Google Cloud · Stripe revenue · Lemon Squeezy revenue · Creem revenue · Polar revenue · Paddle Billing revenue · Supabase operations · GitHub activity · Vercel deployments · Custom REST metrics · Agent Playbooks · Agent Signal Radar · Agent conversations and product scope · Agent Growth Missions · Agent Quality Lab · Extension Marketplace · Connector SDK · Agent Skills · Agency portals
Bing Webmaster
Connect a user-level API key to discover verified sites and synchronize Bing search evidence. Follow the Bing Webmaster setup guide.
Trust boundary
LLMs receive bounded evidence assembled from deterministic calculations. Imported text cannot change agent instructions, and important findings retain their metric, period, source, and freshness provenance.
Before serving users, set independent secrets, configure provider credentials, apply every D1 migration to the intended remote database, verify the resulting tables, and test OAuth, email, billing webhooks, report delivery, and recovery in that environment.