What is inboard

inboard is a unified AI workspace for finance and strategy teams. It combines document collaboration, database querying, and AI agents in a single platform that keeps your data under your control.

Components

inboard has three components:

1. inboard app — a desktop application for macOS, Windows, and Linux. All documents are stored locally on user machines. The server never stores document content.
2. Concourse — the backend server, distributed as a Docker container. It handles authentication, user management, extensions, query dispatch, and audit logging.
3. Relay — an on-premises agent that bridges corporate databases to Concourse. It connects outbound only, so no firewall holes are required.

Deployment models

Model	Description
Managed	inboard hosts Concourse for you. You run relays on-prem to connect databases.
Self-hosted	You run Concourse, relays, and the full stack in your own infrastructure.
Hybrid	A future model combining managed and self-hosted components.

Key design principles

• Local-first documents. The server manages access control and real-time sync but never stores document content.
• Outbound-only relay. The relay connects to Concourse over HTTPS. No inbound firewall rules needed on your database network.
• No credential storage. Concourse never stores database credentials. The relay holds them locally.
• No TLS termination. Concourse serves plain HTTP on a single port. Place it behind a reverse proxy (nginx, Caddy, or a cloud load balancer) for HTTPS.

Next steps

• Architecture — understand how the components interact.
• System Requirements — what you need before deploying.
• Concourse Deployment — get Concourse running in minutes.