In brief
Collabase is a Swiss collaboration platform by Infometis AG in Zurich, covering the project and portfolio side of what companies use Jira for today.
The difference is in the cut: projects, knowledge pages, asset registry, test management, automation and time tracking are one product from one vendor, rather than several products plus extensions from a marketplace.
Collabase runs as a dedicated instance in a Swiss data centre or entirely on your own infrastructure; in both cases the data location is a commitment rather than a setting.
For pure software development with Git workflows and build pipelines, Collabase is not the intended tool. The existing toolchain stays in place there.
When a change gets considered at all
In the conversations we have, there are three occasions. None of them is about dissatisfaction, and all three hang on a date or a number.
A vendor event with a date
Atlassian ends Data Center on 28 March 2029, and sales to existing customers stop on 30 March 2028. Anyone running on their own infrastructure has to have chosen a path by then.
A requirement on data location
A rule from a contract, a regulator or an internal policy sets where the data has to sit. That answer rules paths in or out before anyone talks about features.
The number of tools in the house
Projects in one tool, documentation in a second, test cases in an extension, time tracking in a third. Each with its own contract, its own invoice and its own permission model.
The features side by side
Every cell is a sentence about what a product does at that point. No ticks, no crosses: where Collabase does not have something, it says so just as plainly as for the other.
| Feature | Jira | Collabase |
|---|---|---|
Operation and data | ||
| Operating models | Cloud. Data Center runs until 28 March 2029. | Dedicated instance in a Swiss data centre, or entirely on your own infrastructure, including networks without internet access. |
| Data location | Data residency for Switzerland on the Standard, Premium and Enterprise plans, for the core products. For Marketplace apps it has to be checked app by app. | Switzerland, in both operating models and independent of any plan. |
| Vendor | Atlassian Corporation, publicly listed, headquartered in the US and Australia. | Infometis AG, Zurich. |
Scope | ||
| Projects and issues | Jira Software, with boards, sprints and custom workflows. | Projects, with boards, cycles and custom workflows. |
| Knowledge pages | Confluence, a separate product with its own licence. | Docs, in the same product and the same space as the issues. |
| Test management | Through apps from the Atlassian Marketplace. | Test Management, in the same product, aligned to the QualityTree framework. |
| Asset registry | Assets in Jira Service Management, on the Premium and Enterprise plans. | Registry, in the same product, with custom schemas and relations. |
| Automation | Automation for Jira, included in the product. | Automation, in the same product, with 38 connectors. |
| Time tracking | Through apps from the Atlassian Marketplace. | Time, in the same product, on tasks and projects. |
| Software development | Bitbucket for Git and pipelines, plus connections to GitHub and GitLab. | No Git hosting and no build pipelines. The existing toolchain stays in place for that. |
Extension and contract | ||
| Extensions | Atlassian Marketplace with apps from third parties. | No marketplace. What gets added comes from the vendor. |
| Contracting party | Atlassian, plus the respective vendor for each Marketplace app. | One contract, one point of contact, one roadmap. |
| Interface languages | Numerous languages, including German, French and Italian. | German, English, French, Italian. |
Getting started | ||
| Prices | Published, staged by plan and user count. | On request. The figure comes with the quote, once scope and operating model are settled. |
| Before the decision | Trial period with your own instance. | Proof of concept on your own content, with a bounded use case. |
| Import | Migration tooling between its own products. | Import of pages, attachments and page hierarchy from Confluence exports, Notion and Markdown. Jira projects and issues move into Projects. |
The statements about Jira follow Atlassian's public documentation and announcements, as of September 2026. Where something changes, this table changes.
What Collabase does at that point
Three commitments that came before the first feature and that the rest lines up behind.
One product, one vendor
One contract, one point of contact, one roadmap. No marketplace, no third-party plugins, no shared responsibility in operations. When something breaks, there is one number to call rather than three.
The space holds it together
One department, one customer or one project. Documents, tasks, test cases, assets and automations sit side by side in it, with one permission model instead of five.
Quality engineering in the core
Collabase natively integrates the QualityTree framework: requirements, test cases, defects and release approvals sit in the same space as the rest of the work, not in a separate QA tool with its own contract.
Connection and import
A change is rarely a single cut-over date. For running both side by side, the Jira connector is available with its triggers and actions; for the existing content there is the import. Both can be combined while the content moves across.
See the Jira connectorFrequently asked questions
Is Collabase a complete alternative to Jira?
For the project and portfolio side, yes: projects, issues, boards, cycles and workflows are there, along with documentation, asset registry, test management, automation and time tracking in the same product. For pure software development with Git workflows and build pipelines, Collabase is not the intended tool; the existing toolchain stays in place there.
Where is the data held?
In Switzerland, in both operating models. Either as a dedicated instance in a Swiss data centre or entirely on your own infrastructure, including networks without internet access. The data location does not depend on the plan you choose.
Can existing Jira projects be taken over?
Projects, issues and links move into Collabase Projects through the import. Pages, attachments and the page hierarchy come from a Confluence export, from Notion or from Markdown. Exactly what gets taken over is settled during the inventory before the proof of concept.
What does Collabase cost?
Prices are not published on the website. Cloud is billed per user and month, self-hosted per tier and year, staged by user count. The figure comes with the quote, once scope and operating model are settled.
How does a change start?
With a proof of concept: a bounded use case, a real team, a few weeks of runtime, on your own content rather than on demo data. At the end there is a basis for deciding whether and how a change makes sense.
Before a licence is decided, Collabase runs on your content.
A bounded use case, a real team, a few weeks of runtime. For evaluation and migration planning we work with partners who have accompanied comparable undertakings.