How It Works
3 AM: the client portal starts throwing 502 errors.
- The on-call engineer opens the server in the browser. No VPN, no SSH key on their laptop, no shared password. The platform holds the key and connects for them.
- They hand the problem to the AI assistant. “Customers are getting 502 errors on the client portal API. Find the cause and propose a fix.” The AI reads the nginx error log, checks which process is listening on which port, opens the app's settings and reports back: nginx is pointed at port 8081, but the API listens on 8080.
- The AI proposes the fix, but doesn't apply it. The engineer gets a side-by-side diff with the AI's explanation, then Accept & Apply or Reject. The AI can't quietly change files.
- The engineer reloads nginx and confirms HTTP 200 in the terminal built into the editor, without leaving the page. The login banner already said it: “This session is recorded.”
- The next morning, the security lead replays the whole session like a video, with time-stamped comments. They read the AI's full conversation in the audit log (every message, every command it ran) and confirm the recordings haven't been altered.
















