Introduction
What fikadesk is and how these docs are laid out.
fikadesk is a support inbox your team owns. Email and chat land in one shared list, assigned to people and teams. A website messenger, a help center and an AI agent sit on top of the same data.
Run it on your own hardware under AGPL-3.0, or start on a managed cell. The same image serves both, so the configuration and the API in these docs describe the self-hosted deployment directly.
Start here
- Self-host in under 10 minutes if you have a box and Docker. This is the fastest way to a working inbox.
- Configuration reference when you want to read every
FIKADESK_*variable and what leaving it unset means. - API authentication when you are ready to build against the REST API.
What is in scope
Everything in these docs runs today, with two exceptions called out where they appear: attachments need a storage origin that is still being built, and the MCP server is specified but not yet shipped. Features in private alpha can move, so pin to a release tag if you depend on one.
Note
fikadesk is in private alpha. The managed cloud is provisioned by hand and the product is not ready for real customers yet. These docs describe the self-hosted image, which is the reference deployment.