Coder introduces Agent Relay powered by SpaceXAI, utilizing Cursor’s cloud agents on the infrastructure of customers.

      Coder has introduced Agent Relay, a self-hosted execution environment that enables Cursor’s cloud agents to operate within a customer's own infrastructure, partnering with SpaceXAI for the launch, and the product is currently in private preview. Cursor continues to handle inference and planning, making it an ICT third-party provider under the EU’s Digital Operational Resilience Act.

      Coder has unveiled a method for executing Cursor’s cloud agents within a client’s network, with SpaceXAI as its launch partner.

      The execution pertains to the process rather than the model itself. While the agent loop, including inference and planning, continues to run on Cursor's side, tool calls are executed on the customer’s systems. Coder refers to this outcome as an AI operating layer.

      The intended market is clearly defined as banks, defense agencies, and government organizations, where Coder argues that the primary obstacle has been the deployment model instead of demand.

      Currently, it is in private preview with design partners. No pricing details, general availability projection, or specific customers have been disclosed in the announcement. Coder indicates that air-gapped deployment is an option when external access is not permissible.

      In Europe, this obstacle is already identified as DORA, which has been effective since January 17, 2025, governing how financial entities procure ICT services.

      The requirements are not influenced by where the code is executed, but rather the arrangement and the provider involved.

      This presents a challenging aspect of the pitch. Since Cursor continues to manage the inference, it remains an ICT third-party provider, regardless of the tool operations' location.

      Article 30 specifies necessary contract details, including processing and storage locations, audit rights for banks and regulators, subcontracting conditions, as well as data retrieval and deletion upon exit.

      There is also an inventory requirement. Article 28 stipulates a register linking each provider, service, criticality rating, and data location, which must be made available to supervisors upon request.

      Critical functions necessitate a validated exit strategy. Exit plans must address migration feasibility, notice periods, transition support, and whether the approach has been validated. The bank retains full accountability, regardless of how much is outsourced.

      Ownership is currently a pertinent issue, as SpaceX finalized its acquisition of Cursor this year.

      The aim is not to diminish the value of self-hosting. Maintaining source code and sensitive information on machines owned by a bank addresses a legitimate concern, and having an audit log is a credible compliance artifact.

      However, the documentation remains applicable. TNW reported that OpenAI ceased its model supply to Cursor following the acquisition, which corresponds precisely to the dependency that Article 30 is designed to document.