01
The end of Confluence Data Center
Atlassian ends Data Center on 28 March 2029, and sales to existing customers end on 30 March 2028. If you run Confluence 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. Docs covers what companies use Confluence for today: pages, page hierarchies, templates and shared storage in spaces. Alongside it, in the same product, sit projects, test management, an asset registry, automation and time tracking.
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. Knowledge pages in particular tend to carry the content that requirement is about.
03
Knowledge kept apart from the work
The page describes a process, the issue behind it sits in a second tool, the test case in an extension. 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 withConfluence
| Feature | Confluence | 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 | ||
| Knowledge pages | Pages, page hierarchy, templates and spaces. | Docs, with pages, page hierarchy, templates and spaces. |
| Projects and issues | Through Jira, a separate product with its own licence. | Projects, in the same product and the same space as the pages. |
| Test management | Not included. It runs through Jira and apps from the Atlassian Marketplace. | Test Management, in the same product, built around the QualityTree framework. |
| Asset registry | Not included. Assets sit in Jira Service Management. | Registry, in the same product, with custom schemas and relationships. |
| Automation | Automation, 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 | Not a focus of Confluence. It runs through Jira, Bitbucket, GitHub or 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. |
The statements about Collabase reflect where we stand today. The statements about Confluence 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 Confluence, 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. Pages, 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 pages that describe them.
Apps & integrations
Import from Confluence
The route out of Confluence runs through the export. We take pages, attachments and the page hierarchy from it, and the same goes for Notion and Markdown. We establish what exactly comes across on your own export, before the proof of concept starts.
Frequent questions
Is Collabase a complete alternative to Confluence?
For knowledge work, yes: pages, page hierarchy, templates and spaces are all in Docs, along with projects, test management, asset registry, 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 Confluence pages be taken over?
Pages, attachments and the page hierarchy move into Docs from a Confluence export. Content from Notion and from Markdown comes across the same way. We establish what exactly comes with it on your own export, before the proof of concept.
How does Collabase differ from Jira?
Jira is a separate product with its own licence alongside Confluence. In Collabase, Projects is an app inside the same product: issues, boards and cycles sit in the same space as the pages that describe them and share one permission model.
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.