We bring automation, projects, knowledge pages, test management and time tracking together in one product. Workflows react to tasks, pages and meetings and run on an instance in Switzerland or on your own infrastructure.
We build and run Collabase at Infometis AG in Zurich. The Automation Engine covers what companies use Make.com for today: workflows built from triggers, conditions and actions, webhooks, schedules and connections to third-party systems. It is one of seven apps and works on the same tasks, pages, registry entries and permissions as the rest of the platform.
Collabase runs as a dedicated instance in a Swiss data centre or entirely on your own infrastructure. Data and stored credentials stay there, and the location is set out in the contract.
Three occasions come up again and again in the conversations we have. Each one hangs on a requirement or a number. If you only connect third-party systems to each other and are not looking for a work platform, a change is rarely the right question.
A requirement from a contract, a regulator or an internal policy sets out where data may be processed. With Make you choose the data centre per organisation, in the EU or in the US. If your requirement calls for Switzerland or for running it yourself, that is where the examination starts.
A workflow creates tasks, changes pages or reads registry entries. In Collabase it does so with the permissions of its own service user, which sees only where it is a member. The more internal data a workflow touches, the more this question matters.
Since 27 August 2025 Make bills in credits, and most actions cost one credit. Anyone running many small workflows therefore plans around the number of executions. Collabase bills per user, not per execution.
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.
| Feature | Make.com | Collabase |
|---|---|---|
Operations and data | ||
| Operating models | Hosted service from Make, with an on-prem agent for connecting local systems. | Dedicated instance in a Swiss data centre or on your infrastructure, also without internet access. |
| Data location | Data centre per organisation in the EU or in the US, which cannot be changed after the organisation is created. | Switzerland, in both operating models and regardless of plan. |
| Vendor | Make, formerly Integromat, part of Celonis since 2020. | Infometis AG, Zurich. |
| Billing | Credits per month. Most actions cost one credit, routers and error handler modules none. | Per user and month. No billing per execution. |
Workflow and connections | ||
| Error handling | Error handler modules with Rollback, Break, Resume, Commit and Ignore. | An error flow per workflow. After a crash a run resumes at the first unfinished step, and runs can be repeated one at a time or up to 100 at once. |
| Integrations | Catalogue of ready-made apps. Make states the current number on its own website. | 1000+ connectors, plus an HTTP plug for any REST API with pagination, retry and auth. |
| AI | Features with an AI provider can use more than one credit. | Agent step with knowledge search, other flows, plug actions and external MCP servers, with approval on request. Each workspace can store its own AI provider with a budget. |
Scope and contract | ||
| Work platform | Standalone tool that connects third-party systems. | One of seven apps. Workflows react to events from tasks, projects, pages, registry, meetings, test management and time tracking. Collabase Automation does not exist without the platform. |
| Contract and payment | Payment by credit card, ACH direct debit or Google Pay, and by invoice on the Enterprise plan. | Infometis AG as the sole contracting party, quote and invoice. |
Getting started | ||
| Pricing | Core, Pro and Teams plans, plus Enterprise. Make states the amounts on its pricing page, and yearly payment is cheaper than monthly. | 20 CHF (Isolated Cloud) or 16 CHF (Self-Hosted) per user and month, with all seven apps. |
| Before the decision | Free plan with 1000 credits per month. | Proof of concept on your own content, with one bounded use case. |
The statements about Collabase reflect our current position. The statements about Make follow Make's public pricing page and documentation, as of October 2026. Where Make does not state a figure there, it appears on Make's website. If something changes, we change this table.
The data location is decided before the features, and for workflows the stored credentials belong with it. Collabase runs as a dedicated instance in a Swiss data centre, operated by us, or entirely on your infrastructure. Stored credentials can no longer be read once saved, only replaced, and are redacted in run data. If you want, you connect HashiCorp Vault or Azure Key Vault, and Collabase then stores only a reference.
Make is a hosted service. Each organisation chooses a data centre in the EU or in the US when it is created, and the choice cannot be changed afterwards. For systems in your own network there is the on-prem agent. Whether that is enough for your requirements depends on whether Switzerland is required or the EU will do.
Three decisions came before the first building block, and the rest is aligned to them.
Workflows react to tasks, projects, pages, registry entries, meetings, comments, time tracking and time. Webhooks, schedules with cron and time zone, and a public chat page for a flow come on top.
Each workspace has its own service user. It sees and changes only where it is a member, inherits nothing from public spaces or groups and cannot sign in. The roles in a workspace are admin, editor and viewer.
Draft and publish are separate, the version history can be restored, and every change can be traced per workspace. In sensitive workspaces a second admin approves, and Git sync carries workflows from development to production with diff, releases and rollback.
With webhooks and the HTTP plug we connect Collabase to existing services, including those that keep running in Make while workflows move across. We rebuild one of your existing workflows in the proof of concept. Which ones are suitable, we establish in the stocktake.
For workflows between Collabase and third-party systems, yes: triggers, branches with AND and OR rules, loops, sub-flows, a code step in TypeScript, webhooks and schedules are there, along with agent steps using AI. Collabase Automation exists only together with the platform, not as a standalone tool. The feature table shows row by row where the boundary runs.
In Switzerland, in both operating models. Either as a dedicated instance in a Swiss data centre or entirely on your own infrastructure. Stored credentials can no longer be read and are redacted in run data, and on request they sit in HashiCorp Vault or Azure Key Vault.
Yes. Self-hosted, Collabase runs entirely on your infrastructure, including in networks without internet access. Connections to cloud applications need access to the outside; which of them you need, we establish before the proof of concept.
1000+ connectors are available. For everything else there is an HTTP plug for any REST API, with pagination, retry and auth, plus webhooks. Your own plugs are built with the Plug SDK, which arrives in Q4 2026. Make keeps a large catalogue of ready-made apps; whether your systems appear with us, we check before the proof of concept.
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, and there is no billing per execution. The quote states the total amount.
We rebuild one of your workflows in Collabase in the proof of concept, on your own systems and with your real connections. Which scenarios are suitable, we establish in the stocktake before the start.
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.
One bounded use case, a real team, a few weeks of runtime. We rebuild one of your weekly or monthly processes as a workflow, on your own systems.
