Skip to main content
Managed Apps operates dedicated applications assigned to a Webdock 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.
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 Webdock Tabularium app was assigned to its existing project. Other projects still require an explicit installation grant and app binding.

​
Operate the app in Webdock

  • 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.

​
Production Console

The production Console shows 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. Production Console with the existing Tabularium app ready in Managed Apps

​
Panel preview

These captures show a fictional Harbor project in the local UI fixture. Start and stop are simulated here; the images are not evidence of a production installation. The production Console supplies trusted app and Hosting links above the panel. Managed Apps panel showing a dedicated Tabularium app in the running state The same dedicated app shown as stopped after refreshing its status

​
Configure the registry in Tabularium

Use the dedicated Tabularium administration for registry branding, kinds, manifest fields, submissions, providers and users. Webdock 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 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. 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 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 Webdock, 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

The public container can be pulled anonymously by the manifest’s immutable digest. The release descriptor matches the registry’s signed manifest. Production activation additionally verified the private runtime’s TLS certificate, plugin identity, version and generation. The public plugin endpoint exposes only the UI; application actions pass through the authenticated Webdock host.