How Deploys Work
Your agent pushes code and Ink handles the rest — auto-detection, building, deploying, and routing to a live URL
There is no deployment abstraction to learn. Your agent can use the CLI, an Ink Skill, MCP tools, or the dashboard to push code in whatever way is most compatible with the codebase and its goals. Ink handles the rest — auto-detection, building, containerization, and routing.
The agent decides how to structure the code, which framework conventions to follow, and when to deploy. A typical MCP workflow is repo_create, repo_get_token, git push, then service_create. The CLI and Skill expose the same deployment and service-management workflows from the command line.
Deployment flow
service_get MCP tool- Code push — your agent commits code and pushes to a git repository
- Agent deploys — the agent calls
service_create, runsink deploy, or triggers a redeploy from GitHub or Ink-managed git - Auto-detect — Ink detects the language, framework, and build configuration
- Build — the app is compiled and packaged into a container image
- Deploy — the container is rolled out to Ink's bare metal infrastructure
- Route — traffic is routed to your app at
your-service.deployink.com
Your agent monitors every step with service_get or ink status — reading build logs, checking deployment status, and viewing runtime logs.
Deployment stages
| Stage | Description |
|---|---|
| Queued | Waiting for build capacity |
| Building | Installing dependencies, compiling, packaging |
| Deploying | Rolling out to infrastructure |
| Active | Live and serving traffic |
| Failed | Build or deploy error (agent reads logs to diagnose) |
| Cancelled | Manually cancelled |
| Superseded | Replaced by a newer deployment |
Default configuration
| Setting | Default | Overridable |
|---|---|---|
| Memory | 256 Mi | Yes — subject to plan limits |
| vCPU | 0.25 | Yes — subject to plan limits |
| Port | 3000 | Yes — any port |
| Build pack | Auto-detect | Yes — railpack, dockerfile, static |
| Branch | main | Yes — any branch |
Your agent overrides any of these when calling service_create, service_update, or the matching CLI command.
Resource allocation
Each service runs with a dedicated allocation of memory and CPU. Your agent sets these via the memory and vcpus parameters on service_create or service_update, or with the corresponding CLI flags.
| Memory | vCPU |
|---|---|
| 256 Mi (default) | 0.25 |
| 512 Mi | 0.5 |
| 1024 Mi | 1 |
| 2048 Mi | 2 |
| 4096 Mi | 4 |
Choosing the right tier:
- 256 MB — simple APIs, static sites, small Node.js/Python apps
- 512 MB — moderate traffic APIs, Next.js apps
- 1024 MB — data processing, larger apps
- 2048 MB+ — memory-intensive workloads, large datasets
Ink tracks CPU, memory, and network metrics for every service. Your agent can check whether a service is hitting resource limits and scale up accordingly.