Coder launches Agent Relay with SpaceXAI, running Cursor’s cloud agents on customer infrastructure
Coder has announced Agent Relay, a self-hosted execution environment that lets Cursor’s cloud agents run inside a customer’s own infrastructure, with SpaceXAI as launch partner and the product in private preview. Cursor continues to run inference and planning, so under the EU’s Digital Operational Resilience Act it remains an ICT third-party provider. Coder has announced […] This story continues at The Next Web
Coder has announced Agent Relay, a self-hosted execution environment that lets Cursor’s cloud agents run inside a customer’s own infrastructure, with SpaceXAI as launch partner and the product in private preview. Cursor continues to run inference and planning, so under the EU’s Digital Operational Resilience Act it remains an ICT third-party provider.
Coder has announced a way to run Cursor’s cloud agents inside a customer’s own network. SpaceXAI is the launch partner for Agent Relay, the company said .
What moves is the execution rather than the model. Cursor keeps running the agent loop, including inference and planning, while tool calls happen on the customer’s machines. Coder calls the result an AI operating layer.
The target market is named plainly. Banks, defence agencies and government institutions, where Coder argues the blocker has always been the deployment model rather than the appetite.
It is in private preview with design partners. There is no pricing, no general availability and no named customer anywhere in the announcement. Coder says air-gapped deployment is available where no external access is acceptable.
In Europe that blocker already has a name. DORA has applied since 17 January 2025 and governs how financial entities contract for ICT services.
Its requirements do not attach to where code executes. They attach to the arrangement and to the provider behind it.
Which is the awkward part of the pitch. Cursor still runs the inference, so it remains an ICT third-party provider whatever happens to the tool calls.
Article 30 sets out what the contract has to say. Processing and storage locations, audit rights for the bank and its regulator, subcontracting conditions, and data return and deletion on exit.
There is an inventory as well. Article 28 requires a register linking every provider, service, criticality rating and data location, available to supervisors on request.
Critical functions need a tested way out. Exit plans must cover migration feasibility, notice periods, transition assistance and whether the route has been validated. The bank keeps full responsibility however much it contracts out.
Ownership is a live question here too. SpaceX completed its takeover of Cursor this year.
The point is not that self-hosting is worthless. Keeping source code and secrets on machines a bank controls answers a real objection, and the audit log is a genuine compliance artefact.
It is that the paperwork survives it. TNW reported OpenAI ending model supply to Cursor after the acquisition, which is exactly the dependency Article 30 exists to document.