Things that most actual Kanban flows have that no one has built into a decent product:
- Nested columns in lanes
- Rows for class-of-service
- WIP limits (per lane, per column, and per class-of-service)
- Sub-boards for meta issues
 Please prove me wrong if there is such a product out there!
However the reason I moved back to Trello was the interface was a bit old-fashioned, and I found it hard to get my team on-board on kanbanflow wheras it was really easy to get them going on Trello.
It’s always surprising to me how many “lean” and “agile” productivity tools completely focus on the artifacts and seem to have skipped the core concepts entirely.
It's a bummer because in the current state, Wekan doesn't really provide much real management value. I really wanted to use it for Kanban, because it's one of the flagship applications of the fantastic Sandstorm cloud platform (https://sandstorm.io), to introduce some colleagues to both concepts at the same time... but I guess I will only show them about the later.
Well at least it implements subtasks (checklists)!
Yes, Wekan does not have those features yet. Anyway, Wekan is being actively developed and features added. Wekan is friendly community driven project and welcomes all contributions.
Some have commented on Wekan GitHub issues that they prefer to use Wekan, because some others project management tools are overkill, or don't have the same usability as Wekan. It depends on use case.
Likewise sub-boards and meta-issues. If we're doing agile properly then each card represents a user-facing deliverable. Allowing meta-issues encourages doing the wrong thing.
Limiting work in progress I've achieved by having people assign themselves to cards, and questioning those who are on multiple cards. In the cases where we're violating our work-in-progress limit, I'd rather have the board reflect reality than not.
Having used it for some projects as an alternative to JIRA, Trello, GitLab boards, and a few others that I tried, I think it's not perfect, quite hard to use for non-tech users, but much better than most of the alternatives.
The number of details/settings available is great compared to Trello or GitLab. The pricing/hosting is great compared to JIRA. The non-tech usability is much better in JIRA and Trello, but for a tech team, it has many small things/shortcuts like ones you already use in their IDEs which is really great.
There are hundreds of tools like this, and I tried maybe 20 or 30 of them; the thing is, there is no perfect tool out there, and there won't be as use cases for such a tool can be extremely different! YouTrack gets a lot of points right for a tech team from my experience though.
But it's not general-purpose like Wekan or Trello; it's focused on workflow for managed IT and at the moment only pulls ticket data from ConnectWise, software for managed services providers.
Not trying to be a dick, but that sounds... kind of weasely.
Or a set of policies (solve in 4hours or less)
For the different tickets... It's the most powerful tool of the Kanban Method
Sorry about that, making new website is still in progress, there will be better landing page.
They've come a long way since and I think with time they can really shape up to become a strong competitor to Trello.
When I was working in a corporate environment I was able to setup an instance myself to help organize my tasks. Had I used Trello it would've been against our policy if I potentially left sensitive data on there and hard(read: impossible for me alone) to get permission to use Trello officially.
Trello related CSS was dropped in Wekan v0.9 2015-09-10, so after that Wekan does not use anything from Trello. UI and feature set is different.
According to Open Hub, Wekan currently has about 9000 lines of code without counting Meteor.js framework and related packages.
I don't remember did Wekan original creator Maxime Quandalle mention why did he choose Meteor.js in his talk at YouTube:
trello is a nice prototype tho.
I know self hosting is actually better but it is also work and is the typical information which people put on Trello confidential enough to justify self hosting? IDK and again Trello is free.
There are many reasons why self-hosting is the only viable option for some use-cases.
And then there are also data longevity issues, where you'd need the ability to backup and restore your data. If Trello goes away (as a free service), then you have fewer options in the regard.
This is exactly why I have a spare box running Wekan in my office at work. We run clinical applications for a hospital; sometimes project tracking+testing involves PHI that we have to be super careful about letting into the outside world.
What are you talking about? In what way are Trello users 'the product'? Are you just repeating a catch phrase that people say about other companies or do you actually know this to be the case?
I don't use Trello myself, but unless something has changed there aren't ads being shown to users (the reasons for the 'you're the product' saying for services like Google or Facebook), I'm not sure what data they could sell that would be worthwhile for a to-do app. What else would make the users 'the product'?
AFAIK they make all their money from their premium services, and since being bought by Atlassian I doubt revenue is at the top of their priority list anyway. Atlassian is full of premium services and Trello seems like a way to introduce all of those users to Atlassian's suite.
The free tier is a cheap loss leader for the actual product which are the enterprise and team versions which are not free.
Worth pointing out: they have a sandstorm version, which changes the amount of justification need rather a lot.
That or you need a contract that guarantees that the software is hosted outside the US, which Trello won't provide.
Not sure about the other stuff, I love Trello, but that purchase gave me pause.
Most of the so called clones don't even have basic stuff like using Command-v to paste pictures right from the clipboard directly into some card and you tell us Trello is dying?
Trello is UI-wise the best kanban thing by far. All clones might look like Trello but their usability has so many glitches and is always inferior.
Besides, nobody needs nested boards, just make another board. Moreover, it is common that after a while a board should get archived and a new one should be created instead. Otherwise it gets too messy and I don't want to imagine how 'nested boards' look.
Edit: thanks for the downvotes, would love to hear your opinions instead
Considering it for myself, even if it isn't the intended use case.
Wekan is available on many platforms:
a) In Wekan standalone version it's possible to disable self-registration in Admin Panel. There is inviting users, user permissions Admin/Normal/Comment only, but not user management yet:
and in next version it's possible for user to change password:
b) In https://sandstorm.io version there is already user management, Google/GitHub/LDAP/SAML authentication etc:
Newest version of Wekan is coming to Sandstorm in near future, progress is at:
There are issues for having LDAP/Saml/GitHub/Google etc auth for Standalone Wekan, but they are not implemented yet.
Sandstorm platform brings LDAP, SAML etc authentication to all apps running on Sandstorm.
Sandstorm has long list of sandboxing and other high-end security features:
All of Sandstorm is now Open Source, including Blackrock clustering:
For Standalone Wekan, Teams/Organizations/User admin is currently at planning stage:
Also shout out to https://greggigon.github.io/my-personal-kanban/ that is a simple and offline board
Wekan can be used locally on local network that is not connected to Internet. There is no offline sync yet.
There is possibility to use read-only mirroring to PostgreSQL using ToroDB:
but currently there's this bug, please wait for it to be fixed:
There is issue about directly using other backends than MongoDB, but that would require some code changes, so it's not implemented yet:
Wekan can be installed on x64 operating systems where source/Docker/Ubuntu snap/VirtualBox installs work.
There is no Raspberry Pi version yet:
Wekan has API and Outgoing Webhooks, but they are different than Trello:
Is it possible to use Trello extensions and integrate them with only Trello API ? And is it allowed to use Trello extensions outside Trello ? Or would they require separate integration to Wekan ?
For example on Trello templates can not be used outside Trello:
For general integration (similar to Zapier) there is plan to use Open Source tool Huginn: