# AgentDeploy > AI-native deployment and runtime infrastructure. Agents build and act; people retain control of infrastructure, access and production decisions. ## Connect - Remote MCP: https://mcp.agent-deploy.ai/mcp - Agent guide: https://install.agent-deploy.ai/agent - Publishing Skill: https://install.agent-deploy.ai/skills/publish/SKILL.md - Console: https://console.agent-deploy.ai - Documentation: https://docs.agent-deploy.ai ## Supported publication profiles - Static HTML, CSS, JavaScript and built frontend assets. - JavaScript / TypeScript Fetch Workers. Available bindings depend on node capabilities. - Digest-pinned Linux OCI images serving HTTP. ## Workflow Discover authorized organizations and eligible nodes. Build with the agent's local tools. Package and upload an immutable release. Deploy to a separate preview environment and verify it. Promote the exact reviewed release after explicit production approval. Observe status and roll back when required. ## Core value - Give agents autonomy while keeping infrastructure, access and production control with the user. - Deploy and provision applications and services from supported agents through MCP. - Unify customer cloud accounts, third-party provider runtimes, edge sites and private infrastructure in one control plane. - AgentDeploy does not sell or operate hosting capacity. - Use scoped permissions, controlled network paths and temporary authorization where configured. - Preserve an explicit Preview and approval boundary before production changes. - The customer-side Edge Runtime and clients will be open sourced so behavior and trust boundaries can be independently reviewed. ## Customer paths - OPCs and indie builders: /customers/opc.html - Developers: /customers/developers.html - Small and midsize businesses: /customers/smb.html - Small teams inside large enterprises: /customers/enterprise-teams.html ## Use cases - Migration deployment: /use-cases/migration.html - Multi-cloud and multi-site deployment: /use-cases/multi-cloud-multi-site.html - Infrastructure cost assessment and optimization: /use-cases/cost-optimization.html Migration depends on source access, data portability and application-specific constraints. Multi-site capabilities depend on registered node and provider capabilities. Cost recommendations depend on the completeness of billing, utilization and labor data and do not guarantee savings. Use the live MCP capability and development profile tools to check current support. The website's session and release diagrams are illustrative, not live deployment status. ## Enterprise delivery and operations Coding and general-purpose agents create deployable applications. AgentDeploy connects that output to approved customer-controlled or third-party runtime environments, controlled service entry points and ongoing operations. Gateway, Mesh and Tunnel provide configurable connectivity boundaries. Operations teams and infrastructure providers retain responsibility for capacity, application quality and data permissions. Agents can work with scoped resource grants and, where configured, temporary network tickets or policies that expire or can be revoked after the task. OAuth, open APIs and runtime metrics are available. Enterprise SSO/SCIM, approval workflows and external system adapters depend on project-specific integration.