Does self-hosting Trello cost less than staying on Trello?
WeKan and Nextcloud Deck carry no license fee, so the comparison turns on infrastructure, staff time, support and migration. If your renewal is driven by per-user pricing, the question is whether the seats you pay for each year cost more than the people and servers needed to run a board tool yourself. Pull your current Trello plan terms (Standard, Premium, Enterprise, and any Atlassian Guard add-on) from your admin console or order form, and multiply them by your real active member count, including guests. Do not assume the list price applies to your contract. Ask your Atlassian account team to confirm what is billed at renewal.
Self-hosting usually costs more in the places that are easy to overlook. Someone must install WeKan (MongoDB 6 to 9, or the default FerretDB v1 with SQLite) or Nextcloud Deck, apply upgrades, watch security advisories and keep backups tested. WeKan publishes releases very frequently, so budget time for regular updates. Nextcloud requires you to move one major version at a time, back up before every upgrade and disable third-party apps until they are confirmed compatible. Those tasks recur every year, and they are where internal hours and any outside help will go. Hosting, storage, and off-site backup copies are recurring costs too.
Self-hosting usually costs less as headcount grows, because there is no per-seat charge that rises with each new member or guest. The price of the server stays roughly flat, while the Trello bill scales with users. Optional paid support is the other variable. WeKan offers private pre-paid support through wekan.fi, and Nextcloud Enterprise is sold in tiers with a 100-user minimum. Neither vendor's price is covered here, so request written quotes that state the user count, support hours, response times and maintenance period, and compare them with your Trello renewal over the same term. Include one-time migration effort in the same model.
Which cost components move when you replace Trello
This table lists the cost components that change when a team moves from Trello to self-hosted WeKan or Nextcloud Deck, with each side marked as one-time or recurring. Start with the license row, then check infrastructure, upgrades and internal skills, which usually carry the ongoing cost. The main takeaway is that removing license fees shifts spending toward hosting, operations and any paid support you choose to buy.
| Cost component | Trello | WeKan or Nextcloud Deck |
|---|---|---|
| License or subscription | Recurring per-user subscription on the plan you choose. Confirm current rates with Atlassian. | No license fee. WeKan is MIT-licensed, and Nextcloud Server is AGPL-3.0 with a free community edition. |
| Infrastructure | None on your side. Atlassian hosts the service. | Recurring: servers or cloud instances, storage and a database such as MongoDB, PostgreSQL or the SQLite default. |
| Implementation and migration | One-time internal effort to set up workspaces, members and login settings. | One-time: install, configure login, and import boards. Trello's JSON export carries only the 1,000 most recent actions per board. |
| Support | Included in plan tiers, billed recurring through the subscription. | Optional, recurring. WeKan offers paid private support; Nextcloud Enterprise list prices start at 71.29 euros per user per year (Nextcloud pricing page). |
| Upgrades | Handled by Atlassian. No upgrade project to fund. | Recurring effort: WeKan ships releases often, and Nextcloud majors arrive every four months and must be applied one at a time. |
| Backups | Atlassian operates the service. Your own export copies remain a task you must schedule and check. | Recurring: you run and test backups. Nextcloud All-in-One bundles BorgBackup-based backups. |
| Internal skills | Recurring admin time for workspace settings, access and plan management. | Recurring: staff to run the database, web server, patching, access rules and monitoring. |
What moves the comparison for your organization
Five or six variables decide whether self-hosting costs more or less than staying on Trello. Each one shifts the balance in a predictable direction, so you can rank them against your own environment before asking for any quote.
User count and seat growth
Trello bills per user on each plan, so cost rises with every added member. Self-hosted WeKan and Nextcloud Deck carry no per-seat license fee, which means the cost of hosting grows more slowly than headcount. Your cost moves mainly with infrastructure sizing and administration time. Ask how many active users you have now, how many you expect in two years, and how many guests need access to individual boards.
Data volume and attachments
Attachments and long board histories drive storage, backup size and restore time more than user count does. Trello's JSON export is capped at the 1,000 most recent actions per board, so busy boards with large files need a planned migration path and a larger storage budget. Measure attachment totals per workspace and the age of archived cards before sizing storage.
Edition choice for Nextcloud
Nextcloud Server is free under AGPL-3.0, but Nextcloud Enterprise adds paid maintenance and support in Standard, Premium and Ultimate tiers with a 100-user minimum. Choosing Enterprise moves cost from staff time to a recurring subscription, and the tier determines how long maintenance lasts and how quickly support responds. Confirm which tier matches your required response times before you budget.
Paid support for WeKan
WeKan is MIT-licensed and can run without a subscription, but it is a fast-moving project with frequent releases. Official private pre-paid support from wekan.fi is an optional recurring cost that buys vendor access for fixes and upgrades. Decide in advance whether your team can absorb upgrade testing in-house or whether you need a support contract with defined response expectations.
Availability and backup targets
Self-hosting moves responsibility for uptime, restore testing and off-site copies to your team. Recovery time and recovery point objectives set how much redundancy you pay for, such as a second node, replicated storage or a managed database. Nextcloud All-in-One bundles BorgBackup-based backups, which lowers setup effort, but you still need to test restores and define retention.
Existing internal skills
Your current staff determine the largest hidden cost. WeKan runs on MongoDB 6 to 9 or on its default FerretDB with SQLite, so teams that already operate MongoDB or Node.js administer it more easily. Nextcloud is written mainly in PHP with a recommended MariaDB or PostgreSQL stack, so PHP and database administration skills matter. Where skills are missing, budget for training or external administration, and ask who will apply major version upgrades, which Nextcloud requires one major version at a time.
How to build the cost model with your own numbers
This sequence turns the cost components in this comparison into a worksheet built from your own seat counts, attachment volumes and admin hours, so both options are priced for the same period. The output is a side-by-side model with one-time and recurring lines kept apart.
Record current Trello seats and plan terms
Pull the list of active Trello members, guests and workspaces from your Trello admin view, and note the plan tier, billing cycle and renewal date for each workspace. Confirm the current per-user rate with Atlassian's pricing page or your billing invoice rather than a figure from memory. Separate paid seats from guests, because the billing treatment can differ. The check is a single table with seat count, tier and renewal date for every workspace.
List identity and admin requirements
Document whether you use Atlassian Guard for single sign-on, SCIM provisioning, audit logging or domain controls, and which of these features you rely on day to day. Then list the equivalent needs for WeKan, which supports SAML, LDAP, OAuth2 and passwordless login, and for Nextcloud, which documents LDAP, OpenID Connect and SAML backends. Ask your identity team whether these fit your directory and whether any control must be rebuilt rather than inherited. The check is a requirements list that names each control you must keep.
Measure attachment and backup volume
Export or sum the size of attachments across your active boards, then add the growth you expect over the period you are modeling. Storage and backup costs follow this number, not the seat count, so record it separately. Decide where the data will live, whether on a VM, in Kubernetes or in an existing Nextcloud instance, and price the storage tier and backup target you already use. The check is a storage estimate in gigabytes with a backup copy count, both tied to your own environment.
Assign monthly admin and upgrade hours
Estimate the hours your team will spend each month on patching, upgrades, user administration, plugin checks and monitoring. For Nextcloud, include the one-major-version-at-a-time upgrade path and the backup step before each upgrade, and for WeKan, include the frequent release cadence and the choice of database backend. Assign these hours to named roles at your internal loaded rate. The check is a monthly hours table by role that a finance reviewer can challenge.
Request written support quotes
Decide whether you need paid support at all, then ask each vendor for a written quote tied to a specific scope. For Nextcloud, compare the Standard, Premium and Ultimate tiers and their stated maintenance and response terms, and confirm the 100-user minimum applies to your organization. For WeKan, ask the official support provider at wekan.fi what is included in pre-paid support. Ask DeployOpen for a fixed-scope quote for any implementation or ongoing support you choose. The check is a set of written quotes with scope, term and renewal terms attached.
Cost the migration as one-time work
Estimate the one-time effort to export Trello data, import boards, reconcile comments and attachments, test permissions and train users. Note that Trello's JSON export carries only the 1,000 most recent actions per board, so busy boards may need a different extraction route, and include that work in the estimate. Keep the result in its own column, because it does not recur. The check is a migration line with hours, tooling and any outside help, marked clearly as one-time.
Compare both options over the same period
Place Trello's recurring seat fees and the recurring lines for each self-hosted option in one table, using the same number of months for all of them. Show one-time migration and setup costs separately, then add the recurring lines to each total. Note what drives each figure up or down, such as seat growth, attachment growth or the support tier you pick. Review the model with finance and your security team before you use it for a renewal decision. The check is a side-by-side model where every line is labeled one-time or recurring and the period is stated once.
What you pay for on the self-hosted side
The software is free, but the platform underneath it is your cost. WeKan has no license fee under the MIT license, and Nextcloud Server is AGPL-3.0. What you pay for is the database, the web tier and the backups. WeKan supports MongoDB 6 to 9, but its default is FerretDB v1 with SQLite, which needs no database server, so a small team can start without one. FerretDB with PostgreSQL also works. Nextcloud 35 recommends MariaDB 11.8 or PostgreSQL 18, PHP 8.5 and either Apache 2.4 or nginx with php-fpm. Each of these is a component someone must patch, monitor and back up. Confirm with your platform team which database engine you already operate, because that choice decides whether the database is an extra service or a shared one.
Nextcloud also sets an upgrade cadence you must staff. Nextcloud does not allow skipping major releases, so you must move one major version at a time, back up before every upgrade and disable third-party apps until each is confirmed compatible. Nextcloud 35 was released on 16 September 2026 and is supported until September 2027, so plan a recurring upgrade window into your operating calendar. WeKan also ships releases very frequently, which argues for a pinned version and a test instance rather than automatic production updates. Backups are a recurring cost in both cases, and the cost of restore testing is easy to forget.
If you want vendor-backed support, Nextcloud Enterprise is sold in Standard, Premium and Ultimate tiers with a 100-user minimum. Standard includes 1-year maintenance, Premium adds a maintenance lifecycle of 5 or more years, and Ultimate adds support up to 24/7 with response times down to 1 hour, according to the Nextcloud pricing page. List prices start at 71.29, 104.99 and 204.75 euros per user per year respectively for 100 or more users, with lower rates from 200 users. Ask any quote to separate subscription fees from hosting, database and backup labor, and confirm whether the 5-year lifecycle covers the exact Nextcloud major version you deploy.
How the comparison differs by team size and setup
A small team that wants a Trello-like board on its own hardware usually has the simplest cost profile. WeKan is MIT-licensed, so there is no license fee to pay. The recurring costs are the server, the database choice, backups and the person who keeps the instance patched. WeKan's default setup uses FerretDB v1 with SQLite, which avoids running a separate database server, but the official Docker and Kubernetes images and the Snap package change how much operational work sits with the team.
- Hosting: A single VM or a small host that someone on the team can administer is often enough for a board-only workload. Ask the partner what size they would size for your user count and attachment volume.
- Upgrades: WeKan publishes releases very frequently, so budget time for regular updates. A Snap install updates automatically, while Docker installs need a planned pull and restart.
- Backups: Backups are your responsibility. Confirm the database and attachment storage are both included in the backup job and test a restore.
- Login: SAML, LDAP and OAuth2 options are listed in the README. Confirm which of these your identity provider supports before you assume single sign-on is in place.
- Support: WeKan's README points to official private pre-paid support from wekan.fi. Ask for the written scope and response expectations before you rely on it.
Ask any quote to separate one-time migration work from recurring hosting, patching and backup time, and to state who restores the instance if it fails.
If your organization already runs Nextcloud for files and chat, Deck adds a kanban board to infrastructure you already pay to operate. The main cost question shifts from a new platform to the scope of the existing one. Nextcloud Server is AGPL-3.0, so the community edition carries no license fee. Enterprise subscriptions are a separate, optional cost, and their list prices should be checked on the vendor's page at the time of quoting.
- Incremental cost: Deck adds boards to a server you already maintain, so the extra effort is mostly configuration, user onboarding and testing the app after upgrades.
- Upgrade discipline: Nextcloud does not allow skipping major releases, so you must upgrade one major version at a time, back up before each upgrade and disable third-party apps until they are confirmed compatible. Plan that time against your release calendar.
- Identity: LDAP and Active Directory users can log in with directory credentials, and OpenID Connect and SAML backends are documented. Confirm which backend matches your directory before you build the rest of the plan.
- Deployment method: Nextcloud All-in-One bundles caching, PostgreSQL, backups and antivirus. Ask whether your team will run it or whether a partner will manage it.
- Database and PHP versions: Check the supported database and PHP versions for the release you plan to run, since older stacks may need changes first.
Ask the partner to show how Deck fits into your existing backup and upgrade windows, not only the cost of installing it.
A regulated organization usually cares less about the license and more about who answers when something breaks, who can show evidence of controls and how the platform is changed. Community editions are free, but the cost of a contracted support model, documented change control and assessment readiness can be the largest line in the budget. Compare that against the per-user fees you pay today, using the same time horizon for both.
- Support scope: Ask for response times, support hours and what is excluded in writing. WeKan offers paid private support, and Nextcloud Enterprise tiers differ by maintenance length and support hours, according to Nextcloud's pricing page.
- Maintenance lifecycle: Confirm how long the chosen version receives security fixes. Nextcloud supports each major release for one year, so long lifecycles may require a paid tier.
- Evidence: Ask the partner what documentation they produce for access control, backups and change records. DeployOpen prepares systems and evidence for compliance assessments but does not issue audit reports or certifications, so the independent auditor's requirements should be confirmed early.
- Testing: Ask whether security testing of the deployed instance is in scope or sold separately, and how often it recurs.
- Exit terms: Ask how data is exported and what the partner's obligations are if you change providers.
Request a quote that lists the support tier, the maintenance period and the evidence deliverables as separate line items, so you can compare it fairly with the renewal you are replacing.
What migration adds to the first-year cost
Migration is often the largest one-time item in the first year, and it is easy to underestimate because Trello's data does not move cleanly in a single step. WeKan has a built-in Trello import, and Nextcloud Deck can import Trello boards with the occ deck:import command, so the tooling exists for both. The harder question is how much of the board history you need to keep. Trello's JSON export carries only the 1,000 most recent actions per board, so older comments and activity will not come across in that export. Keeping all comments and raw attachments requires a Premium Workspace export, which needs a Trello plan that includes it. Confirm which of these you need before you budget, because that choice determines how much manual reconstruction your team will do. The migration guide for WeKan and the sibling pages on exporting from Trello and migrating to Nextcloud Deck explain each route in detail.
Staff time is the component most teams underbudget. Someone must map Trello lists to WeKan swimlanes or Deck stacks, decide how Trello labels become WeKan labels or Deck tags, and match Trello members to accounts on the new server, including people who have left the organization. Plan for a pilot board that a few users check line by line before the rest of the boards move. Validate attachments separately: confirm that files open, that links resolve and that card counts match the source for each board. Large attachment sets and boards with long comment histories take longer to check, and archived cards need an explicit decision about whether they move at all. All of this is one-time work, and it is usually paid from internal staff time, a DeployOpen fixed-scope engagement or both. When you request a quote, ask for the mapping approach per board, the attachment validation method, the handling of archived cards and the user matching process, and ask what is excluded from the written scope. Your own IT team should also confirm the Trello plan and export options available to your organization before work starts.
Questions buyers ask before comparing Trello costs
How much staff time does self-hosting WeKan or Nextcloud Deck take?
The time is recurring and predictable, but the total depends on your environment, your change process and how many users you serve. Plan for regular work on upgrades, backup restore tests, monitoring, user and group administration and security patches. WeKan publishes releases very frequently, with v12.52 on October 17, 2026 after v12.51 and v12.50 the same day, so someone must track and test each update. Nextcloud publishes a new major version every four months, and each major version needs its own staged upgrade. Ask your platform team to estimate hours per month against the upgrade calendar before comparing with a subscription.
Can a small team run WeKan or Deck without outside help?
A small team with Linux, container and database skills can run either app, but it needs a named owner and a tested recovery procedure. WeKan can be installed as a Snap with automatic updates, as an AppImage, or as Docker and Kubernetes images, and its default setup uses FerretDB with SQLite, so no separate database server is needed. Nextcloud All-in-One bundles PostgreSQL, Redis, caching, optional Office and Talk, and BorgBackup-based backups. Review the WeKan repository and the upgrade rules for your chosen app, then decide whether your staff can own upgrades and restores without outside help.
How long does a Trello migration take, and what drives it?
No general duration can be stated because the effort depends on the scope of your Trello workspace. The main drivers are the number of boards, the volume of comments and attachments, archived cards, Power-Ups that your teams rely on, the number of users to map to accounts, and how much validation your teams require before cutover. WeKan's documented import formats include Trello, so the import path is supported, but the result still needs checking board by board. Ask any provider for a written scope that lists the boards, the data types in scope, the testing steps and the acceptance criteria before agreeing on a timeline.
What recurring costs remain after a self-hosted launch?
The recurring costs are infrastructure, storage, backup retention, staff time and any support subscription. Infrastructure and storage grow with the number of boards and attachments, and backup copies add storage in a second location. One-time costs include the initial setup, migration, testing and user onboarding. Nextcloud Enterprise is a paid option with per-user list prices on its pricing page, starting at 71.29 euros per user per year for the Standard tier with a 100-user minimum, so confirm current figures on the Nextcloud pricing page before budgeting. WeKan's paid support comes from its maintainers as a private pre-paid arrangement.
When is paid support for WeKan or Nextcloud worth it?
Paid support is worth evaluating when you lack staff to cover upgrades and incidents, when a regulator or internal policy requires a named support path, or when a single outage would disrupt many teams. Nextcloud Enterprise's Standard tier includes one year of maintenance, Premium adds a maintenance lifecycle of five or more years with extended support hours and clustered instance support, and the top tier adds support up to 24/7 with response times down to one hour, according to its pricing page. Compare those terms with your own incident needs and the cost of an internal on-call rota before you decide.
How do I compare a per-user Trello plan with the cost of a server?
Compare the recurring per-seat subscription with a mostly fixed server cost plus staff time, then add one-time migration effort. A per-user plan grows with headcount and includes vendor-run hosting, while a server grows mainly with storage, backup retention and the hours your team spends operating it. Build a model with these lines: current seat count and the plan prices shown on Atlassian's pricing page, hosting and storage, backup copies, staff hours at your loaded rate, migration and testing, and optional support. Run the model for each year of the contract, and check which Trello features your teams actually use, such as Power-Ups, before assuming equal functionality.
Which identity and SSO options do the self-hosted boards support?
Both apps support centralized sign-in, but you should confirm the exact configuration for your identity provider. WeKan's README lists login options including SAML, LDAP, OAuth2 login providers and passwordless login. Nextcloud documents LDAP and Active Directory integration, where directory users appear in Nextcloud and sign in with directory credentials, and it also documents OpenID Connect and SAML authentication backends. Confirm with Atlassian which Trello plan includes single sign-on and what Atlassian Guard adds for your administrators, because those controls are part of the commercial comparison.
When an implementation partner changes the cost picture
An implementation partner turns the self-hosting cost into a written scope, which is the main way to keep it predictable. DeployOpen plans, implements, hardens, backs up and documents WeKan or Nextcloud Deck inside your own cloud account, data center or air-gapped network. The work covers the parts a small team usually cannot absorb alongside daily duties: choosing the database (WeKan defaults to FerretDB with SQLite, while MongoDB 6 to 9 is also supported), configuring login through SAML, LDAP or OAuth2 or through Nextcloud's LDAP, OpenID Connect and SAML backends, setting up backups, and writing the runbook your operators will follow.
Most engagements are fixed-scope, so the deliverables, the environments in scope, the Trello import work and the acceptance tests are agreed in writing before any work starts. Ask for the scope to name the exact WeKan or Deck version, the hosting model, the number of boards and attachments to migrate, and who signs off on the cutover. Those items are what move a quote up or down, so a vague scope is usually where surprises appear later.
Ongoing support, upgrades and continuous testing are available as retainers, and that is where recurring cost sits. For Nextcloud, plan upgrades one major version at a time with a backup before each step, and confirm which of your apps are compatible before you upgrade. DeployOpen does not publish a price list, so a quote follows the written scope. Ask each vendor you compare for the same breakdown: setup, hosting, backup, support and upgrade effort, so the figures line up with your own internal estimate.
How DeployOpen scopes a fixed-price implementation
DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure. For a Trello cost vs self-hosted WeKan and Nextcloud Deck decision, the work starts with a written scope that shows which boards, users, attachments and access rules move, and what the platform will cost to run in your environment.
How we scope
- Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope lists which Trello boards, lists, cards, comments and attachments are in or out of the migration.
- Scoping records whether WeKan or Nextcloud Deck fits your login, hosting and existing Nextcloud or database setup.
How we build
- Installation runs in your own cloud accounts, data centers or air-gapped networks, not in a DeployOpen-hosted environment.
- Import runs are tested on copies of representative boards, and gaps in comments or attachments are documented before cutover.
- Login integration with your identity provider, backups and upgrade paths are configured and tested as part of the agreed scope.
How we hand over
- Handover includes configuration documentation, runbooks for backup, restore and upgrades, and a record of what was migrated.
- Your team receives the deliverables listed in the written scope, so you can see what was built and what was left out.
- Operators learn the upgrade sequence for their chosen platform, including the backup step before each change.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover.
- Ask for a quote built from the written scope, with setup, migration, hosting and support priced as separate line items.
- Confirm with us which support responsibilities sit with your team and which sit with a retainer before signing.
