Skip to documentation
DevelopersManaurum Platform v2
Back to Manaurum

Manaurum Platform v2

Manifest v2

Ship manifest.json at the bundle root. The downloadable JSON Schema is the canonical field and validation reference.

Contracts reviewed: · SDK version: 2.6.1

Required fields and identifiers

manifest_version and manaurum_sdk_version are strings equal to 2. Include app_id, name, version and runtime; version is MAJOR.MINOR.PATCH without prerelease or build suffixes. runtime.mode is hosted, byo or dev. The schema permits a non-empty app_id; use a lowercase URL-safe slug for a hosted app. The platform also assigns an internal UUID. Do not interchange that UUID and the slug in capability headers. The example opts out of managed SQL with data.none.

json
{
  "manifest_version": "2",
  "manaurum_sdk_version": "2",
  "app_id": "my-tracker",
  "name": "My Tracker",
  "version": "0.0.1",
  "runtime": {
    "mode": "hosted",
    "port": 8000,
    "health_path": "/healthz",
    "api_routes": [
      {
        "path": "/api/items",
        "auth": "user"
      }
    ]
  },
  "data": {
    "none": true
  },
  "frontend": {
    "entry_point": "src/static/index.html",
    "window": {
      "default_width": 800,
      "default_height": 600
    }
  },
  "requires_capabilities": [
    {
      "name": "os.kv.get",
      "version": "1"
    },
    {
      "name": "os.kv.set",
      "version": "1"
    }
  ]
}

Routes, storage and browser permissions

API routes declare path and auth: user, anonymous, optional or people. optional serves guests anonymously and adds signed context for members; people requires the top-level people block and a verified role/person pass. undeclared API paths return 404. User handlers verify X-Manaurum-User-Context. Static routes and /healthz have a separate gateway policy; public_paths permits top-level document navigation without a session and never opens API access. Set an anonymous health_path and the correct container port for a strict readiness probe. Default SQL storage is per app and tenant; data.none and data.byo opt out, data.shared requires your own tenant filtering. data.extensions requests vector or pg_trgm and also needs an operator grant. Browser permissions accepts microphone and camera, is refused for BYO, and cannot be declared from Studio. It delegates the feature to an iframe but never skips browser consent.

Additional blocks and reserved fields

requires_capabilities and optional_capabilities declare platform access; platforms declares mobile support. provides and consumes describe RPC, events and bulk contracts. agent_capabilities exposes internal agent handlers; tenant_config declares settings and metadata describes the app. offline describes Edge replication. schedules invokes hidden internal handlers with a cron-scheduler system token once per slot. telegram.handler_path receives buttons, reactions and replies with a telegram-bot system token; verify it, deduplicate update_id and answer within 8 seconds. Migration files use migration metadata. webhooks, migrate_command and runtime.replicas validate but are not wired to delivery, migration execution or self-service scaling. The root rejects unknown keys.

json
{
  "migration": {
    "breaking": false,
    "reason": "additive index",
    "rollback_strategy": "forward-only"
  }
}

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

Getting startedFeature availability