> ## Documentation Index > Fetch the complete documentation index at: https://docs.spitzli.cloud/llms.txt > Use this file to discover all available pages before exploring further. # Managed Apps > Operate a dedicated application while configuring its features in the application's own administration. Managed Apps operates dedicated applications assigned to a Spitzli Cloud project. **Tabularium is an app in Managed Apps**, not a separate registry-management plugin. Each customer gets their own Tabularium instance and manages its registry through that instance. > [!NOTE] > > The initial Managed Apps integration operates existing applications provisioned through Hosting. It does not yet provision a new instance, database or domain from the plugin. The host adapter and plugin must be installed together; catalog publication alone does not activate them. On 18 October 2026, the production host adapter, database policy and developer alpha were deployed together, and the existing Spitzli Cloud Tabularium app was assigned to its existing project. Other projects still require an explicit installation grant and app binding. ## Operate the app in Spitzli Cloud * See the assigned application, deployment status and current operation. * Start, stop or restart the existing application through Hosting. * Open its Hosting detail page for infrastructure administration. * Open the customer's dedicated Tabularium instance. Stopping an application uses Hosting's existing lifecycle and retains its data. Start, stop and restart require current application and subscription revisions and a write-capable project session. The plugin cannot select another customer's project, pass arbitrary hosting commands or obtain database, cluster or registry credentials. ## Recorded protocol-v1 pilot The October 2026 protocol-v1 pilot recorded the existing Tabularium app and its trusted app/Hosting links. The signed read action was verified with an authenticated operator session; the same app read from a different project was denied. No stop or restart was performed on the live registry during verification. ## Configure the registry in Tabularium Use the dedicated Tabularium administration for registry branding, kinds, manifest fields, submissions, providers and users. Spitzli Cloud does not duplicate those screens or request a Tabularium administrator token for Managed Apps. The operator binds each managed app to its actual project and verified HTTPS origin. A plugin installation does not grant access to unassigned apps. Existing registry data and settings stay in place when an already deployed Tabularium app is connected. ## Tracking is a separate product [Managed Analytics](https://docs.spitzli.cloud/developers/managed-analytics.md) uses a shared Umami instance and gives each customer project scoped tracking resources. Customers do not receive their own Umami installation. Its integrated tracking controls therefore remain in the analytics plugin. ## API and MCP The Managed Apps plugin exposes application list/detail and start/stop/restart actions through the same host authorization used by its panel. | Action | Intent | | - | - | | `apps.list` | List the apps assigned to this project | | `apps.get` | Read one assigned app's operational state | | `apps.start` | Start the existing app | | `apps.stop` | Stop the app, retaining its data | | `apps.restart` | Restart the existing app | Mutations carry `app_id`, `revision` and `subscription_revision`; the host derives the project and idempotency scope from the verified invocation. A stale revision is rejected. App links are rendered by the Console from trusted Hosting metadata, outside the sandboxed plugin panel. Registry branding, kinds, manifest fields and provider settings are not plugin actions. See [plugin API and MCP](https://docs.spitzli.cloud/developers/plugin-api-mcp.md) for the common transport rules. ## Withdrawn registry-admin alpha The former `managed-registry` version `0.1.0-alpha.1` is withdrawn and must not be installed. It mirrored registry administration into Spitzli Cloud, which is not the Managed Apps product boundary. Its source and immutable release artifacts are retained for traceability; it was not installed in production. ## Source and release * [Managed Apps source](https://github.com/spitzli/webdock-extension-managed-apps) * [Developer alpha 0.1.0-alpha.1](https://github.com/spitzli/webdock-extension-managed-apps/releases/tag/v0.1.0-alpha.1) * [Registry entry](https://registry.webdock.dev/plugins/managed-apps) This is an established protocol-v1 release. Its signed manifest and immutable image remain preserved; newer native releases do not replace its transport or binding automatically. Current availability depends on the installed host adapter, runtime and project binding. See [release boundaries](https://docs.spitzli.cloud/developers/plugin-releases.md). The current host boundary is implemented in native app host services (`crates/plugin-host`). A historical pilot is not current acceptance for every customer installation. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.