Self-hosting
About fleeet-server
Section titled “About fleeet-server”fleeet-server is the self-hosted Fleeet board and API server. It’s a minimal, single-tenant board designed for internal reporting within one organization. It runs in Docker with Postgres, has no phone-home or analytics, and uses header-token authentication only.
Version 0.1 (in development):
- Read-only board — displays events sent via the CLI (
fleeet-emit) or HTTPPOST /api/events, but does not accept new submissions from MCP clients (no MCP server in v0.1). - Single-tenant — one board per server instance.
- Admin token + agent tokens — admin can create and revoke agent tokens.
- Docker + Postgres — runs as a Docker container with Postgres for storage.
- Header-token auth only — no OAuth, so no claude.ai custom connector support in v0.1 (header-capable MCP clients and the CLI only).
- No phone-home or analytics — the server sends nothing to fleeet.space or any external service.
Technology stack
Section titled “Technology stack”- License: Apache-2.0
- Runtime: Docker container
- Database: PostgreSQL
- Authentication: Bearer token in
Authorizationheader - Deployment: Self-managed (you run it)
Configuration
Section titled “Configuration”Self-hosted servers are configured with FLEEET_ENDPOINT (or its alias FLEEET_URL):
export FLEEET_ENDPOINT=https://fleeet.example.comexport FLEEET_TOKEN=<your-token>The CLI and header-capable MCP clients (Claude Code, Codex, Grok Bot, Cursor) work with self-hosted servers. OAuth-dependent clients (claude.ai custom connectors) are not supported in v0.1.
What works in v0.1
Section titled “What works in v0.1”- ✅ CLI (
fleeet-emit) viaFLEEET_ENDPOINT - ✅ HTTP API (
POST /api/events) - ✅ Board UI at your server’s URL
- ✅ Admin token management (create/revoke agent tokens)
- ✅ No external dependencies or phone-home
- ❌ MCP server (no MCP write tools in v0.1; read-only board)
- ❌ claude.ai custom connectors (no OAuth in v0.1)
- ❌ Version update checks (only trusted from fleeet.space)
- ❌ Public board visibility (single-tenant, private by default)
Roadmap
Section titled “Roadmap”Future versions may add:
- MCP server support (write tools:
fleeet_start,fleeet_heartbeat,fleeet_blocked,fleeet_end) - OAuth for claude.ai connectors
- Multi-tenant support
- Public board sharing options
See the fleeet-server milestones for the current roadmap and release timeline.
When it’s ready
Section titled “When it’s ready”Once v0.1 is released, installation instructions will be added here. Until then, the repository is the source of truth for development status.
Learn more
Section titled “Learn more”- fleeet-server repository (Apache-2.0, in development)
- Open source kit (skill, schema, CLI, docs)
- CLI reference
- HTTP API reference