Hello, I have a working instance with 30+ users and 20+ projects in a single server for my local office, but the company wants to expand the tool to entire workers (more than 7000 employees), can Kanboard handle all this load? is there a recommended design to use for large scale deploys?
I appreciate the community thoughts.
I think that it could be a problem if you have installed Kanboard with SQLite.
For a large scale use, it is recommended to use MySQL or PostgreSQL database type.
As you can read it in the documentation:
https://docs.kanboard.org/en/1.2.15/admin_guide/requirements.html
Thanks for the tip. For large scale is recommended to keep separated servers for application and DB or any other requirements like amount of RAM per 1000 user? or any other requirement like that?
Hello,
I deployed Kanboard on a big enterprise, and we have now more than 18k users.
Today we have 1 server with 16vcpu and 32gb of ram with : MariaDB, Apache (FPM) and PHP. We found some limits to this architecture (apache process, db on the same server than application, response time).
We are now migrating to a cloud infrastructure, and stopping to host our own MariaDB server, with AWS we will start with 1 server (Nginx + PHP), 1 load balancer (provided by AWS) and 1 Amazon RDS database. We already validated this architecture on “pre-production” and it was easy to migrate.
But if you don’t have budget for cloud, I didn’t recommend to keep the DB server on the same server than the application, and keep full backups of your DB and data/ folder.
Without any specific configuration, Apache by default will fails to handle so many users.
Thanks Cyboulette. How do you handle the admin responsibilities? I mean, 1 admin for 18K users sounds like a titanic task.
We are a fully dedicated team to the implementation of Kanboard (I mean that we have budget for this). But the tool is free for our users (we can say that Kanboard created “work” ^^).
(During COVID lockdown, we were gaining more than 1,500 users per month, before we were at ~500).
We are 4-5 administrators and we developed some plugins to facilitate our daily work. For example we implemented the SSO with our LDAP/IDP in order to automatise account creation and login.
Each new user is registered as “platform-manager” and not as “platform-user”, it allows our users to create their own projects and manage members inside (by permissions).
We are using the https://github.com/Confexion/Greenwing theme in order to make Kanboard prettier (because we had some bad feedbacks about UX) with custom adaptations.
By the past our admin team needed to manage : reset password, account creation, login issues etc. Since the SSO, the support is now only about questions on functionalities (and we are redirecting 90% of time to the kanboard documentation) or about new functionalities (interconnect with enterprise applications, UX, new features). I think we have now only <5 mails per day, before we had >30.
Technically we never had major issue with Kanboard or with our server. And we are trying to participate to open source 
Thanks Cyboulette, we are receiving each month new users because COVID, but we are experiencing a speed reduction when moving tasks between columns, any ideas?
Read this about performances : https://docs.kanboard.org/en/latest/admin_guide/performances.html
Use mysql/mariadb instead of SQlite, check the performances of your sql server.
Try to find where is the performance issue : kanboard itself ? configuration ? hardware ? apache ? etc.
Have a look on : https://github.com/kanboard/kanboard/issues/3822 and https://github.com/kanboard/kanboard/issues/4197 (there is an idea of solution/fix).
Cyboulette, do you use any plugins to create organization structure inside of Kanboard system?
For example splitting users into groups, wich are related to the departments in the company, and join several groups (departments) into one bigger department.
No, each user can create kanboard project and manage it. We have projects for teams, departments, manufacturing, or personal projects.
Do you use any plugins to create sub-projects to manage big projects?
Or current functions of Kanboard fit to most of user’s requests?
Current functions of Kanboard fit to most of user’s requests 
For big projects, users are using swimlanes or 1 project for each topic.
Of course, we have some users’s requests and we are trying to fit the needs in a global view (I mean for all the users, and avoid customization for each user’s).