Skip to documentation
DevelopersManaurum Platform v2
Back to Manaurum

Manaurum Platform v2

Feature availability

Implementation status and known limits, reviewed against the repository contracts. This page does not monitor live outages.

Contracts reviewed: · SDK version: 2.6.1

Implemented contracts

Hosted containers, manifest v2 validation, developer/runtime credentials, capability gateway, scoped SQL roles, immutable source snapshots, migrations, Dev Hub and Aurum Studio are implemented. CLI commands include init, validate, validate-migration, deploy, rollback, logs, list-versions, set-secret, describe, fetch-source, history and diff. Cron schedules and Telegram events have internal signed handlers. The capability list is generated from registered backend definitions; integrations, flags, grants and spending limits still determine actual availability.

Conditional availability

Cross-tenant Store listing/install uses workspace policy and the platform-v2 feature gate. Image generation needs a tenant flag and OpenAI BYOK. Database extensions require an operator grant. User-scoped capabilities need user context and any required folder/permission grant. Studio builds declarative backend models but does not accept arbitrary handwritten handlers or device permissions. CLI install is not implemented; install published apps through the Store.

Reserved and planned

Webhook declarations validate but Core does not deliver them. migrate_command is reserved; use SQL files. runtime.replicas is accepted but scaling is operator-controlled. A tenant Agent Registry and marketplace payments/revenue share are planned, not shipped. Per-app agent_capabilities already exists. The v1 app platform is retired. Review date and SDK version identify this reference; they do not certify that a deployment or integration is healthy right now.

This is a feature reference, not a live service-health dashboard. Availability also depends on workspace permissions, integrations and feature flags.

Getting startedFeature availability