Alternatives to Wekan logo

Alternatives to Wekan

Trello, Taiga.io, Restyaboard, Kanboard, and OpenProject are the most popular alternatives and competitors to Wekan.
54
100
+ 1
19

What is Wekan and what are its top alternatives?

Whether you’re maintaining a personal todo list, planning your holidays with some friends, or working in a team on your next revolutionary idea, Kanban boards are an unbeatable tool to keep your things organized. They give you a visual overview of the current state of your project, and make you productive by allowing you to focus on the few items that matter the most.
Wekan is a tool in the Project Management category of a tech stack.
Wekan is an open source tool with 19.1K GitHub stars and 2.8K GitHub forks. Here’s a link to Wekan's open source repository on GitHub

Top Alternatives to Wekan

  • Trello
    Trello

    Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what's being worked on, who's working on what, and where something is in a process. ...

  • Taiga.io
    Taiga.io

    Taiga is a project management platform for startups and agile developers & designers who want a simple, beautiful tool that makes work truly enjoyable. Over 55,000 developers & designers and over 52,0000 projects in first 10 months. ...

  • Restyaboard
    Restyaboard

    Trello like kanban board. Based on Restya platform.

  • Kanboard
    Kanboard

    It is a free and open source Kanban project management software. Your work is displayed on a board so that you have a clear overview of your project. Each column represents a step in your workflow. ...

  • OpenProject
    OpenProject

    It is an open source software for project management with a wide set of features and plugins and an active international community. ...

  • Jira
    Jira

    Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work. Jira comes out-of-the-box with everything agile teams need to ship value to customers faster. ...

  • Redmine
    Redmine

    Redmine is a flexible project management web application. Written using the Ruby on Rails framework, it is cross-platform and cross-database. ...

  • GitLab
    GitLab

    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers. ...

Wekan alternatives & related posts

Trello logo

Trello

42.5K
33K
3.7K
Your entire project, in a single glance
42.5K
33K
+ 1
3.7K
PROS OF TRELLO
  • 715
    Great for collaboration
  • 628
    Easy to use
  • 573
    Free
  • 375
    Fast
  • 347
    Realtime
  • 237
    Intuitive
  • 215
    Visualizing
  • 169
    Flexible
  • 126
    Fun user interface
  • 83
    Snappy and blazing fast
  • 30
    Simple, intuitive UI that gets out of your way
  • 27
    Kanban
  • 21
    Clean Interface
  • 18
    Easy setup
  • 18
    Card Structure
  • 17
    Drag and drop attachments
  • 11
    Simple
  • 10
    Markdown commentary on cards
  • 9
    Lists
  • 9
    Integration with other work collaborative apps
  • 8
    Satisfying User Experience
  • 8
    Cross-Platform Integration
  • 7
    Recognizes GitHub commit links
  • 6
    Easy to learn
  • 5
    Great
  • 4
    Better than email
  • 4
    Versatile Team & Project Management
  • 3
    and lots of integrations
  • 3
    Trello’s Developmental Transparency
  • 3
    Effective
  • 2
    Easy
  • 2
    Powerful
  • 2
    Agile
  • 2
    Easy to have an overview of the project status
  • 2
    flexible and fast
  • 2
    Simple and intuitive
  • 1
    Name rolls of the tongue
  • 1
    Customizable
  • 1
    Email integration
  • 1
    Personal organisation
  • 1
    Nice
  • 1
    Great organizing (of events/tasks)
  • 0
    Easiest way to visually express the scope of projects
CONS OF TRELLO
  • 5
    No concept of velocity or points
  • 4
    Very light native integrations
  • 2
    A little too flexible

related Trello posts

Johnny Bell

So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

#StackDecisionsLaunch

See more
Francisco Quintero
Tech Lead at Dev As Pros · | 13 upvotes · 1.5M views

For Etom, a side project. We wanted to test an idea for a future and bigger project.

What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

You kind of need a map to work as a proxy between the software and Google Maps API.

We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

Thanks to all the people behind Create React App it's easier to start any React application.

We also chose a module called Reactstrap which is Bootstrap UI in React components.

An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

See more
Taiga.io logo

Taiga.io

186
209
178
Free. Open source Agile Project Management tool. Top 10 Open Source Projects of 2014 by Red Hat sponsored...
186
209
+ 1
178
PROS OF TAIGA.IO
  • 40
    Free. open source. agile project management
  • 23
    Elegant, beautiful
  • 22
    Has most of the common tools in jira, for free
  • 21
    Responsive, client-side based ui
  • 17
    Excellent burn down charts to track progress of sprints
  • 16
    Simple
  • 14
    Can be deployed by ourself
  • 9
    Fast Growing Community
  • 4
    Jira + Confluence killer
  • 4
    Simple and very efficient for middle size project
  • 4
    Hipchat
  • 3
    Slack
  • 1
    Best agile by far
CONS OF TAIGA.IO
  • 0
    Bad performance
  • 0
    Bad ui

related Taiga.io posts

Restyaboard logo

Restyaboard

10
35
6
Open source, Trello like kanban board
10
35
+ 1
6
PROS OF RESTYABOARD
  • 4
    Open Source
  • 2
    Self hosted
CONS OF RESTYABOARD
    Be the first to leave a con

    related Restyaboard posts

    Kanboard logo

    Kanboard

    26
    34
    0
    Free and open source Kanban project management software
    26
    34
    + 1
    0
    PROS OF KANBOARD
      Be the first to leave a pro
      CONS OF KANBOARD
        Be the first to leave a con

        related Kanboard posts

        OpenProject logo

        OpenProject

        52
        84
        0
        Aa web-based project collaboration software
        52
        84
        + 1
        0
        PROS OF OPENPROJECT
          Be the first to leave a pro
          CONS OF OPENPROJECT
            Be the first to leave a con

            related OpenProject posts

            Jira logo

            Jira

            60.3K
            47.4K
            1.2K
            The #1 software development tool used by agile teams to plan, track, and release great software.
            60.3K
            47.4K
            + 1
            1.2K
            PROS OF JIRA
            • 310
              Powerful
            • 254
              Flexible
            • 149
              Easy separation of projects
            • 113
              Run in the cloud
            • 105
              Code integration
            • 57
              Easy to use
            • 52
              Run on your own
            • 39
              Great customization
            • 38
              Easy Workflow Configuration
            • 27
              REST API
            • 12
              Great Agile Management tool
            • 7
              Integrates with virtually everything
            • 6
              Confluence
            • 5
              Complicated
            • 3
              Sentry Issues Integration
            CONS OF JIRA
            • 8
              Rather expensive
            • 5
              Large memory requirement
            • 2
              Slow
            • 1
              Cloud or Datacenter only

            related Jira posts

            Johnny Bell

            So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

            When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

            With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

            I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

            In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

            #StackDecisionsLaunch

            See more
            Jakub Olan
            Node.js Software Engineer · | 17 upvotes · 380.1K views

            Last time we shared there information about our decision about using YouTrack over Jira actually we found much better solution that our team have loved. Linear is a minimalistic issue tracker that integrates well with Sentry, GitHub, Slack and Figma which are our basic tools. I would like to recommend checking out Linear as a potential alternative to "heavy" issue trackers, maybe at enterprises that may not work but when we're a startup that works awesome!

            See more
            Redmine logo

            Redmine

            592
            434
            129
            A flexible project management web application written using Ruby on Rails framework
            592
            434
            + 1
            129
            PROS OF REDMINE
            • 54
              Open source
            • 27
              Customizable with themes and plugins
            • 10
              Integration with code version control like git/svn
            • 9
              Powerful custom queries
            • 6
              RESTful API
            • 6
              Customizable workflows
            • 6
              Integration with email clients
            • 5
              Support for MS SQL Server
            • 2
              Time tracking, reports
            • 2
              Self-hosted
            • 1
              Projects and groups separation
            • 1
              Lightweight
            CONS OF REDMINE
              Be the first to leave a con

              related Redmine posts

              We were using a hosted version of Redmine to track defects and user stories originally. We migrated to Jira.

              Jira was an easy decision for a number of reasons:

              • It's much more "Scrum ready" straight out of the box
              • It's so much easier to keep a track of progress (I love the reporting)
              • It natively encourages you to adhere to Scrum/Agile/Kanban practices
              • Atlassian has a fantastic DevOps ecosystem when considering the likes of Confluence and Bamboo etc
              • So many integrations!
              • Its UI is so intuitive which makes it an absolute pleasure to use!

              I know there are alot of other tools in this space but not even considering anything else at the moment. Love Jira!

              See more
              GitLab logo

              GitLab

              60.5K
              51.6K
              2.5K
              Open source self-hosted Git management software
              60.5K
              51.6K
              + 1
              2.5K
              PROS OF GITLAB
              • 507
                Self hosted
              • 429
                Free
              • 339
                Has community edition
              • 242
                Easy setup
              • 240
                Familiar interface
              • 137
                Includes many features, including ci
              • 113
                Nice UI
              • 84
                Good integration with gitlabci
              • 57
                Simple setup
              • 34
                Free private repository
              • 34
                Has an official mobile app
              • 31
                Continuous Integration
              • 22
                Open source, great ui (like github)
              • 18
                Slack Integration
              • 14
                Full CI flow
              • 11
                Free and unlimited private git repos
              • 10
                User, group, and project access management is simple
              • 9
                All in one (Git, CI, Agile..)
              • 8
                Built-in CI
              • 8
                Intuitive UI
              • 6
                Full DevOps suite with Git
              • 6
                Both public and private Repositories
              • 5
                Integrated Docker Registry
              • 5
                Build/pipeline definition alongside code
              • 5
                So easy to use
              • 5
                CI
              • 5
                It's powerful source code management tool
              • 4
                Unlimited free repos & collaborators
              • 4
                Security and Stable
              • 4
                On-premises
              • 4
                It's fully integrated
              • 4
                Excellent
              • 4
                Issue system
              • 4
                Mattermost Chat client
              • 4
                Dockerized
              • 3
                Great for team collaboration
              • 3
                Free private repos
              • 3
                Because is the best remote host for git repositories
              • 3
                Low maintenance cost due omnibus-deployment
              • 3
                Not Microsoft Owned
              • 3
                Built-in Docker Registry
              • 3
                Opensource
              • 3
                I like the its runners and executors feature
              • 2
                Multilingual interface
              • 2
                Powerful software planning and maintaining tools
              • 2
                Review Apps feature
              • 2
                Kubernetes integration with GitLab CI
              • 2
                One-click install through DigitalOcean
              • 2
                Powerful Continuous Integration System
              • 2
                Native CI
              • 2
                HipChat intergration
              • 2
                Many private repo
              • 2
                Kubernetes Integration
              • 2
                Published IP list for whitelisting (gl-infra#434)
              • 2
                Wounderful
              • 2
                Beautiful
              • 2
                Groups of groups
              • 2
                The dashboard with deployed environments
              • 2
                It includes everything I need, all packaged with docker
              • 1
                Supports Radius/Ldap & Browser Code Edits
              CONS OF GITLAB
              • 28
                Slow ui performance
              • 8
                Introduce breaking bugs every release
              • 6
                Insecure (no published IP list for whitelisting)
              • 2
                Built-in Docker Registry
              • 1
                Review Apps feature

              related GitLab posts

              Tim Abbott
              Shared insights
              on
              GitHubGitHubGitLabGitLab
              at

              I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

              But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

              • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
              • You can't let anyone with a GitHub account self-assign issues to themselves.
              • Many more similar issues.

              It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

              We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

              See more
              Joshua Dean Küpper
              CEO at Scrayos UG (haftungsbeschränkt) · | 20 upvotes · 691.2K views

              We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

              While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

              We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

              See more