Guide · Deployment and agents

Self-hosted AI project management: a practical setup

Self-hosted AI project management means running the ticket-drafting stack on your own infrastructure, with your own database and credentials. Relay is Apache-2.0, has no feature gates on the open-source path and lets you connect all four trackers and both chat apps. Your data stays in your database.

By the Relay maintainers · Last updated 19 November 2026 · Source on GitHub

Why self-host?

Three reasons come up for small teams: data location, control over credentials and freedom from feature gating. A self-hosted Relay instance keeps notes, drafts and the audit log in a database you manage. Tracker and chat credentials are encrypted per workspace with AES-256-GCM, and a kill switch can halt external writes. Nothing about the tool requires sending your meeting content to a third party beyond the LLM provider you choose to configure.

What does a setup involve?

  1. Clone and install. Use the repository's pinned workspace setup and run pnpm doctor.
  2. Configure. Copy the example environment file and add LLM, tracker and chat credentials.
  3. Migrate. Run pnpm db:migrate, or let the API auto-migrate.
  4. Start the services. Run the API, the outbox worker and a chat app. docker compose up --build starts the stack.
  5. Try it without credentials. pnpm demo runs the full pipeline against a fake tracker.

Are there limits on the self-hosted path?

No artificial ones. Self-hosted Relay has no feature gates, no seat limits and no capture quota. The plan matrix applies only to hosted plans, and its quota layer resolves an unknown or missing plan to self_hosted, which is unlimited. Full Smart Assignment, team memory, the audit log and all four tracker adapters are available in the open-source build. The working conversion path today is self-hosting.

Repository snapshot: 423 tests passing, 86% line coverage. Live chat and tracker smoke checks still need real credentials.

How is data kept portable?

Storage is Postgres with pgvector in production and PGlite for a single-machine trial. There is no proprietary format: pg_dump gives a complete copy. Tenant isolation is built in through workspace IDs and row-level security, with service-layer checks as a second boundary. Every row carries a workspace ID, and writes are attributed to an actor in an append-only, hash-chained audit log.

What is available in a self-hosted install
CapabilitySelf-hosted
TrackersGitHub, Linear, Jira, Notion
Chat appsSlack and Discord
Agent surfaceREST API and MCP server, 28 tools
LimitsNone enforced on the open-source path

Is a hosted service available?

Not yet. Cloud Free and Cloud Pro or Team are planned, not live. Quota enforcement, metering and device login exist in the code, but signup and billing are opt-in per instance, no prices are configured, and the site's waitlist is closed. Do not plan around a managed service today. If you need Relay now, the documented and supported path is the self-hosted stack above.

Next step

Clone the repository, run pnpm demo and inspect the evidence chain on a real note. Then follow the hosting guide for a persistent deployment.


Self-host Relay Read the hosting guide