Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

Project and Portfolio Management

Projects your team actually keeps current.

Cycles, sprints, workload, roadmap and portfolio sit in the same space as the documentation.

Why now

The status gets written three times. Once in the work item, once in the deck, once in the report.

The work sits in the item list, the roadmap in a presentation, the weekly report in a document next to it. Every week the same numbers are moved by hand into a second shape, and the workload lives in a spreadsheet exactly one person maintains.

01

In the sprint review someone looks for the page behind the story in a second tool.

02

Capacity planning lives in a spreadsheet beside the initiative.

03

The report and the board show different numbers.

Capabilities

What shortens Monday morning. Everything in the same space, nothing behind an export.

01

Cycles and sprints

Estimate, capacity and burndown hang off the same initiative. What gets estimated in planning shows up as a number in the review.

02

Portfolio across initiatives

Several projects side by side, with status, ownership and open points. The view comes out of the work items, not out of a second set of records.

03

Roadmap from real work items

The timeline reads the items your team moves anyway. When a cycle shifts, the roadmap shifts with it.

04

Status report as a flow

Weekly report and status update come out of the cycles as an automation and land as a page in the space or a message in the channel.

One day

Monday morning, sprint planning. From the backlog to the published status, without switching tools.

Platform

The apps behind it. All in the same space, no second tool.

Projects carries the work items, Docs holds the knowledge beside them, Time records effort on the item itself, and Automation takes the repetition off your hands.

Integrations

Connected where it counts. Connections from everyday project work.

See all integrations

Commits on the work item, effort into accounting, meetings into the calendar, updates into the channel.

Operations

One product, one vendor. Every module belongs to it.

Work items, documentation, time tracking and automation belong to the same product. There is no add-on for the roadmap and no second tool for the report; what a project lead needs sits in the same space as the work.

One contract, one point of contact.

All modules from one vendor, with nothing extra to buy.

Operated in a Swiss data centre or on your own hardware.

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.

Read the sovereignty promise

Questions from project leads. What comes up first in an initial conversation.

What is project and portfolio management in Collabase?

Cycles, sprints, workload, roadmap and portfolio in one system. The views read from the work items the team moves anyway, not from a second set of records.

How many initiatives can run in parallel?

The number of spaces and initiatives is not capped. The portfolio view brings them together; which ones appear is governed by permissions.

Can we bring content over from Jira and Confluence?

We take content over as part of the migration; we set the route against your actual content.

How does capacity planning work across teams?

Workload hangs off people, not off a single initiative. Anyone planned into two cycles appears in both with the same available time.

Is there a calendar or timeline view?

Cycles carry a start and an end, and the roadmap places them on a timeline.

Can we define our own flows?

Yes. Status sequences, approvals and recurring steps are built in Automation, without code.

Other disciplines in the same system.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.