A Blueprint in the repository
It declares the server, managed Postgres, a disk for uploads and generated secrets. New → Blueprint → the repo → Apply, then open the URL and create the owner. Five clicks to a first room.
Render guideSelf-host
Your server, your rules.
Free, with no limits.
Fabrikka is one container image with everything in it: the web app, the API and the MCP endpoint. Add Postgres and a domain, and you have the same product we host, with nothing held back.
Any server with Docker
The compose file brings the server, Postgres 17 and Caddy with automatic HTTPS. The init script generates every secret, so there is nothing to invent.
- Point a domain at the server.
- Run the four commands on the right.
- Open the domain and create the owner with the one-time setup code from
docker compose logs server. - Invite your team with a link. There is no open registration.
terminal
$ git clone github.com/federicoaldunate/fabrikka
$ cd fabrikka/docker/selfhost
$ ./init.sh your.domain
$ docker compose up -dOr deploy in one click
Verified, not documented
The same image, from a template
One service, one Postgres, one volume. Upgrading is pulling a newer image and restarting.
Railway guideWhat you're running
No telemetry.
The server phones nobody. There is no license check and no usage report.
No model keys.
Agents run on your people's machines. The server never needs an AI provider key.
One volume to back up.
A Postgres dump plus the uploads directory. Migrations run at start, so upgrades are pull and restart.
Private by design.
Invite by link only. A room is invisible to anyone not in it.
Your vendors, as you.
GitHub, Jira, Linear and others connect per person through each vendor's own MCP server.
AGPL-3.0.
Use it, change it, run it for your organization. If you offer a modified Fabrikka to others over a network, share your source.