Operating System CentOS

MyCollab Community Edition Is Archived: Status and Maintained Alternatives

MyCollab's repository was archived in April 2025. Here is the project's status, why a new install is a bad idea, and maintained self-hosted alternatives.

MyCollab Community Edition was an open-source, Java-based project management and collaboration suite with tickets, Kanban boards, milestones and documents, licensed under the AGPL v3. It is no longer developed. This page explains the project's current status, what it means if you were about to install MyCollab on a server, and which maintained self-hosted tools cover the same ground, with a verified quick start for one of them.

Project status

The MyCollab repository on GitHub was archived by its owner on 22 April 2025 and is now read-only. The README carries an archive notice stating that the project is no longer actively maintained. The last published release is 7.0.3.

In practice this means:

  • No bug fixes or security fixes will be released, for MyCollab itself or for the libraries bundled in its download.
  • Issues and pull requests can no longer be opened.
  • The documented requirements are frozen at Java Runtime Environment 8 or newer and MySQL 5.6 or newer, and nobody tests the application against current Java or MySQL/MariaDB releases any more.

The platform that older tutorials pair it with is gone too: CentOS 7 reached end of life on 30 June 2024, and its successors are AlmaLinux 9, Rocky Linux 9 and CentOS Stream 9.

Should you still install MyCollab?

Not for anything new. A project management tool holds user accounts, internal plans and attachments, and it is normally reachable from the internet. Running an unmaintained Java web application in that role means that any vulnerability found from now on stays open. The release archive is still downloadable from GitHub, but this guide deliberately does not walk through installing it.

If you already run MyCollab, treat it as legacy software: keep it behind a VPN or an IP allowlist rather than on the public internet, take regular dumps of its MySQL database and its file storage, and plan a migration. Do not count on a direct importer in the tool you move to: expect to carry tickets over through exports and manual work, or to start clean and keep the old instance for reference only.

Maintained alternatives

These self-hosted tools cover the same use case and are actively developed:

  • OpenProject: work packages, Gantt charts, boards, wikis, time tracking. The Community edition is open source. Closest to MyCollab in scope.
  • Redmine: issue tracking with projects, wikis and a large plugin ecosystem. This site has a separate guide for installing it on AlmaLinux 9 and Rocky Linux 9.
  • Taiga: Scrum and Kanban boards for agile teams. This site also has a separate guide for it.

The MyCollab README itself points to a project called FlowInquiry as a successor. Its repository could not be reached when this page was written, so check that it is alive before considering it.

Quick start: OpenProject with Docker

OpenProject documents Docker as an installation method, which makes the steps identical on AlmaLinux 9, Rocky Linux 9, Debian and Ubuntu. You need Docker Engine installed and at least a few gigabytes of free memory. First generate a secret for the application:

openssl rand -hex 64

Create directories for the database and uploaded files, then start the all-in-one container. Replace the host name with the name users will type in the browser and paste your secret in place of the placeholder:

sudo mkdir -p /var/lib/openproject/{pgdata,assets}

sudo docker run -d -p 8080:80 --name openproject \
  -e OPENPROJECT_HOST__NAME=openproject.example.com \
  -e SECRET_KEY_BASE=<your-secret-key-base> \
  -v /var/lib/openproject/pgdata:/var/openproject/pgdata \
  -v /var/lib/openproject/assets:/var/openproject/assets \
  openproject/openproject:17

The first start takes a few minutes while the database is initialised. Follow it with:

sudo docker logs -f openproject

The application then listens on port 8080. Sign in with the user admin and the password admin; you are asked to change the password immediately. The container expects to be reached over HTTPS under the host name you set, so put a reverse proxy with a TLS certificate in front of port 8080. For a quick test without TLS on a private network, add -e OPENPROJECT_HTTPS=false and set OPENPROJECT_HOST__NAME to the address and port you use, for example 203.0.113.10:8080.

OpenProject describes this single container as a quick way to get started and recommends its Docker Compose setup, with one container per process, for production. See the OpenProject Docker installation guide for that variant and for upgrades.

Frequently asked questions

Is there a community fork of MyCollab that continues development?

None is referenced by the project. The archive notice in the repository names a different product as the suggested successor rather than a continuation of the MyCollab code base.

Can I keep using the MyCollab source code?

Yes. Archiving does not change the licence: the code remains available under the AGPL v3, so you may run, study and modify it. You simply become the maintainer of whatever you run.

Does OpenProject need MySQL like MyCollab did?

No. OpenProject uses PostgreSQL, and the all-in-one container ships its own PostgreSQL server, which is why the command above mounts a pgdata directory. You do not need to install a database on the host.

Share story:

Continue reading other guides on How VPS.