Kubernetes and k3s
Connect an existing cluster and manage permitted workloads.
Vercel
Authorize a team and choose the projects available to Webdock.
turboSMTP
Use your own sending account with workspace-scoped Mail keys.
Automate with MCP
Discover BYOK tools, revision checks and recovery behavior.
Permissions before connection
A platform operator enables each provider separately in the customer’s Your infrastructure → Selfservice permissions controls. All provider switches are disabled by default. Workspace owners and administrators can use enabled connections; they cannot grant themselves platform privileges.
Read-only customer preview cannot make these changes. A provider grant, workspace membership or hosting scope alone is insufficient: Webdock rechecks the current combination on each action.
Connection lifecycle
A registration record is not a working connection. Complete agent enrollment or provider authorization, then inspect the last verification and inventory timestamps. Refresh stale data before making changes. Disabling a permission blocks further use through Webdock. Disconnecting or revoking a connection does not delete provider resources. Keep provider-side access and backups under your control; revoke provider credentials separately when they should no longer work outside Webdock.BYOK does not provide a blanket availability, backup or data-residency guarantee. Supply location evidence for clusters and verify actual deployment regions. A provider’s global management services remain distinct from its workload location.