Apps
Build any app your organization needs and enable it inside a context: it inherits the context's boundary and sees only what its groups see. Ship it with your AI coding tool, or install one from the store.
The SweetHive App SDK comes with a developer guide your AI coding tool can follow: the handshake, the scoped API and the publishing steps. Describe what you want; it writes the app, and you register it in SweetHive.
See the quickstartDon't build what already exists. Browse ready-made apps and add one to a context in a click. It goes live scoped: no integration project, no data migration.
Browse the storeApps are built with the SweetHive App SDK. It comes with a developer guide written to be handed to your AI coding tool: the launch handshake, auth, the scoped data API, and how to test and publish, in one file. You describe the app, it writes the code, you review and ship.
In SweetHive, open Developer → Apps and choose Register app. Pick the type (embedded in a context, or external on its own URL), the URL and the capability: read, read + draft, or read + post. You get a client ID and a client secret, shown once.
Download the SDK developer guide from the same page and give it to your AI coding tool. The SDK runs the embed handshake (external apps get a signed launch link) and hands your app a short-lived token scoped to the context and to the person using it.
Set the app to Active to submit it for review. Once approved it appears in the store, and it can be added to any context from the context's Apps card (Add app).
The App SDK is in early access and not yet published on npm: ask us for access.
Apps are not integrations bolted on the side. When you add one to a context, it inherits that context's boundary: every call is bounded by the install's context and by what the person using the app can see, and it can't reach across the tree without an explicit share. The same scoping law that governs people and agents governs apps, so IT can enable them without opening the whole hive.
An app's reach is the context it's installed in ∩ the live visibility of the person using it, enforced server side through a short-lived token. Its capability (read, draft, post) is fixed at registration.
Add an app to one context at a time. Different contexts can run different apps, or the same app installed separately, each with its own scope and settings.
An app posts only into its install's context, addressed to groups, and its first post needs the user's confirmation. Disable an app and every install's token stops working.
Browse apps built by SweetHive and its partners, and add one to a context in a click. Installed apps enter scoped: they see exactly what that context's groups see, and nothing else. Build once, get it approved for the store, and every hive can add it.
Custom apps, scoped to the contexts they run in, built with your AI coding tool or installed from the store.
Get a demo