Open source

An open-source whiteboard you can run yourself.

Freero is MIT licensed, from the canvas to the MCP server. Use it here, or run the same code on your own servers, under your own policies, next to your own Jira.

Why open source matters for a whiteboard

Your boards hold plans, research and decisions. You should be able to see how they are handled and choose where they live.

  • No lock-in

    Export boards as images, PDF, SVG, CSV, Markdown or JSON; read everything through the API; take the whole server with you.
  • Inspectable security

    The permission checks, the agent safety rules and the audit log are code you can read and test, not a promise on a page.
  • Your infrastructure

    Keep data in your region and network, behind your SSO, connected to your self-managed Jira Data Center or GitHub Enterprise Server.

Self-host in three steps

One Docker image serves the app, the realtime connections, the API, the MCP server and these pages.

  1. Get the code and build the image

    Terminal
    git clone https://github.com/antonber/freero.git && cd freero
    docker build -t freero .
  2. Try the whole stack on one machine

    Terminal
    docker compose up --build -d
    # open http://localhost:8080 and sign up
    The compose file runs Caddy in front of two app instances, PostgreSQL, Redis, MinIO for files and Mailpit for mail.
  3. Make it yours

    Set PUBLIC_URL, SESSION_SECRET and DATABASE_URL, put TLS in front, and schedule the backup script. Turn on what you need: SMTP, Google or Microsoft sign-in, an AI provider, tracker OAuth apps.

Guides: deployment, configuration, operations and backups.

Included in every installation

  • Can: Real-time boards, comments, notifications and version history
  • Can: The MCP server and its OAuth sign-in, the REST API, webhooks
  • Can: Jira Cloud and Data Center, Linear and GitHub sync
  • Can: Built-in AI on the provider you configure, including local models
  • Can: Team workspaces, SSO (SAML, OpenID Connect) and SCIM
  • Can: Audit log, admin console, retention and data exports
  • Can: Health checks, Prometheus metrics, JSON logs, an admin CLI
  • Can: Horizontal scaling with PostgreSQL, Redis and S3-compatible storage

Built to be changed

Freero’s codebase is organised so that a new feature is a new folder: features are discovered by convention, every piece of state has one writer, and an automated check fails when code crosses a boundary, naming the supported path. That keeps contributions small and reviews short.

Start with ARCHITECTURE.md and the README.

Frequently asked questions

Is there an enterprise edition or a licence key?

No. There is one codebase under the MIT licence. SSO, SCIM, the audit log, the admin console, tracker sync and the MCP server are in every installation.

What do I need to run Freero in production?

Docker (or Node 22), PostgreSQL 15 or newer, and a reverse proxy for TLS. Add Redis and S3-compatible storage to run more than one instance. Everything is configured with environment variables.

Can I turn the marketing pages off on my server?

Yes. Set SITE=false and the address people open goes straight to the app; no marketing page is served and search engines are asked to stay away.

Which licences do Freero’s dependencies use?

Permissive ones only: licences such as MIT, Apache-2.0, BSD, ISC and MPL-2.0 for code, and the SIL Open Font License for the Inter typeface. GPL, AGPL and source-available projects are integrated at the protocol level, never bundled.

Bring your team and your agents to one board

Free to use, open source, and yours to host. No credit card, no seat count.