Task containers turn idle jobs into on-demand compute
Blog post from Upsun
Upsun’s task containers, generally available since August 12, 2026, provide ephemeral, API-triggered compute for jobs that run intermittently, such as database re-indexing, exports, reports, and one-time migrations, avoiding the cost of continuously running services. Defined in `.upsun/config.yaml`, each task uses a specified runtime image and command, starts through the Console, CLI, or API, provides logs and status for each invocation, and is billed per second with run times from one hour by default up to 24 hours. Tasks differ from workers, which handle persistent background processing, and crons, which provide scheduling; schedules or external systems can instead trigger tasks when needed. They can securely access declared environment services through one-way relationships and can be started by applications using short-lived authorization tokens. The approach is also positioned for AI agents that need limited production context such as logs, metrics, and deployment history without unrestricted application access, using container isolation, permissions, preview environments, resource sizing, and parallel-run limits to manage security and costs.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.