FrankBoard

A modernization fork of Kanboard for cleaner, faster, more user-friendly self-hosted work boards for small teams (fork of Kanboard).

Site: frankboard.com · Migrate: frankboard.com/migrate · Setup help: support@zfiremedia.com

Owner: Frank Bryant / ZFire Media

What is FrankBoard?

FrankBoard is based on Kanboard. It preserves Kanboard's core strengths—simplicity, stability, self-hosting, low operational overhead—while preparing for incremental modernization. FrankBoard does not aim to become a Jira clone.

Differences from Kanboard: docs/product/differences-from-kanboard.md

Community is free (this repo). Paid migration assistance and VPS/Docker setup are available via email (invoice first). See docs/launch/service-quote-sheet-v1.md.

Screenshots

Login	Board	Task detail

More on the site: frankboard.com/#screenshots

VPS-First Docker Workflow

FrankBoard uses a VPS-first deployment model: the primary development and staging runtime is Docker on a VPS, not local Docker on the operator machine.

Basics

1. Clone this repo on a VPS with Docker and Docker Compose installed
2. Copy .env.example to .env and set POSTGRES_PASSWORD (and other overrides as needed)
3. Run docker compose up -d
4. Access the app at http://<vps-ip>:<APP_PORT> (default port 8080)
5. Default login: admin / admin — change immediately

See docs/deployment/vps-docker-staging.md for the full deployment guide.

Deployment / Staging Expectations

• Required: VPS with Docker and Docker Compose v2+
• Database: PostgreSQL is the primary target (configured via DATABASE_URL)
• Volumes: app_data, app_plugins, and db_data persist across restarts
• Optional: Reverse proxy (nginx, Caddy, Traefik) in front for SSL and custom domains

Documentation Locations

Resource	Location
Project status & phases	PROJECT_STATUS.md
Action history	ACTION_LOG.md
System architecture	docs/architecture/system-overview.md
Codebase audit	docs/architecture/codebase-audit.md
VPS deployment guide	docs/deployment/vps-docker-staging.md
Architecture decisions (ADRs)	docs/decisions/

Principles

• Preserve Kanboard's strengths: simplicity, stability, self-hosting, low overhead
• Do not become a Jira clone
• Incremental modernization, not a full rewrite
• Prefer PostgreSQL; use Docker for VPS deployment

Upstream

FrankBoard is based on Kanboard v1.2.51. See ChangeLog and Kanboard docs for app behavior and configuration.