The Swiss collaboration platform
Your data stays where you put it. Collabase runs on your infrastructure and stays there.
Collabase is built in Zurich and operated in Switzerland. Your content is therefore subject to Swiss law rather than the US Cloud Act. Processing meets the requirements of the nFADP and the GDPR.
Your data stays in Switzerland
Your content is subject to Swiss law. In managed operation it sits encrypted on servers in a Swiss data centre, in self-hosted operation you choose the location yourself. In the standard setup it stays out of reach of the US Cloud Act. Connect an external AI provider and its terms apply to the content you send there.
AI only once you switch it on
Collabase AI is optional and enabled per space. You connect the provider of your choice with your own key, whether OpenAI, Anthropic, Gemini or Infomaniak in Switzerland. Without activation every piece of content stays in your environment.
Evidence for the compliance review
Information security is certified to ISO 27001 and processing meets the nFADP and the GDPR. The documents are ready before you ask for them.
A product that takes the shape of your process. Without a line of code.
The space holds it together: a department, a client or an initiative. What sits inside it and how it moves is up to you — through your own fields, your own status sequences and your own flows.
Knowledge
Requirements, runbooks and decisions in the same place as the work, with history and approval.
Work items
From backlog through cycle to sign-off, with effort recorded on the item instead of in a second spreadsheet.
Quality
Test cases on the requirement, runs with environment and result, findings as a work item in the same cycle.
Carried by
Data and flows
Directories of your own for whatever your process keeps, and automations that hang off them.
Carried by
Adapted to your processes.
Three levers, and no more are needed. All three are settings in the product, not an add-on and not custom development.
Your own fields and object types
A contract gets term, notice period and owner as fields of its own. A work item gets, per type, the fields it actually needs.
Your own status sequences and approvals
Which states exist, who may move an item on and who has to agree first sits on the item type. Multi-stage, with roles and a deadline.
Your own flows
What happens after an event you assemble in Automation: create tasks, set reminders, trigger external systems.
One product, one vendor
Collabase is a closed product. One contract, one point of contact, one roadmap. A marketplace, third-party plugins and shared responsibility in operations do not apply. Operation and further development sit in one place.
What is created in one tool is already waiting in the next.
Roles rarely divide the work as clear-cut as an org chart suggests. What counts is the handover: a requirement finding its test case, a decision finding its page, an event finding its trigger.
From requirement to evidence
Test cases and runs hang directly off the story. A deviation found in a run becomes a task in the same cycle — in the same tool.
From decision to documentation
What was decided sits as a page in the same space as the work, in the tree rather than in an attachment. The verified marker shows which page was reviewed last.
From event to deployment
Workflows without code, triggered by events from every app. From a status change to a deployment — automatically.
This is what the work looks like. Two views your team opens every day.
Task, history and discussion in one view
Type, cycle, estimate and owner sit on the left, the full history on the right. Every status change stays traceable, and the discussion lives on the task instead of in a chat.
- Story, bug and custom types
- Cycles and estimates in story points
- Activity history with every status change
Documents that are reviewed and kept current
Pages sit in a tree everyone understands. A document can be marked as verified so it is clear what to rely on. Tables, callouts and diagrams are part of the editor.
- Page tree with sub-pages
- Mark a page as verified
- Tables, callouts and diagrams
Your own instance, in a Swiss data centre.
No shared tenant: Collabase runs for you on dedicated servers in Switzerland. We take care of updates, backups and security patches, and access stays with you. This is the route most customers choose.
Dedicated servers in Switzerland, no shared tenant
Updates, backups and security patches are on us
A named contact, response within 24 hours
Collabase also runs on your own hardware. Including networks with no internet access.
If you want to run the instance yourself, you run it yourself. Same capabilities, same codebase, and the keys stay with you. Docker or Kubernetes, sign-in through OIDC, LDAP or SAML, PostgreSQL as the store.
The platform decision is coming up in the next few years. Made early, it stays a choice.
Two developments put the topic on the agenda, however well today's setup runs.
The trigger comes from outside
Maintenance windows end, operating models get switched, licence terms change. The timing is rarely in your own calendar. Decide early and you still decide for yourself.
Where you operate is settled once
Where content lives is decided with the platform and rarely changes afterwards. Keep it in Switzerland and Swiss law applies rather than the US Cloud Act, and processing meets the nFADP and the GDPR. That choice is open at the start of a move, not in the middle.
Two operating models, the same seven apps. The difference is in operations and sign-in.
Isolated Cloud runs as your own instance in a Swiss data centre, Self-Hosted on your hardware. Both come with SSO, LDAP/AD, audit logging and security policies. We calculate the price for your user count.
Both operating models side by side Isolated Cloud and Self-Hosted compared feature by feature.
Go to the pricing comparisonWe are migration specialists. We handle the move.
We get your content out of the system you have today, whichever one that is. Pages, work items, attachments, permissions and the links between them. You get a named contact, a parallel run and a way back if something jams.
Taking stock
We look at what you have: areas, projects, permissions and the quirks that grew over the years. The result is a clear list of what gets migrated, what should be reorganised and what can stay where it is.
Import and parallel run
The content moves across, structure and links included. Both systems run side by side for a while, so the switch happens step by step.
Cutover
Sign-in runs through your directory and the old system goes out of service. We are there on the day, with a fallback in case something jams.
Hand in hand You are not moving on your own. We plan it with you, carry it out and stay reachable after the cutover.
Find a partnerWhat we are building Collabase for. And what we are not.
A handful of commitments came before the first line of code. They explain why the platform looks the way it does, and why it is run the way it is.
Read our visionSelf-hosted, with the full feature set.
One product with every capability, not a kit
Bootstrapped, Swiss-owned and free of investors
Customers help decide what comes next
Twenty-seven years of running projects and securing quality. Poured into a platform.
Collabase is a product of Infometis AG. Since 1998 we have run projects and secured quality for Swiss banks, insurers and public administrations. The method, the craft and the experience gathered along the way now sit inside the platform.
Service and product from one hand: the same people who run your initiative and secure your quality build the tool for it and operate it.
More about InfometisConsulting since
1998
Disciplines
Project management and quality engineering
Where Collabase comes from
Collabase started in late 2024 as an open-source project by Brian Trepto for knowledge management and collaboration. Over the following months the single tool grew into a platform. Infometis AG brought sales, support and a roadmap with it; since then Collabase has been proprietary software of Infometis AG.
The founding decisions — running it in your own house, one product instead of a construction kit, self-funding — come from that time and still hold unchanged.
Our vision
100 % Swiss. Based in Zurich. Built by the lake, run in Switzerland.
Collabase is built in Zurich, operated in Switzerland and made by people who grab a coffee by the lake between two meetings. No offshore development, no follow-the-sun support across five time zones. When you call, someone in Zurich picks up.
Meet the teamNotes from development, operations and customer conversations.
Data sovereignty, running on your own hardware, moving off tools that grew over years: the questions from our conversations, answered at length.
The CLOUD Act and data sovereignty: why data residency in Switzerland is not enough
Data residency in Switzerland determines where your data sits. It offers no protection against the US CLOUD Act, because that law attaches to control over the data, not to its location. In June 2026 the European Commission translated this distinction into a four-level assessment framework and showed which evidence regulated companies will have to produce.
Organising team documents without building a second file store
In most teams, files hang off pages and tasks, and after a year nobody knows where. A second file store with its own folder structure brings copies and duplicate permissions with it. The Collabase Documents app shows every attachment in one place and sorts it into folders, without any file changing its location or its permissions.
Atlassian Data Center is being retired. What you need to know now.
Atlassian has announced end of life for its Data Center products. From 28 March 2029, Jira Software, Jira Service Management, Confluence, Bamboo, Crowd and the associated Marketplace apps run in read-only mode. For companies that rely on these tools, that sets a window of roughly three years.
Questions that come before the decision
Eight questions that come before the decision.
What is Collabase?
Collabase is a Swiss collaboration platform with seven apps in one product: documentation, projects, intranet, registry, test management, automation and time tracking. They all sit in the same space instead of in separate tools. It runs in a Swiss data centre or on your own hardware. It is built in Zurich by Infometis AG.
Can I try Collabase before deciding?
Yes, in a proof of concept. Within days we set up an instance with your own content, not a demo database. You test it against real workflows. The instance runs in a Swiss data centre or on your hardware.
Where is Collabase data stored?
In Switzerland only. In the Isolated Cloud it sits on dedicated servers in a Swiss data centre; in self-hosted operation you choose the location yourself. In both models it stays out of reach of the US Cloud Act and meets the nFADP and the GDPR. Activate an external AI provider and the content you send there leaves that scope.
Where is our content processed once we enable the AI?
With the provider you connect yourself. Collabase AI is optional and enabled per space, with your own account and your own key. To keep processing in Switzerland, choose Infomaniak; OpenAI, Anthropic and Gemini process on their own infrastructure under their own terms. Without activation Collabase processes no content through AI.
Can I migrate content from Confluence, Jira or Notion to Collabase?
Yes. The importer takes over pages, attachments and the page hierarchy from Confluence exports as well as from Notion and Markdown. Jira projects, tickets and links move into Collabase Projects. We map permissions and space structures together with you.
How much effort is installing Collabase?
A compose file is enough for the first instance. On a prepared Linux server Collabase runs within an hour. For production with SSO, backups and monitoring we plan a full day.
What does Collabase cost?
Billing is per user and month, staged by team size. All seven apps and all integrations are included. We name the amount in the quote.
How do I get my data out of Collabase again?
Your data sits in PostgreSQL and can be exported as JSON at any time; attachments sit in S3-compatible storage. The export runs through the REST API. On exit we additionally deliver a complete dump in open formats.