Applications and domains

Apps And Domains

Control shared-auth app clients, standalone domains, tenant white-label routes, public sites, redirect URIs, origins, scopes, and protocol readiness.
4 ready Open app clients
3 Tenant workspaces 2 active and 1 under setup or review 2 Pending approvals 1 blocked items need explanation or remediation 4/4 App clients Shared auth, redirects, origins, OpenAPI, MCP, and A2A readiness 1 Agent identities Agent access must remain permissioned, scoped, and audited

Shared auth

App client readiness

3 items

Every standalone app needs a manifest, audience, issuer, redirect URI, allowed origin, and scopes.

Standalone app clients Keep app registration compatible with apps on DiyaOS domains and approved standalone domains.
ready 4 apps
Tenant-branded DiyaOS hosting Resolve tenant context and render approved tenant branding on DiyaOS-owned hosts.
watch Tenant experience
White-label custom domains Activate only after tenant approval, DNS verification, certificate readiness, and app-client validation.
high Domain control

Client domains

Public site routing

3 items

Some tenant public sites can also run through DiyaOS, but admin/auth routes stay governed.

Public website hosting Public pages must remain separate from admin routes, app auth callbacks, and private tenant portals.
medium Public site
Redirect and origin safety Allowed origins and redirects must be registered records, not hard-coded domains.
high App client
Protocol readiness Apps should expose OpenAPI and plan MCP, A2A, and CloudEvents where agents need access.
watch Agents

Useful Drill-Downs

existing tools
App clients Integrations API Manifest Tenant governance