01
The data has to sit in Switzerland
awork runs in the cloud on Microsoft Azure in Frankfurt. When a requirement from a contract, a regulator or an internal policy calls for Switzerland, that is the first question rather than the last.
What Collabase covers
We build and run Collabase at Infometis AG in Zurich. The platform covers the project and task work companies use awork for today, and sets knowledge pages, test management, an asset registry, automation and time tracking alongside it. 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, including in networks without internet access. In both cases the data location is written into the contract.
Alternative
When a change is worth examining
Three occasions come up again and again in the conversations we have. Each one hangs on a requirement or a number. If none of them applies, a change is rarely the right question.
02
Operations belong in house
awork is a cloud service. Anyone who has to operate on their own infrastructure, in a closed network or under their own operational responsibility, needs a product that is delivered that way.
03
The scope grows beyond tasks
Test cases, an asset registry and documentation that carries more than a project note join projects and time tracking. Each additional 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 withawork
| Feature | awork | Collabase |
|---|---|---|
Operations and data | ||
| Operating models | Cloud, hosted on Microsoft Azure Germany in Frankfurt. No self-hosting. | Dedicated instance in a Swiss data centre or on your own infrastructure, including without internet access. |
| Data location | Germany (Azure Germany, dedicated tenant). Support and communication services partly in third countries. | Switzerland, in both operating models. |
| Vendor | awork GmbH, Hamburg. | Infometis AG, Zurich. |
Scope | ||
| Knowledge pages | awork Docs, lightweight, tied to projects. | Docs, with pages, page hierarchy, templates and spaces. |
| Projects and issues | Tasks in lists, boards and a timeline. The core of awork. | Projects, with boards, cycles and custom workflows. |
| Test management | Not included. | Test Management, in the same product, built around the QualityTree framework. |
| Asset registry | Not included. | Registry, in the same product, with custom schemas and relationships. |
| Automation | Automations, included in the product. | Automation, in the same product, with 1000+ connectors. |
| Time tracking | A core function, included in the product, with capacity planning. | Time, in the same product, on tasks and projects. |
| Software development | Not a focus. Connections to GitHub and GitLab through awork Connect. | Stays in your existing toolchain. Collabase brings no Git hosting and no build pipelines. |
Extensions and contract | ||
| Extensions | awork Connect for integrations, an open API, an n8n connector. No app marketplace. | We develop extensions ourselves. There is no marketplace. |
| Contracting party | awork GmbH. | Infometis AG as the sole contracting party. |
| Interface languages | German, English. | German, English, French, Italian. |
Getting started | ||
| Pricing | Published publicly, from EUR 5 per user per month, tiered by plan. | 20 CHF (Isolated Cloud) or 16 CHF (Self-Hosted) per user and month, with all seven apps. |
| Before the decision | 14-day free trial with a dedicated instance. | Proof of concept on your own content, with one bounded use case. |
| Import | Import from Trello, Asana and Excel. | 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 awork follow awork's public documentation, 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.
awork is a cloud service and runs on Microsoft Azure in Frankfurt, by its own account in a dedicated tenant; support and communication services sit partly in third countries. For a requirement that calls for Switzerland, or for operating inside your own network, that is where the examination starts.
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
The route from awork to Collabase
Tasks, projects and recorded time come across through the awork export, documentation through Markdown. What can be carried over and what is set up afresh, we establish on your own data before the proof of concept starts.
Frequent questions
Is Collabase a complete alternative to awork?
For project and task work, yes: projects, tasks, boards, cycles, workflows and time tracking are there, along with documentation, asset registry, test management and automation 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.
Can Collabase be operated in house?
Yes. 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.
Can existing awork projects be taken over?
Tasks, projects and recorded time come across through the awork export, pages and documentation through Markdown. We establish what exactly comes with it on your own data, before the proof of concept.
Is there time tracking like awork's?
Time is one of the seven apps and runs in the same product, on tasks and projects. Capacity and utilisation planning are not the same scope; what you need of it belongs in the review that precedes 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.