Repository navigation
Covan 0.1.0
The first tagged release, and the first one you can actually pull.
git clone https://github.com/covan-ai/covan
cd covan
cp .env.docker.example .env # set OPENAI_API_KEY
docker compose pull
docker compose upBoth images are published for linux/amd64 and linux/arm64:
ghcr.io/covan-ai/covan-api:0.1.0ghcr.io/covan-ai/covan-web:0.1.0
latest and 0.1 point here too; edge follows main. Pin with COVAN_VERSION=0.1.0 in .env.
What Covan is
One agent that knows what your team wrote down. Everyone trains it together and talks to it privately — conversations are isolated per person by Postgres row level security, not by a check in the API. Upload documents, group them into bundles, attach them to an agent, and ask; answers cite the documents they came from, and the citations survive a reload.
What is in this one
- A publishable web image. Vite inlines
VITE_*at build time, which is why there was never an image worth publishing — the bundle carried whoever built it. It is now built against placeholders and configured when the container starts, so one image serves every deployment. - Rate limiting in the API. Two tiers, on by default on both deployment paths, in front of every endpoint that spends money at OpenAI. Previously the only bound was on request size, which caps what one call costs rather than how many arrive.
- Bring your own endpoint.
OPENAI_BASE_URLsends completions to Ollama, vLLM, LiteLLM or OpenRouter. Embeddings and transcription still go to OpenAI —docs/self-hosting.mdsays why, plainly, rather than leaving it to be discovered. - Routines. Scheduled work that runs while nobody is watching, delivered by email or Slack.
- Two runtimes, one source. The same code runs on Cloudflare Workers with R2 and on Node with the filesystem under
docker compose.
What is not promised
The API is unversioned and nothing is promised about compatibility between commits or between this release and the next. Read docs/self-hosting.md before putting it in front of anyone outside your team — in particular the sections on what to change before the stack faces a network, and the two honest limitations of the built-in rate limiter.
One known limitation, documented rather than discovered: a person removed from a workspace keeps their own chat sessions from it. docs/team.md covers that and the rest of what outlives a membership.
Licence
AGPL-3.0-only.