Sandbox Preview URLs and Auth via Customer Proxy

One of the most requested features is here: Daytona now supports Customer Proxy.
This gives you full control over how sandbox preview links are served to your users.

Instead of preview links pointing back to Daytona, you can deploy your own proxy and decide exactly how previews behave.

What You Can Do

With Customer Proxy, you can:

• Use your own domain - e.g., preview.yourcompany.com

• Add authentication - protect private previews with your own auth flow

• Auto-manage sandboxes - start stopped sandboxes before forwarding traffic

• Customize error handling - show branded error pages instead of generic responses

• Remove warnings & tweak CORS - bypass default Daytona settings with custom headers like:

1X-Daytona-Skip-Preview-Warning: true  
2X-Daytona-Disable-CORS: true

How It Works

When someone opens a preview link, the request goes through your proxy first. From there, you decide what happens:

1. Authenticate the user with your own logic

2. Start the sandbox if it’s stopped

3. Forward the request to the running sandbox

4. Apply your own styling, headers, and error pages

For private previews, simply attach the sandbox token:

1X-Daytona-Preview-Token: {sandboxToken}

Tokens can be fetched via the Daytona SDK or API.

We’ve provided starter implementations so you can get up and running fast:

• Typescript Example

• Golang Example

Why It Matters

For teams running previews in production-like workflows, Customer Proxy removes friction:

• No more external-looking links. Everything stays under your own domain.

• No extra login screens. Your company’s auth and branding.

• No more surprises. Every preview behaves exactly as you define.

Get Started Today

Customer Proxy is available now in Daytona v0.25.
Check out the Customer Proxy documentation and start hosting sandbox previews on your own terms.