Skip to content

#84 · Enhanced Private Locations: WebSocket & CLI Support

We’ve released a new version of our Private Locations feature, now supporting testing of internal APIs with more protocols, including WebSocket, which was previously unsupported.

Additionally, Private Locations are now available through the Escape CLI for a smoother experience. Learn more here.

Key benefits:

1. Single Pane of Glass

All Escape tooling (CLI for API interactions and Private Location management) is now unified into one binary, reducing complexity and making deployment easier.

2. Improved Stability & Scalability

  • More stable and scalable, especially for frontend DAST
  • More reliable health checks for uninterrupted operation

3. Simplified Setup & Usage

  • No more manual repeater ID creation
  • Support for WebSocket protocols for better API testing
  • No Node.js installation required (binary format)

4. Enhanced Transparency & Monitoring

  • Open-source & auditable for security and transparency
  • Direct log access from the Escape front-end
  • New workflow indicating when a repeater is unhealthy

Migration from Legacy Repeater

If you're using the old repeater image, follow the migration guide below to switch to the new CLI-based approach.

The new escapetech/cli image simplifies setup—no need to manually create a repeater or copy-paste its ID.

Steps to migrate:

  1. Retrieve your API key from your profile page
  2. Update your configuration:
    • Remove the ESCAPE_REPEATER_ID environment variable
    • Add the ESCAPE_API_KEY environment variable
  3. Update the startup command:\ locations start -v location-name where location-name is your desired location name
  4. Switch from the escapetech/repeater image to the escapetech/cli:latest image