01
The end of Jira Data Center
Atlassian ends Jira Data Center on 28 March 2029, and sales to existing customers end on 30 March 2028. If you run Jira on your own infrastructure today, you will choose a successor before then.
What Collabase covers
We build and run Collabase at Infometis AG in Zurich. The platform covers the project and portfolio side of what companies use Jira and Confluence for today, plus test management, an asset registry and time tracking. We deliver all of it in one product and under one contract.
Collabase runs as a dedicated instance in a Swiss data centre or entirely on your own infrastructure. In both cases the data location is written into the contract and does not depend on the plan you choose.
Alternative
When a change is worth examining
Three occasions come up again and again in the conversations we have. Each one hangs on a date or a number. If none of them applies, a change is rarely the right question.
02
Requirements on data location
A requirement from a contract, a regulator or an internal policy sets out where your data may be held. We clarify that requirement with you early, because it shapes everything that follows.
03
Several tools side by side
Projects in one tool, documentation in a second, test cases in an extension, time tracking in a third. Each tool brings its own contract, its own invoice and its own permission model.
The features side by side
The table describes each feature in one sentence. Where Collabase does not cover something, we write that into the cell the same way we write the other side.
Compare withJira
| Feature | Jira | Collabase |
|---|---|---|
Operations and data | ||
| Operating models | Cloud. Data Center runs until 28 March 2029. | Dedicated instance in a Swiss data centre or on your own infrastructure, including 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 regardless of plan. |
| Vendor | Atlassian Corporation, publicly listed, headquartered in the USA 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, built around 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 relationships. |
| 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. | Stays in your existing toolchain. Collabase brings no Git hosting and no build pipelines. |
Extensions and contract | ||
| Extensions | Atlassian Marketplace with apps from third parties. | We develop extensions ourselves. There is no marketplace. |
| Contracting party | Atlassian, plus the respective vendor for each marketplace app. | Infometis AG as the sole contracting party. |
| Interface languages | Numerous languages, among them German, French and Italian. | German, English, French, Italian. |
Getting started | ||
| Pricing | Published publicly, tiered by plan and number of users. | 20 CHF (Isolated Cloud) or 16 CHF (Self-Hosted) per user and month, with all seven apps. |
| Before the decision | Trial period with a dedicated instance. | Proof of concept on your own content, with one bounded use case. |
| Import | Migration tools between Atlassian's own products. | We import pages, attachments and page hierarchies from Confluence exports, Notion and Markdown. Jira projects and issues move into Projects. |
The statements about Collabase reflect where we stand today. The statements about Jira follow Atlassian's public documentation and announcements, as of September 2026. When something changes, we change this table.
Operations and data
Operations and data in detail
Data location is settled before features are. Collabase runs either as a dedicated instance in a Swiss data centre, operated by us, or entirely on your own infrastructure, including in networks without internet access. In both cases the data sits in Switzerland regardless of the scope you choose, and the location is written into the contract.
With Jira, data location depends on the plan and the product: data residency for Switzerland is available on the Standard, Premium and Enterprise plans for the core products, and for marketplace apps it has to be checked app by app. Data Center runs until 28 March 2029, and sales to existing customers end on 30 March 2028. Anyone working on their own infrastructure today and intending to stay there will choose a route before then.
Collabase
Three ground decisions behind Collabase
Three decisions came before the first feature, and everything else follows from them.
One product from one vendor
You have one contract with us, one point of contact and one roadmap. We develop extensions ourselves. Operations and development therefore sit in the same place.
One space for one undertaking
A space stands for a department, a client or a project. Documents, tasks, test cases, assets and automations sit side by side within it and share one permission model.
Quality engineering at the core
We have integrated the QualityTree framework natively. Requirements, test cases, deviations and approvals sit in the same space as the rest of the work.
Apps & integrations
Jira connection and import
In most cases Collabase runs alongside Jira for a while. For that phase we provide the Jira connection with its triggers and actions, and for the later move the import. The two can be combined, as long as the content travels.
See the Jira connectionFrequent 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. The feature table on this page shows row by row where the boundary runs.
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 in networks without internet access. 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. We settle what exactly is carried over with you in the review that precedes the proof of concept.
How does Collabase differ from Confluence?
Confluence is a separate product with its own licence alongside Jira. In Collabase, Docs is an app inside the same product: pages sit in the same space as issues, test cases and assets and share one permission model. We take existing content over from a Confluence export, with pages, attachments and page hierarchy.
Can Collabase be used without internet access?
Yes, when self-hosted. Collabase runs entirely on your own infrastructure, including in closed networks. Connections to cloud applications need a route outwards; we clarify which of them you need before the proof of concept.
What does Collabase cost?
Isolated Cloud costs 20 CHF per user and month, billed monthly. Self-Hosted costs 16 CHF per user and month, billed yearly. All seven apps are included. The quote states the total amount.
How does a change begin?
With a proof of concept: one bounded use case, a real team, a few weeks of runtime, on your own content rather than on demo data. What comes out of it is a basis for deciding whether and how a change makes sense.
Before a licence is decided, Collabase runs on your content.
One 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.