What changed
Kong announced Volcano to address the growing complexity of stitching together separate services for AI software, according to the launch post. The company said it designed the platform after building internal agents and working with over 1,000 large enterprise organizations. Kong noted it processed more than a quadrillion customer requests over the past 12 months before opening the platform to developers.1
According to Kong's announcement, developers can drive Volcano from coding harnesses such as Cursor and Claude Code or through an online builder. Once agents, backends, and frontends are deployed, the platform continuously detects issues and applies bug fixes autonomously. Kong said this self-healing loop improves codebases over time without human intervention.1
How it works
Volcano's product page describes a core orchestration layer built around durable functions that checkpoint each step for up to a year. Workflows can pause for human approval before resuming from the exact stopping point, while distributed locks ensure one worker handles a task at a time. The platform also includes managed PostgreSQL with pgvector, private file storage buckets, and isolated sandboxes for running agent-generated code.2
For a concrete workflow, Volcano's documentation outlines a GitHub webhook pull request summarizer that pairs incoming webhooks with a durable function and replays test payloads from Insomnia. Developers can also deploy a Model Context Protocol server as a Volcano function and call its tools from Insomnia's client. The platform's CLI installs skills for detected local coding agents during setup.2
Volcano's pricing page lists a free HOBBY tier that pauses resources once monthly allowances are reached, including 1 GB of Postgres storage and 100,000 function invocations. The $17 per month SUPERAGENT plan, paid annually, raises database storage to 10 GB and includes 1,000 monthly credits for overages, with extra blocks costing $25. An Enterprise tier adds custom limits and service-level agreements, though the published pages do not specify which bug classes the self-healing engine cannot fix.3