Automated processes, on your own infrastructure.
Triggers, conditions and actions in a visual builder, connected to Slack, Teams, GitHub, Jira and more. Without monthly task limits, and the data stays inside your network.
Overview
In short.
Collabase Automation is the automation engine of the Swiss platform Collabase. Triggers, conditions and actions are built in the visual builder, with native access to test runs, Docs pages and Registry records. Execution happens on your own infrastructure.
- Without task limits
- Unlimited runs, no billing per executed step
- On your infrastructure
- Self-hosted or in the Isolated Cloud, without passing data to third parties
- Native to Collabase
- Access to test runs, Docs pages and Registry records without API keys
- 1000+ integrations
- From Bexio to Jira and GitHub, plus webhooks and REST API
When automation pays off
When recurring steps turn into a full-time job.
Reports are clicked together by hand on Friday afternoon. Alerts for critical events travel by email and drown in the inbox. Data moves between two systems by copy and paste. The Automation Engine takes over those steps, and the processing runs on your own infrastructure.
A recurring weekly report costs two to four hours every week.
Data exchange between two internal systems runs on manual export and import today.
External automation services are out of the question for compliance reasons, because data would leave the company network.
Value
What you gain.
Features
Everything a workflow needs, on your own infrastructure.
Visual no-code builder
Triggers from all apps
Conditions with branching and abort
Native Collabase actions
Native actions without API keys
Slack, Teams, GitHub, Jira and more
No monthly task limits
Runs on your own infrastructure
Data stays in your own network
Complete node reference by category
Developer Platform
Your own triggers and actions, with the App SDK from Q4 2026.
With the App SDK you write apps in TypeScript and React that bring their own triggers and actions into the automation builder and react to events in Collabase.
To the App SDKUse cases
Where it pays off.
Alerts
Notifications on critical events, escalation after a set time.
Recurring reports
Weekly reports, key figures and status overviews on schedule.
Data synchronisation
Matching between internal systems without external staging.
Approval processes
Multi-stage approvals with reminders and escalation.
Ecosystem
The Automation Engine is one app of seven.
It starts test runs in Test Management, creates records in Registry, publishes pages in Docs and creates tasks in Projects, without API keys, because it uses the logged-in session. Every app shares login, permissions and data. One contract, one deployment, one contact.
- DocsThe wiki for your team's knowledge, with version history and export to PDF, DOCX and Markdown.
- ProjectsAgile project management for product and engineering teams, with cycles and releases.
- IntranetYour organisation's internal home page, with news and a people directory.
- RegistryAsset and infrastructure management for IT teams, with custom fields per directory.
- Test ManagementQuality assurance in the same space, with test cases and runs attached to the task.
- AutomationWorkflows without code, triggered by events from any app.
- TimeTime tracking and billing, directly on tasks and projects.
Operations
Operations and data sovereignty.
Where the data sits is decided by the operating model, not by the small print.
Swiss hosted
Operated on Swiss public cloud at Infomaniak, one isolated environment per customer. Content is processed in Switzerland only, apart from the upstream web application firewall.
Self-hosted
Runs on your own infrastructure. Full control over the data, no access from outside.
revFADP & GDPR
Data processing agreement included. Compliant with the revised Swiss data protection act and the GDPR.
Questions from first conversations.
Where do the automations run?
On your own infrastructure, self-hosted or in the Isolated Cloud. Execution does not leave your environment and is not handed to a third party.
Do we need API keys for actions inside Collabase?
No. Test runs, Docs pages and Registry records can be addressed natively. You only need a key for external systems that you connect yourself.
Which systems can be connected?
1000+ integrations, from Bexio to Jira and GitHub. Anything not on that list can be connected through webhooks and the REST API.
How is a flow built?
In the visual builder, from three parts: a trigger, conditions and actions. Triggers are events from any app, such as a new record in Registry or a failed test run.
Automate the process that costs you the most time.
In the proof of concept we rebuild one of your real weekly or monthly processes as an automation, on your own system and with your real connections.Pricing: from 16 CHF per user and month