Sign in
← AI PulseSep 2, 2026

Policy · news · Single-source brief

Cursor Details Self-Hosted Machine Integrations

Cursor provides partner guides and reference templates for running Self-Hosted Machines workers across various cloud platforms, including AWS Lambda, Cloudflare, and Kubernetes.

By Illumora Editorial

Source · Sep 2, 2026, 9:00 PM · On Illumora · Sep 2, 2026, 9:02 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →Cursor Changelog — Integrations | Cursor Docs
Save

The Cursor Changelog details integration options for Self-Hosted Machines workers, offering guidance and reference templates for deployment on multiple infrastructure partners. These resources support running Team Pool workers on platforms such as AWS Lambda, Cloudflare, Namespace, Modal, Daytona, E2B, Vercel, and Kubernetes.

Key Points

  • Cursor offers partner guides and reference templates for Self-Hosted Machines workers.
  • Supported platforms include AWS Lambda, Cloudflare, Namespace, Modal, Daytona, E2B, Vercel, and Kubernetes.
  • All worker options use the same mechanism: the Cursor CLI opens an outbound HTTPS connection to Cursor, which then sends agent tool calls over that connection.
  • Reference architectures are provided, but users retain ownership of the worker image, infrastructure, secrets, scaling policy, and production validation.
  • Specific templates are available, such as anysphere/aws-lambda-workers for Lambda MicroVMs and anysphere/cloudflare-workers for Cloudflare Containers.
  • Deployment requires a Cursor Enterprise plan with Self-Hosted Machines enabled and a service account API key.
  • Workers need outbound HTTPS access to api2.cursor.sh, api2direct.cursor.sh, and cloud-agent-artifacts.s3.us-east-1.amazonaws.com.

Context

According to the Cursor Changelog, these integrations provide a framework for deploying Self-Hosted Machines workers. Each partner maintains its own guide, and Cursor offers reference repositories that users can clone and adapt. These templates include a worker controller that claims pending pool requests and initiates one worker per claim.

Why It Matters

Builders deploying Cursor agents can leverage these integration guides and templates to manage their own worker infrastructure, allowing for custom scaling, security, and operational control over their agent deployments.

What To Do

  • Review the Cursor documentation for Self-Hosted Machines integrations to identify suitable deployment platforms.
  • Examine the provided reference templates, such as those for AWS Lambda MicroVMs or Cloudflare Containers, to understand the worker deployment model.
  • Note the network requirements for outbound HTTPS connections to Cursor endpoints.
  • Ensure that a Cursor Enterprise plan is in place and Self-Hosted Machines are enabled for deployment.