Skip to main content
BoardPulse AI ships as a set of Docker services that you can have running on a single machine in minutes. This guide walks you through configuring your environment, pulling the AI model, and sending your first query against the built-in demo dataset.
1

Prerequisites (NVIDIA GPU — local models only)

If you plan to run AI inference locally with Ollama, your host machine needs NVIDIA GPU support configured for Docker. Skip this step if you are using the cloud or mock provider instead.
Cloud and mock providers work on any machine with Docker installed — no GPU required.
2

Copy and configure your environment file

Copy the example environment file, then open it and set the variables that control your data source and AI provider.
Key variables to review before starting:
Leave SEED_DEMO_DATA=true and DEFAULT_SOURCE_INCLUDE_TABLES at their defaults to use the built-in demo dataset — no external database needed.
3

Start all services

Use the local-models Docker Compose profile to include the Ollama service alongside the API, admin panel, PostgreSQL, Redis, and Open WebUI.
If you are using the cloud or mock provider and do not need Ollama, omit the profile flag:
Always use up -d rather than restart when changing .env. The restart command does not reload environment variables.
4

Pull the AI model

After the Ollama container is running, download the model. This step is required before the API will return real AI responses when using the local provider.
The download is several gigabytes. Wait for it to complete before sending queries.
5

Access the interfaces

Once all containers are healthy, three interfaces are available:
In Open WebUI, select the boardpulse-executive model from the model selector to route queries through the BoardPulse AI backend.
6

Run your first query

The demo dataset is seeded automatically on startup and contains three tables: sales_orders, invoices, and inventory_items. Send a query using curl or any HTTP client:
A successful response looks like this:
The sql field shows exactly what was executed — nothing runs without passing the SQL guardrail layer first.

Next steps

Connect your database

Replace the demo dataset with your own Supabase, RDS, or on-premise PostgreSQL instance

Configure model providers

Switch from mock to OpenAI or a local Ollama model for real AI responses

SQL guardrails

Understand how BoardPulse AI validates every query before execution

API reference

Full request and response schema for the chat endpoint