App Store
The App Store is where you discover and manage the Apps available on your Operaide instance. It shows every App that has been published to the built-in registry — both the Core Apps that ship with the platform and any custom Apps that developers have added.
You access the App Store from App-Store in the bottom section of the sidebar.
What You See
The App Store displays Apps as a card grid. Each card shows:
| Element | Description |
|---|---|
| Name | The package name of the App (e.g. operaide-app-core-operaide-chat) |
| Description | A short summary of what the App does |
| Error badge | A red indicator if the App has compatibility issues (hover for details) |
| Actions | Buttons at the bottom of the card: Details, Use as Template, and Deploy |
··· menu | A dropdown in the top-right corner of the card with additional actions (e.g. legacy operations) |
The organization name displayed in the header confirms which organization's App Store you are viewing.
Core Apps
Every Operaide installation ships with a set of Core Apps (op-core-*). These are reference implementations maintained by the Operaide team and automatically published to the built-in registry when the instance starts. They are available in the App Store immediately after provisioning.
Core Apps available out of the box include:
| App | Purpose |
|---|---|
operaide-app-core-operaide-chat | Full-featured chat with streaming, file handling, web search, and assistant management |
operaide-app-core-basic-chat | Simpler chat with a configurable system prompt |
operaide-app-core-knowledge-chat | Chat with knowledge base integration |
operaide-app-core-websearch | Web search functionality |
operaide-app-core-blank-app | Empty scaffold for developers starting a new App |
How New Apps Reach the Store
Publishing is handled by developers. There are two paths, and both result in the App appearing in your App Store:
Path 1: npm publish (standard)
A developer publishes a packaged App to the instance's built-in npm registry:
npm publish
The developer's .npmrc file points to your instance's registry endpoint (https://<your-instance>/api/v1/registry) and includes an API key for authentication. The user behind the API key must hold NPM Registry Publisher (or a role that implies it, such as App Developer, App Manager, or System Administrator); otherwise the registry returns 403 Forbidden. Once published, the App appears in the App Store for all organizations on that instance.
If a requested package is not in the local registry, Operaide forwards the request to an upstream registry. The default upstream is https://registry.npmjs.org. To configure a private upstream (Verdaccio, GitHub Packages, npm Enterprise, or another Operaide instance), see Upstream NPM Registry.
Path 2: Direct deploy (development)
During active development, a developer can upload source files directly:
npm run deploy
This sends files to the /api/v1/deploy-reaktor endpoint. The App appears immediately and is automatically installed in the developer's organization. This path is typically used on development instances, not production.
Path 3: Export and Import via UI
You can transfer an App between two Operaide instances that do not share a registry. No npm CLI, tooling, or API key is required.
Export on the source instance:
- Open the App Store.
- Click Details on an App card.
- In the drawer, click Export as .tgz.
- The browser downloads
<packageName>-<version>.tgz.
Import on the target instance:
- Open the App Store.
- Click Import App in the store header.
- Select the
.tgzfile from the export step.
A success notification confirms the import and the App appears in the store.
The file format is the standard npm tarball with all files under a package/ root. Files produced by Open in Studio (named <app>@<version>.tgz, flat layout) are Studio artifacts and are rejected by the import with a clear error.
Version collisions: the import rejects a version that already exists on the target instance. Bump the version on the source, re-publish, and re-export to bring in an updated build.
Required permissions:
| Action | Permission |
|---|---|
| Export | Read from NPM Registry |
| Import | Publish to NPM Registry |
On a production instance, the typical workflow is: a developer publishes the App to the registry (Path 1), and you install it from the App Store. The developer does not need direct access to the production instance beyond their API key.
Getting Updated App Versions
When a developer publishes a new version of an existing App, the updated version appears in the App Store automatically. The App Store always shows the highest version that is compatible with your platform version.
Compatibility is determined by the @operaide/aktor peer dependency declared in the App's package.json. If a new version requires a newer platform version than what you are running, it will not appear in the store until the platform is upgraded.
Permissions
Access to the App Store is controlled by the following permissions:
| Permission | Description | Default roles |
|---|---|---|
| Access App Store | View available Apps in the store | App Developer, App Manager |
| Install Apps | Install Apps from the store into the organization | App Manager |
| Download App Code | Download App source code as a .tgz archive | App Developer |
| Read from NPM Registry | Read package metadata and tarballs via the registry (npm install) | NPM Registry Reader, NPM Registry Publisher, App Developer (by implication) |
| Publish to NPM Registry | Publish new package versions via the registry (npm publish) | NPM Registry Publisher, App Developer (by implication) |
Only users with the App Manager role can install Apps. If you need to install an App, ensure your account has this role assigned.