Cloud Deploy Pack
★Trusted◇Sandbox optionalv1.0.0MIT✔Verified80by AgentNode · published 6 months ago · toolpack
Deploy applications to Vercel, Railway, Fly.io, and Render.
One-command deployment to popular cloud platforms. Supports static sites, Node.js, Python, and Docker-based deployments with environment variable management.
Quick Start
agentnode install cloud-deploy-packRuns in a subprocess with filtered environment by default. Declared permissions are policy-checked, not sandboxed.
Usage
From packagefrom cloud_deploy_pack.tool import run
result = run(
capability="deploy_app",
params={
"platform": "vercel",
"project_dir": "./my-nextjs-app",
"project_name": "my-nextjs-app",
"environment": "production",
"env_vars": {
"DATABASE_URL": "postgres://...",
"NEXT_PUBLIC_API_URL": "https://api.example.com"
}
}
)
print(f"Deployment ID: {result['deployment_id']}")
print(f"URL: {result['url']}")
print(f"Status: {result['status']}")
print(f"Ready in: {result['ready_seconds']}s")Environment Variables
VERCEL_TOKENVercel personal access token. Required when deploying to Vercel.
RAILWAY_TOKENRailway API token. Required when deploying to Railway.
FLY_API_TOKENFly.io authentication token. Required when deploying to Fly.io.
RENDER_API_KEYRender API key. Required when deploying to Render.
Runs locally on your machine. No execution data is sent to AgentNode. Permissions are checked before execution. Learn how this works
Verification
Package installs and imports correctly. runtime checks passed.
This package was executed and validated by AgentNode before listing. Install, import, and runtime checks passed.
Verified in real_auto mode
Last verified 17d ago· Runner v2.0.0
Use this when you need to...
- ›Deploy a Next.js app to Vercel from source
- ›Push a Docker container to Railway
- ›Deploy a Python API to Fly.io globally
- ›Roll back a failed deployment to the previous version
- ›Check deployment status and live URLs
README
Version History
Capabilities
Permissions
Declared by the publisher. Checked before execution by the policy gate.
Permissions are policy-checked before execution. For trusted and curated packages that run on the host, network and filesystem access are policy-checked but not OS-sandboxed. When runtime isolation is required for untrusted/community code, AgentNode uses sandbox-or-fail-closed if the required container runtime and pinned image are available. Learn more
Privacy
All tool execution happens locally on your machine. AgentNode never receives:
- • Tool inputs or outputs
- • Execution logs
- • Data your agent processes
Only install events and search queries are sent to the registry.
agentnode install cloud-deploy-packEnvironment Variables
VERCEL_TOKENRAILWAY_TOKENFLY_API_TOKENRENDER_API_KEYFiles (3)
License
MITStats
Compatibility
Frameworks
Runtime
pythonPython Version
>=3.10Trust & Security
Publisher
AgentNode
@agentnode