Home

GhostlyShare User Guide

GhostlyShare makes local development apps public through temporary or custom Cloudflare-powered URLs. It is meant for demos, reviews, mobile-device testing, webhook testing, and short-lived sharing of local work.

This wiki explains what GhostlyShare expects, how app detection works, why apps may be merged, why a public link may need a moment before it is reachable, and what is different between Windows and Linux.

Quick Links

• Getting Started
• Installation and Updates
• App Detection
• App Merging
• Going Public
• Custom Domains
• Windows and Linux
• Troubleshooting
• Reporting Bugs and Feature Requests
• Testing Checklist
• FAQ

What GhostlyShare Is For

GhostlyShare is for local development services that already work on your machine:

• Frontend dev servers.
• Backend APIs.
• Local dashboards.
• Documentation sites.
• Framework development servers.
• Temporary demo apps.
• Local webhook receivers.

GhostlyShare does not deploy your app. Your app keeps running locally. GhostlyShare starts a secure tunnel and forwards public traffic back to your local app.

What GhostlyShare Is Not

GhostlyShare is not a production hosting platform. Public links are meant to be temporary and controlled by your desktop session.

It is also not a general port forwarder for every local process. GhostlyShare tries to avoid exposing system services, infrastructure services, printer services, VPN services, random background ports, and weakly identified HTTP endpoints.

Basic Flow

1. Start your local app.
2. Open GhostlyShare.
3. Wait for the app to appear.
4. Choose Random or Custom.
5. Select Go Public.
6. Copy or open the public URL.
7. Stop sharing when you are done.

If your app does not appear, see App Detection and Troubleshooting.

Bugs and Feature Requests

Use GitHub Issues to report bugs or request user-facing improvements:

• Report a bug
• Request a feature

Please remove Cloudflare API tokens, passwords, private URLs, and other secrets before posting.