Review
Preview local work
Send a live application preview to a teammate, client, or another device without deploying it first.
Public URLsBeta
Your local service.Ready to share.
Turn one selected loopback port into a public HTTPS URL. Share a preview, receive a webhook, or test a callback while this device is sharing.
- HTTPS + WSS
- Loopback only
- 3 URL beta cap
Use cases
Keep the feedback loop local.
A public endpoint is most useful when a local service needs a real outside caller. Zync keeps that workflow inside the desktop workspace.
Integrate
Receive webhooks
Give a third-party service a reachable HTTPS endpoint while your local webhook handler is running.
Authenticate
Test OAuth callbacks
Exercise browser-based callback flows against a public endpoint that routes to your local application.
Realtime
Share WebSockets
Carry WebSocket traffic through the WSS endpoint for local realtime interfaces and development servers.
From port to URL
Four steps. No deploy.
Public URLs is a desktop workflow. Choose the service, create the share, then leave the agent running for as long as the link should work.
Sign in
Use the separate Public URLs account with GitHub or Google.
Choose a port
Select a service on localhost, 127.0.0.1, or ::1.
Create the URL
Add an optional name and visitor password, then share the generated HTTPS link.
Keep sharing
The desktop share agent keeps the route live until you stop, delete, or sign out.
Visitor
→https://public-urlZync relay
→HTTPS / WSSThis device
localhost:3000Separate by design
A share link is not an SSH tunnel.
Both features move traffic, but they have different accounts, lifetimes, targets, and trust boundaries. Pick the surface that matches the job.
Public URLs Beta
Share a local web service.
- Loopback target on this device
- Public HTTPS and WSS endpoint
- Separate GitHub or Google share account
- Lives with the desktop share agent
Port forwarding
Route through an SSH session.
- Local, remote, or SOCKS forwarding
- Target reached through an SSH server
- No Public URLs account
- Usually tied to the SSH transport
Stay in control
Share deliberately. Stop completely.
The public link is a capability. Zync gives you the controls to protect it, pause it, and remove it when the review or integration task is over.
Read the security model ↗Password when needed
Add a visitor password before sharing a service that should not be openly reachable.
Start, stop, delete
Pause the agent connection, restart a saved share, or delete the URL when the task is finished.
Three during Beta
Owned active, reserved, and stopped URLs count toward the current hard cap of three.
Sharing from this deviceThe local service and share agent must remain available.
Public URLs FAQ
Before you share.
Answers about availability, exposure, account boundaries, and how sharing differs from SSH forwarding.
Is this SSH port forwarding?
No. Public URLs uses a separate Zync account, desktop share agent, API, and HTTPS/WSS relay. It is not SSH -L, -R, or -D.
Does Zync need to stay open?
The desktop share agent on this device must keep running. Closing the local service can leave the URL online but returning connection errors until you stop it.
Can it share another machine on my network?
No. The desktop agent accepts loopback targets only: localhost, 127.0.0.1, or ::1.
Does it expose raw TCP?
The user-facing Public URL is for HTTP and WebSocket services through HTTPS or WSS. Use SSH port forwarding for local, remote, or SOCKS network tunnels.
Can I use a custom domain?
Not in the current Beta. Zync issues the public hostname for each share. Custom domains and team sharing controls are not available today.
Does it use my Drive Sync account?
No. Public URLs sign-in and Google Drive Sync use separate OAuth clients and separate product boundaries.
Public URLs Beta
Share the service you already have running.
Download Zync, open Public URLs, and turn a selected localhost port into a link when you need one.