Managed control plane

Autodisc uses one connected product flow:

1. Sign in through Autodisc.
2. Open /dashboard or any nested /dashboard/x page.
3. Autodisc resolves the active account and permissions server-side.
4. The requested dashboard page opens on the same public origin.

Signing out from Autodisc Deploy also clears the connected Autodisc session. Do not share a control-plane session or use a Dokploy-local password for a managed account.

What remains available

Managed mode changes branding, authentication, links, and infrastructure authorization. It does not intentionally remove Dokploy features. Projects, environments, applications, Compose, databases, deployments, schedules, monitoring, Docker views, Docker Swarm, SSH keys, web-server settings, registries, domains, backups, and notifications remain available when your role and server ownership permit them.

Why some server controls differ

A shared tenant may inspect and operate only containers bound to that tenant's services. The underlying host address, credentials, Docker daemon, Swarm administration, and neighboring workloads are platform infrastructure.

An account-owned Autodisc Server retains the server-level controls needed to operate that infrastructure. Managed Autodisc does not expose a bring-your-own-IP or remote-server attachment path. See Servers, pricing, and lifecycle.

Internal and public APIs

The browser and CLI should use Autodisc's public, account-scoped interfaces. Autodisc communicates with Dokploy through a private runtime gateway. Internal service tokens and runtime binding identifiers are never customer API keys.