Projects & Services
Managing Services
Your agent creates, updates, redeploys, and deletes services through the CLI, Skills, MCP, or dashboard
Services are the core unit of deployment in Ink. Your agent can manage the full lifecycle through the CLI, an Ink Skill, MCP, or the dashboard.
Creating a service
Your agent calls service_create with:
- A name for the service (unique per project)
- A git repository (Ink managed or GitHub)
- Optional: build configuration, environment variables, resource allocation
Prompt
❯
Deploy a FastAPI backend called 'api' from the ink/my-api repo
Service properties
| Property | Description | Default |
|---|---|---|
| Name | Unique within a project | Required |
| Repository | Git repo reference | Required |
| Branch | Branch to deploy from | main |
| URL | Auto-assigned live URL | service-name.deployink.com |
| Port | Port your app listens on | 3000 |
| Build pack | How the app is built | Auto-detect |
| Memory | RAM allocation | 256 Mi |
| vCPU | CPU allocation | 0.25 |
Updating a service
Your agent calls service_update to change configuration and trigger a redeployment. Any changed parameter triggers a new build:
"Scale up the API to 2GB memory and 2 vCPUs"
→ service_update(name="api", memory="2048Mi", vcpus="2")Redeploying
Push new code to the tracked branch, or have your agent call service_update. GitHub repos auto-deploy on push via webhooks.
Deleting a service
"Delete the staging service"
→ service_delete(name="staging")This stops the running container and removes the service. Attached volumes are detached and retained for 24 hours unless reattached or deleted.