I work at XWiki, and we’ve been getting a lot of questions from teams that need to stay on-prem after Atlassian Data Center’s end of life. Together with OpenProject, we’ve built a setup that covers most Confluence + Jira use cases, fully open-source and self-hostable.
Next week, we’re doing a live session to show how migrations work, what tools we use for importing spaces, issues, and attachments, and what still needs improvement.
If you’re running on-prem or testing other open stacks after Atlassian, I’d be interested to hear what approaches you’ve tried.
For teams looking to stay on-prem or move off Atlassian’s stack, we’ve been working on integrating XWiki (for structured documentation) and OpenProject (for project management).
Both are open-source and can be self-hosted, with integrations for linking tasks, requirements, and project docs. We’re hosting a live demo + Q&A on Nov 19 showing how it works in practice.
[For full disclosure] I’m part of the XWiki team, and I'd be happy to answer any questions about this.
Together, XWiki and OpenProject provide a powerful open-source alternative to Atlassian’s Confluence and Jira. XWiki delivers a flexible, extensible knowledge management platform that serves as a true alternative to Confluence in collaborative documentation and team knowledge sharing. When it comes to OpenProject, its full-featured project management and issue tracking capabilities act as a strong Jira alternative. This partnership will offer organizations an integrated, open-source stack. It's a privacy-respecting, vendor-neutral solution for teams seeking to move away from proprietary tools without compromising on functionality or user experience.
The Historical Dictionary of Switzerland runs their entire multilingual encyclopedia (all 36,500+ articles across 4 languages) on XWiki.
This is more than a customized wiki. It’s a platform that supports multilingual publishing, complex editorial workflows, Jira integration, and fast content discovery. All built on open-source software, developed in Europe.
The Historical Dictionary of Switzerland (HLS) needed to move beyond outdated tools, tangled workflows, and rigid systems. They made the switch to a flexible, open solution, and they’re sharing what that looked like.
This release introduces important improvements for the definition of wiki macro parameters and provides a new mechanism for faster macro execution. It also contains a redefinition of the real-time editing toolbar for better user experience. Further, it is now possible for users to resize the panel columns on the right and left of the content. This release contains security fixes, with the highest severity being 9.3/10.
With digital transformation accelerating, your organization’s control over its data and workflows is more critical than ever. While many collaborative platforms seem convenient, they often come at a steep price: vendor lock‑in, a one-size-fits-all approach where customization and deployment are limited, and data management practices remain unclear.
XWiki offers a different approach. It offers a flexible, open-source platform that you can shape to fit your company's specific workflows and security requirements. It puts you in control.
This is indeed obvious for weeks, no questions here. However, the even more accelerated developments in the last 2 weeks, as well as what happened in France with the Ministry of Education opting for a Microsoft solution, even if there are so many good French options out there (Suite Hexagonne to name at least one), made it even more obvious and stringent.
Next week, we’re doing a live session to show how migrations work, what tools we use for importing spaces, issues, and attachments, and what still needs improvement.
If you’re running on-prem or testing other open stacks after Atlassian, I’d be interested to hear what approaches you’ve tried.