Getting external beta testers to access a staging API is usually a pain. You either make the server public (security liability), give them VPN credentials (setup overhead), or ask them to coordinate around a specific time window when you'll open access manually.
VibeControls tunnel tokens provide a clean third path. The staging API runs on a server with an agent installed. Create a port-forward to the API port and enable "Public access". Set the expiry: 4 hours for a focused test session, 24 hours for a day-long integration sprint.
Copy the public URL and send it to the beta testers. They can hit the API from any browser, Postman, or curl command using the URL. No credentials needed — the tunnel token is the access control.
When the expiry time arrives, the URL stops working automatically. No cleanup, no "remember to revoke the access we granted last week." The access lifecycle is completely managed by the token.
For QA teams running external user acceptance testing, this reduces coordination overhead from hours (set up VPN, share credentials, verify connectivity, clean up) to minutes (create token, share URL, forget about it).
Do it yourself
Give external beta testers a public URL to your staging API that automatically stops working after a time window you choose, with no manual cleanup.
Go to Agents and open the agent running on the box that hosts your staging API.
You should see: The agent detail page opens, ready to forward one of its ports.
Ready to make this your story?
