SSD Nodes Learn Hosting plans →
How to do am Matt ConnorBy Matt Connor · Updated 2026-10-14

Which self-hosted Trello alternative dey best?

Compare Planka, Vikunja, Focalboard, Wekan and Kanboard on RAM floor, database, SSO, Trello import, plus which tools still dey maintained.

Which self-hosted Trello alternative you suppose pick?

Three self-hosted Trello alternatives dey worth your time: Planka if you want Trello board exactly and its import file, Vikunja when team need single sign-on and more than board, and Kanboard when VPS (virtual private server) small. No start new project with Focalboard. Its standalone server never get release since October 2023, don already reach 1029 days as at the August check, and its README now dey ask for maintainer.

Wekan na the fifth of the 5 tools wey dey here. E dey work, but e dey use memory several times pass everything else. We check every version, licence, and date below on 5 August 2026. We check the release, single sign-on, mobile, and Trello import claims again on 11 October 2026.

Board tool kọọkan need RAM amount nko?

ChartTypical idle memory per stack in MB, Docker on Ubuntu 24.04
Di data wey dey behind dis chart
[
  {
    "tool": "Planka + Postgres",
    "idle_memory_mb": 280
  },
  {
    "tool": "Vikunja + SQLite",
    "idle_memory_mb": 110
  },
  {
    "tool": "Focalboard + SQLite",
    "idle_memory_mb": 120
  },
  {
    "tool": "Wekan + FerretDB",
    "idle_memory_mb": 750
  },
  {
    "tool": "Kanboard + SQLite",
    "idle_memory_mb": 70
  }
]

Dem na typical idle figures for fresh install wey nobody dey use, the kind number wey docker stats reports one minute after the stack don start. Use dem to size your plan, then measure your own. The pattern matter pass the exact megabyte. If na the same VPS you wan use hold your photo library too, size that side first, because the minimums for PhotoPrism and Immich comparison dey for another order of magnitude, and board tool fit then use anything wey remain.

Kanboard na the minimum at 70 MB because e dey use PHP with SQLite. No long-running application process dey hold your boards for memory, so the container dey idle with almost nothing between requests. Vikunja na one Go binary at 110 MB, and SQLite na e default database, so one container na the complete stack. Planka need 280 MB because e always get two containers: Node server and PostgreSQL. Planka no get SQLite option, so you no fit negotiate the database.

Wekan dey at 750 MB because e na Meteor application. Meteor dey keep live query layer for Node memory and dey push every board change go every open browser through WebSocket, so e memory dey grow as connected people increase instead make e remain flat. For 1 GB VPS, Wekan go start, then die the first time some people open large board. The symptom na container wey disappear and come back with exit code 137, wey docker compose ps shows as restart loop. Confirm am for the host with dmesg -T | grep -i "out of memory", because kernel out-of-memory killer no dey tell the application anything.

Database dependency dey decide half of your backup work, so na one line for each one. Planka require PostgreSQL. Vikunja default to SQLite and e also support PostgreSQL and MySQL or MariaDB. Kanboard default to SQLite and e also support MySQL, MariaDB and PostgreSQL, and its documentation recommend PostgreSQL and warn against SQLite on NFS (network file system). Focalboard default to SQLite. Wekan support MongoDB wire protocol, and its default Compose file now ships FerretDB v1 with embedded SQLite backend instead of real MongoDB server, with separate MongoDB 7 Compose file if you want use one.

Which of these projects dey still get maintenance?

ChartAge of the newest stable release in days, checked 5 August 2026
Di data wey dey behind dis chart
[
  {
    "tool": "Planka 2.1.1",
    "release_age": 109
  },
  {
    "tool": "Vikunja 2.5.0",
    "release_age": 1
  },
  {
    "tool": "Focalboard 7.10.6",
    "release_age": 1029
  },
  {
    "tool": "Wekan 10.67",
    "release_age": 1
  },
  {
    "tool": "Kanboard 1.2.53",
    "release_age": 12
  }
]

Focalboard na the outlier for 1029 days. Its newest tag, v8.0.0 from June 2024, na release only for plugin, so the last release of the standalone server na v7.10.6 from October 2023. Mattermost move board development enter plugin for another repository, and the standalone README talk say dem no dey maintain the repository currently. Na this one clear "no" for this comparison. Everything else na trade-off.

Planka's 109 days healthy for project wey dey release a few times every year. Version 2.1.1 na from April 2026. Kanboard release v1.2.53 12 days before the check, and the two releases before am land for March and April 2026.

Vikunja and Wekan both release within one day of the check, but you suppose understand those two facts differently. Vikunja tag v2.5.0 as normal minor release. Wekan tag v10.65, v10.66 and v10.67 the same day, and na so e normally dey release. Frequent releases no mean say the target stable. With Wekan, you dey choose to follow version number wey dey change quickly, so pin the tag and read the notes before every bump.

Since that check, Planka release 2.2.0 on 9 August 2026 and security release 2.2.1 one day later, while Vikunja release v2.6.0 on 31 August and v2.7.0 on 2 October 2026. The Compose files further down pin those newer tags.

You dey get more than board?

Most comparison posts dey stop for “e look like Trello.” Na this axis dey decide pass RAM, because board no be good format for anything wey get deadline.

  • Planka na board tool and nothing else: projects, boards, lists, cards, labels, checklists, comments and attachments. Calendar and map views na Pro features as of October 2026.
  • Vikunja dey give four views over one set of tasks: List, Kanban, Table and Gantt. Task dey exist once, and you switch view instead of duplicating am.
  • Kanboard na boards with work-in-progress limits, subtasks, attachments, comments, automatic actions and small query language for filtering. The homepage itself talk say “The number of features is voluntarily limited”, and this na fair description.
  • Wekan na boards with swimlanes, plus checklists, custom fields, REST (representational state transfer) API and webhooks.
  • Focalboard dey offer board, table and calendar views over the same cards. Dem list am here for completeness.

If wetin you really want na wiki with some task tracking attached, this comparison no fit. BookStack, Wiki.js and Outline cover that kind setup, and the self-hosted Notion alternatives cover the all-in-one workspace.

Multi-user access and single sign-on

Planka no longer support OpenID Connect for the free Community edition. PLANKA 2.2.0, wey come out on 9 August 2026, remove OIDC and SSO from Community and move dem go PLANKA Pro, and the official Compose file no longer get the OIDC_* settings. If you upgrade instance wey dey use SSO, dem go deactivate those accounts until admin set password and reactivate each one. If na your only admin dey sign in through SSO, you go lock yourself out, so create local admin before you upgrade. Guest roles for people outside your organisation na Pro feature too.

Vikunja support OpenID Connect with several providers at the same time. Set VIKUNJA_AUTH_OPENID_ENABLED=true, then add one block of VIKUNJA_AUTH_OPENID_PROVIDERS_<ID>_* variables for each provider. E also get teams and per-project sharing, and na exactly wetin organisation of twenty people need.

Wekan support LDAP (lightweight directory access protocol), OAuth2, OIDC and SAML. Kanboard get LDAP built in and generic OAuth2 plugin for everything else, plus per-project roles and groups. Focalboard standalone server no get single sign-on at all, and this na another reason to leave am out.

Vikunja, Wekan and Kanboard all work with Authentik identity provider wey you run yourself, and this usually better pass giving twenty people separate password for every app. For Planka, this one now dey require Pro tier.

You fit import your Trello boards?

Planka get the simplest way. Export the board from Trello as JSON, create a board for Planka, click Import and choose Trello. Read the limits first, because dem real: users and attachments no dey import, na only one checklist per card dey come across, and Trello default JSON export dey stop for 1,000 actions without warning say e truncate the file. Check the file yourself before you trust the result.

Vikunja dey import through Trello OAuth flow, under Settings and then "Import from other services". You must enable each migrator for the config before its icon go show, and VIKUNJA_SERVICE_PUBLICURL must correct, because OAuth redirect dey happen for your browser, no be from the server. Vikunja also dey import Todoist, Microsoft To Do, TickTick and Wekan. Since v2.6.0, e dey import Planka v2 too, so if you start with Planka, you no lock yourself in.

Wekan accepts Trello board JSON wey you paste for its import form. Kanboard no get built-in Trello importer. Community TrelloJSON2Kanboard plugin adds Import Trello JSON option to the top menu of Kanboard dashboard and e dey take one exported board at a time. But e no dey inside Kanboard official plugin directory, its last commit na from July 2024, and its own TODO list still include downloading attachments. Test am with one board before you plan move years of Trello history around am.

Wetin the mobile experience be like?

Vikunja na the only one among the five wey get official mobile app, and dem release am separately from the server. The newest tagged release na 0.1.8-beta from October 2024, while the server reach v2.7.0 for October 2026. The app repository call am alpha pre-release, dem distribute am through Google Play beta channel, and e no link any App Store listing for iOS. So, treat the web interface as the main way to access am. Planka no get official app from the project, though the web interface dey responsive and third-party clients dey available. Wekan and Kanboard na web only, and Kanboard interface clearly build am for desktop screen.

Licence matter, and why Planka different

Planka no be open source again, and na this fact most comparisons dey leave out. E start under MIT, move go AGPL-3.0 for 2023, and from 2.0 series e dey release under PLANKA Community License, a fair-code licence wey PLANKA Software GmbH hold. GitHub dey report the licence as "Other" because OSI never approve that licence. You fit self-host am for your own people free, and the licence clearly allow personal, internal, non-profit, and educational use. To resell access to am, or run am as a service for other companies, you need commercial licence.

For two people, na fair arrangement. For company, na term wey you suppose read before twenty people's work enter the system. The other four na ordinary open source: Vikunja na AGPL-3.0, Wekan and Kanboard na MIT, while Focalboard combine Apache 2.0 and AGPL-3.0.

Compose file wey dem pin for the two picks

Pin the image tag. latest mean say the next docker compose pull fit carry you enter another major version, and major versions dey run database migrations wey you no fit easily reverse. Both files below na the upstream ones wey get tag fixed to real release. No pin Planka below 2.2.1: path traversal advisory wey dem publish on 10 August 2026 allow any signed-in user read files from the server for versions up to 2.1.1 wey use local file storage.

Vikunja for SQLite, one container:

services:
  vikunja:
    image: vikunja/vikunja:2.7.0
    restart: unless-stopped
    environment:
      VIKUNJA_SERVICE_PUBLICURL: https://tasks.example.com
      VIKUNJA_SERVICE_SECRET: replace-with-a-long-random-string
      VIKUNJA_SERVICE_TIMEZONE: Europe/Berlin
      VIKUNJA_DATABASE_TYPE: sqlite
      VIKUNJA_DATABASE_PATH: /app/vikunja/files/vikunja.db
    ports:
      - "127.0.0.1:3456:3456"
    volumes:
      - ./files:/app/vikunja/files

Create the data directory with correct owner first, because the container dey run as UID 1000 and e no fit write inside directory wey root own:

mkdir -p files && sudo chown 1000 files
docker compose up -d
docker compose ps
curl -sf http://127.0.0.1:3456/api/v1/info

Healthy stack go show the service as running, and the info endpoint go return JSON wey contain version field. Connection refused for here mean say the container don exit. docker compose logs vikunja name the reason, and permission error for the database file na the common one.

Planka for PostgreSQL, two containers:

services:
  planka:
    image: ghcr.io/plankanban/planka:2.2.1
    restart: unless-stopped
    volumes:
      - data:/app/data
    ports:
      - "127.0.0.1:3000:1337"
    environment:
      - BASE_URL=https://boards.example.com
      - DATABASE_URL=postgresql://postgres@postgres/planka
      - SECRET_KEY=replace-with-openssl-rand-hex-64
    depends_on:
      postgres:
        condition: service_healthy

  postgres:
    image: postgres:16-alpine
    restart: unless-stopped
    volumes:
      - db-data:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB=planka
      - POSTGRES_HOST_AUTH_METHOD=trust
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres -d planka"]
      interval: 10s
      timeout: 5s
      retries: 5

volumes:
  data:
  db-data:

POSTGRES_HOST_AUTH_METHOD=trust mean say PostgreSQL dey accept any connection without password. This safe only because database port no dey published to the host, so na only the other container for the same Compose network fit reach am. No add ports: entry to the postgres service.

Neither stack suppose face internet directly. Both bind to 127.0.0.1, so put reverse proxy for front and terminate TLS (transport layer security) there. Traefik for front of several Compose apps na the usual way to do this once you dey host more than one thing, and Docker Compose basics guide cover the parts of these files wey this page skip.

Board na database, so back am up

Board tool fit fail quietly. Nobody go notice missing backup until volume don disappear, and damaged SQLite file fit open normally before e report database disk image is malformed weeks later.

Never copy live SQLite file with cp. The copy fit catch write wey still dey happen, so archive go look complete but restore into database wey miss some rows. Stop the service for the few seconds wey the copy take:

docker compose stop vikunja
tar czf vikunja-$(date +%F).tgz files
docker compose start vikunja

For Planka, dump PostgreSQL instead of copying data directory from cluster wey dey run, and back up uploads volume separately, because attachments no dey inside database:

docker compose exec -T postgres pg_dump -U postgres -Fc planka > planka-db.dump
docker volume ls
docker run --rm -v planka_data:/data -v "$PWD":/backup alpine \
  tar czf /backup/planka-files.tgz -C /data .

docker volume ls dey print the real volume name. Na your Compose project name followed by _data. If you pass name wey no exist, e go create empty volume and give you valid but empty archive without error. So check the file size afterwards.

Then restore am once into scratch stack for the same box, and open card wey you remember. Backup wey you never restore na guess. Send the archives comot from the server too, because copy wey dey stored for the VPS wey you dey protect no be backup. restic backups from VPS cover that part.

Two recommendations

Two people for one 2 GB VPS: run Planka. E resemble Trello pass for look and how e dey work, the Trello import na file wey you fit drag enter, and 280 MB idle memory dey leave most of the 2 GB free for reverse proxy and anything else wey you dey host. Community License cover internal team of two people at no cost. If you no wan depend on source-available licence, Vikunja for SQLite with 110 MB na the open-source choice for the same server.

Twenty people for one organisation: run Vikunja for PostgreSQL. For that size, you need OpenID Connect instead of twenty local passwords. You need teams and sharing per project. Plenty of the work no go fit on board, so List, Table and Gantt views no be optional extra again. AGPL-3.0 also mean say licence matter no go come up as the number of people dey grow. Give am PostgreSQL instead of SQLite, put am behind reverse proxy, and keep the daily dump for another server or storage location.

If the server get less than 1 GB RAM, none of these two choices apply. Use Kanboard at 70 MB. Test the community TrelloJSON2Kanboard plugin with one Trello board before you rely on am for the rest. Use the memory wey you save for another thing from the self-hosting shortlist for 2026. If that server already dey run Jellyfin, Halcyon dey rebuild the library as 90s video store wey you fit waka through, and e go make more entertaining tenant than another board tool. The detailed installation for any tool wey you choose belong for its own guide. This page na only for making the choice.

FAQ

Which self-hosted Trello alternative dey use the least RAM?

Kanboard, at roughly 70 MB when e dey idle, because na PHP with SQLite and e no keep anything for memory between requests. Vikunja dey next at about 110 MB as one Go binary. Wekan na the heavy one at about 750 MB, because Meteor dey keep live query layer for Node memory for every browser wey connect. Measure your own with docker stats after the stack don idle, because these figures na typical values, no be promise.

I fit import my Trello boards enter self-hosted tool?

Planka and Wekan both fit take Trello JSON board export directly. Vikunja imports through Trello OAuth flow, and you must enable the migrator for the config before e go show for the interface. Kanboard no get built-in importer; na only the community TrelloJSON2Kanboard plugin dey available, and dem last update am for July 2024. Plan around two limits: Planka no import users or attachments and e only handle one checklist per card. Trello default JSON export dey stop for 1,000 actions without warning you say e truncate the data.

Focalboard still dey make sense for 2026?

No. The last standalone release, v7.10.6, come out for October 2023, and that was 1029 days before dem check this comparison on 5 August 2026. The newer v8.0.0 tag from June 2024 na plugin-only release, and the README talk say dem no dey maintain the repository currently. Mattermost continue board development only as plugin for separate repository, so na the server wey you go self-host stop development. Choose Planka or Vikunja instead.

Planka still be open source?

E no follow OSI definition again. Planka bin use MIT, move to AGPL-3.0 for 2023, and e dey ship with PLANKA Community License from version 2.0 onward. Self-hosting free for personal, internal, non-profit, and educational use. Reselling access or running am as service for third parties need commercial licence. Calendar view, guest roles, recurring cards, and, since 2.2.0, OpenID Connect single sign-on dey behind the Pro tier. If OSI-approved licence na strict requirement, Vikunja na AGPL-3.0 and Kanboard na MIT.

I need PostgreSQL, or SQLite dey enough?

Vikunja, Kanboard, and Focalboard default to SQLite, and e dey okay for small number of people on one server. Planka require PostgreSQL and e no get SQLite option. Move to PostgreSQL when several people dey write at the same time, because SQLite dey serialise writes and busy instance go start return database is locked. No put SQLite file for network share too: Kanboard documentation warn against SQLite on NFS for this exact reason.

Dis article help you?

#kanban#project-management#planka#vikunja#self-hosting#docker