What is the App SDK?
The App SDK is the toolkit you use to write your own apps for Collabase. An app adds pages, panels, gadgets and automations to Collabase without changing the core. Backend code runs in isolation, and the interface is made of real Collabase components. The SDK is typed and is coming in Q4 2026.
What an app can do. The places where an app shows up in Collabase and takes part in the work.
App window
Its own app window in the drawer, with a sidebar and its own pages.
Work item panel
Its own panel on the work item, just like tests or meetings.
Gadgets
Gadgets for dashboards and cockpits.
Settings
On three levels: instance wide for admins, per space and per project.
Automation
Your own triggers and actions in the automation builder.
Events
React to events in Collabase, for example when a work item is created.
Incoming webhooks
A CI or another system reports results straight to the app.
Data storage
Collections with queries, key value with expiry, and custom values on work items, pages and projects.
Platform services
Notifications via inbox, mail and digest, audit log, global search and the instance's Collabase AI.
Secure because isolated. An app runs in isolation, and admins decide what it may do.
[ 01 ]Isolated code
Backend code runs in V8 isolates with time and memory limits.
[ 02 ]Isolated interfaces
Interfaces run sandboxed and are rendered with real Collabase components. Dark mode, themes, languages and accessibility come from Collabase.
[ 03 ]Permissions
An app can never do more than the person using it. In the background it acts as its own app user, and only in spaces where it is enabled.
[ 04 ]Control for admins
Admins confirm permissions, hosts and data flows to AI, approve apps per group and enable them per space. Signatures and logs can be inspected, and faulty apps lock themselves automatically.
[ 05 ]Data stays in the instance
Whatever an app stores stays in your instance, backups included.
One command to a running app. The CLI scaffolds the app, starts a local Collabase instance and builds the package for your admin.
The manifest is generated from your code. No app store needed: the admin uploads the package to your instance.
The SDK is typed. Mistakes show up while you write.
# creates a working app
$ npm create collabase-app
# starts a local instance, changes reload instantly
$ npm run dev
# builds the package an admin uploads
$ npm run packagePublic on GitHub. The repositories live in the Collabase organization. The npm packages ship with the App SDK.
Repositories
- Collabase/app-sdk
App contract, SDK, CLI and create-collabase-app
- Collabase/app-examples
Example apps and template
npm packages
Coming Q4 2026- @getcollabase/app-sdk
Pages, server functions, storage, events and automation
- @getcollabase/app-cli
dev, build, package, sign and logs
- @getcollabase/app-contract
Manifest and protocol schemas
- create-collabase-app
Scaffold for a new app
Not published yet. The packages ship from Q4 2026.
Questions about the App SDK
What is the App SDK?
The App SDK is the typed toolkit for writing your own Collabase apps in TypeScript and React. Apps run in isolation and on every instance without changing the core.
When is the App SDK available?
The App SDK is coming in Q4 2026, together with the CLI and the npm packages under @getcollabase. The Collabase/app-sdk repository is already public on GitHub.
Which language do you write an app in?
TypeScript and React. The SDK is typed, so mistakes show up while you write.
How does an app get into an instance?
npm run package builds a package that an admin uploads. The manifest is generated from the code, no app store needed. The admin approves the app per group and enables it per space.
Can an app do more than the person using it?
No. An app can never do more than the person using it. In the background it acts as its own app user, and only in spaces where it is enabled.