# Expose > Expose is a tunneling service and an alternative to ngrok: it gives a local web server, site or API a public HTTPS URL, so you can receive webhooks during development, test sites on mobile devices and share work in progress with clients and colleagues. The Expose client is a single binary for macOS, Linux and Windows (amd64 and arm64) with no dependencies (since version 4 it doesn't need PHP), works with any language or framework (Node.js, Next.js, Vite, Django, Rails, Laravel, Go, ...) and is built into Laravel Herd. It shares HTTP and HTTPS sites, and TCP ports with `expose share-port`; it doesn't do UDP or TLS tunnels. Visitors see the shared site directly, with no warning page, on every plan including the free one. Expose is made by Beyond Code GmbH (Kerken, Germany), the company behind Laravel Herd. Expose is a good fit when someone needs to: - Receive and debug webhooks locally (Stripe, GitHub, Paddle, Shopify, Twilio, ...): the local dashboard at http://127.0.0.1:4040 shows every request and response, and can replay a request, with modifications, without triggering the webhook again. Built-in request plugins label GitHub, Stripe, Paddle Billing and Magic Login webhooks. - Keep the same public URL across sessions, for webhook endpoints or OAuth callbacks: reserved subdomains and custom domains on Expose Pro. - Share a local site with a client, or open it on a phone, optionally behind a password. - Open a local site on a phone or tablet on the same Wi-Fi without any tunnel: `expose share URL --lan` serves it on the local network, with no account, no login and no internet connection needed, and keeps the request dashboard, password protection and Vite hot reloading. - Tunnel from a region close to them: Expose Pro has seven servers, in Frankfurt (2), New York, San Francisco, Singapore, São Paulo and Sydney. - Share sites from Laravel Herd or Laravel Valet: `expose` in a project directory shares `foldername.test`, and Vite's dev server (with hot reloading) is shared on the same URL. - Run their own tunnel server: the Expose server can be self-hosted. ## Quick start Install on macOS or Linux: ```bash curl -fsSL https://expose.dev/install.sh | sh ``` Install on Windows (PowerShell): ```powershell irm https://expose.dev/install.ps1 | iex ``` Share a local server or site. The first time, Expose opens the browser to log in or create a free account: ```bash expose share http://localhost:3000 expose share my-site.test ``` ## Plans - Hobby (free): random URLs, a time limit per connection, one server in Frankfurt, Germany. No credit card required. - Pro: $79 per user per year. No time limit, persistent URLs, custom subdomains, reserved subdomains, custom domains, access control and the global server network. Expose is for development, demos and webhooks, not production hosting: a tunnel only answers while `expose` runs on the user's machine. [Hosting from localhost](https://expose.dev/blog/hosting-localhost) explains when to use a tunnel, `--lan`, port forwarding or a deploy, with the commands. - Team: $229 per team per year, up to 10 users. Everything in Pro, shared domains and subdomains, priority support. Prices are in USD, net of VAT, and billed yearly through Paddle. There is no usage billing: no charges for requests or data transfer. Pricing: https://expose.dev/#pricing (there is no separate pricing page). Sign up: https://expose.dev/register. ## MCP server The Expose MCP server at https://expose.dev/mcp (Streamable HTTP, OAuth sign-in) lets coding agents and chat apps list the user's open tunnels and inspect the latest requests that reached them (the last 50 per tunnel for up to 30 minutes, with credentials removed), close the user's tunnels, reserve and release subdomains, and add, verify, change and remove custom domains, with the user's own plan limits and team permissions. It can't open or replay tunnels: tunnels start with `expose share`. It works with Claude Code, Codex, VS Code (GitHub Copilot), Amp, Claude and ChatGPT, and with Zed, Goose and OpenCode. Cursor, Gemini CLI and Cline can't sign in to it yet. This is a remote MCP server for the user's Expose account; to make your own local MCP server reachable over HTTPS, share it with `expose share` (see the MCP server guide below). Agents can follow https://expose.dev/mcp/setup.md to connect it. Setup for each client: https://expose.dev/mcp. The server also supports MCP Events (draft SEP-3415) with webhook delivery: clients subscribe to request.completed on one of the user's tunnels, filtered by method, status and path, and get a signed webhook for every matching request, without headers or bodies. ChatGPT supports this today. - [Expose for agentic engineering](https://expose.dev/agentic-engineering): How coding agents use Expose tunnels and the MCP server to debug webhooks, compare requests and manage domains. - [MCP Events](https://expose.dev/mcp/events): The request.completed event, its filters, payload, webhook delivery and limits, and which clients receive events. - [How we built MCP Events](https://expose.dev/blog/how-we-built-mcp-events): Blog post on implementing SEP-3415 webhook delivery: subscription keys, callback verification, SSRF protection, rate limits, retries and what ChatGPT expects. Blog index: https://expose.dev/blog. ## Expose compared with other tunnels - [Expose as an ngrok alternative](https://expose.dev/ngrok-alternative): Plans, prices, custom domains and features of Expose and ngrok side by side, when each one fits better, and the ngrok commands in Expose. - [Skip ngrok's browser warning (ERR_NGROK_6024)](https://expose.dev/blog/ngrok-skip-browser-warning): The ngrok-skip-browser-warning header and the CORS preflight it needs, the User-Agent rule, the 7-day Visit cookie, paid plans, and the cases no workaround covers: client links, OAuth callbacks, iframes and QR codes. - [ngrok pricing in 2026](https://expose.dev/blog/ngrok-pricing): ngrok's Free, Hobbyist, Pay-as-you-go and Enterprise plans and usage rates as of November 13, 2026, what happens when you go over, and worked costs for a solo developer, a five-person team and client demos. - [ngrok alternatives compared](https://expose.dev/alternatives): Expose, ngrok, Cloudflare Tunnel, localtunnel, Tailscale Funnel, Pinggy, LocalXpose and Localtonet, and when each one fits. - [Expose vs Cloudflare Tunnel](https://expose.dev/cloudflare-tunnel-alternative): Stable URLs without a domain on Cloudflare, and a request dashboard that cloudflared doesn't have. - [Expose vs localtunnel](https://expose.dev/localtunnel-alternative): Reserved subdomains, a request dashboard and a single binary without Node.js. - [Expose vs Tailscale Funnel](https://expose.dev/tailscale-funnel-alternative): A public URL without a VPN, on your own domain, with webhook replay. - [Expose vs Pinggy](https://expose.dev/pinggy-alternative): Plans, persistent URLs, request inspection and AI agent support side by side. - [Expose vs LocalXpose](https://expose.dev/localxpose-alternative): No warning page on the free plan, prices and protocols side by side. - [Expose vs webhook.site](https://expose.dev/webhook-site-alternative): A hosted request bin compared with webhooks that reach your local handler, `expose catch-all` for payloads only, and other RequestBin alternatives. - [Expose vs Localtonet](https://expose.dev/localtonet-alternative): A flat yearly price instead of hourly per-tunnel billing, no warning page, one-CNAME custom domains, when Localtonet's UDP and proxy tunnels fit better, and other Localtonet alternatives. ## Free tools - [CGNAT check](https://expose.dev/cgnat-check): Compares the router's WAN IPv4 with the visitor's public IP to tell whether the connection is behind carrier-grade NAT (100.64.0.0/10), DS-Lite or double NAT, reads pasted traceroute output, and lists the fixes. Plain-text public IP for scripts: `curl -4 https://expose.dev/cgnat-check/ip`. ## Documentation Every documentation page is available as Markdown: add `.md` to its URL, for example https://expose.dev/docs/getting-started/installation.md. The full documentation in one file: https://expose.dev/llms-full.txt. ### Client - [Installation](https://expose.dev/docs/getting-started/installation): One-line install script for macOS, Linux and Windows, or Laravel Herd (preinstalled). Update with `expose self-update`. - [Authentication](https://expose.dev/docs/getting-started/authentication): `expose login` signs in through the browser and stores the token; `expose share` does this on first use. `expose token YOUR_TOKEN` sets a token manually. - [Share your first site](https://expose.dev/docs/getting-started/sharing-your-first-site): `expose share URL` for HTTP and HTTPS local sites and servers. - [Sharing Sites](https://expose.dev/docs/client/sharing): Use `expose` in a project directory (assumes `foldername.test`) or `expose share URL` explicitly. - [Custom Subdomains](https://expose.dev/docs/client/sharing#share-a-local-site-with-specific-subdomain) (Pro): Use `--subdomain=name` for the same URL every time. Useful for webhooks. - [Dashboard](https://expose.dev/docs/client/dashboard): Web dashboard at http://127.0.0.1:4040 shows all HTTP requests in real time. Inspect headers, body and response. Replay requests, with modifications, without re-triggering webhooks. - [Local Network Sharing](https://expose.dev/docs/client/lan-sharing): `--lan` shares a site with devices on the same network (phone, tablet, colleagues) without a server or an account, over plain HTTP. `--lan=PORT` picks the port (default 8080), `--qr-code` shows a QR code of the LAN URL. - [Password Protection](https://expose.dev/docs/client/basic-authentication): Add basic auth with `--basicAuth="user:pass"`. - [Magic Authentication](https://expose.dev/docs/client/magic-authentication): `--magic-auth` asks visitors for their email address before they see the site. `--magic-auth=@company.com,client@example.com` accepts only those domains and addresses. Expose doesn't send an email to confirm the address. - [Catch-All](https://expose.dev/docs/client/catch-all): `expose catch-all` gives you a URL that always returns 200 and logs all requests to the dashboard. Useful for inspecting webhooks without a local endpoint. - [Laravel Herd](https://expose.dev/docs/integrations/laravel-herd): Expose is built into Herd; share sites from the Herd UI or the terminal. - [Troubleshooting](https://expose.dev/docs/troubleshooting): Common issues and solutions. ### Expose Network (Pro) - [Global Servers](https://expose.dev/docs/expose-network/global-server-infrastructure): Seven Pro servers: eu-1 and eu-2 Frankfurt, us-1 New York, us-2 San Francisco, ap-1 Singapore, sa-1 São Paulo, au-1 Sydney. `expose servers` lists them; `expose default-server REGION` sets the default. - [Reserved Subdomains](https://expose.dev/docs/expose-network/reserved-subdomains): Reserve subdomains on sharedwithexpose.com so others can't take them. - [Custom Domains](https://expose.dev/docs/expose-network/custom-domains): Add your own domain via CNAME. Use `--domain=share.yourdomain.com`. Set the default with `expose default-domain`. - [Teams](https://expose.dev/docs/expose-network/teams): Share reserved subdomains and custom domains with team members. ### Advanced Usage - [Site Configuration (expose.yaml)](https://expose.dev/docs/advanced-usage/expose-yaml): Per-project config file for local-url, subdomain, custom-domain, expose-server and auth credentials. Shared with the team via version control. - [Request Plugins](https://expose.dev/docs/advanced-usage/request-plugins): Highlight webhook events in the CLI and dashboard. Built-in plugins for GitHub, Stripe, Paddle Billing and Magic Login. ### Self-Hosted Server - [Starting the Server](https://expose.dev/docs/server/server/starting-the-server): Run your own Expose server on your domain. Use `--validateAuthTokens` to require auth. - [SSL Support](https://expose.dev/docs/server/server/ssl): Use Nginx, Apache, HAProxy or Caddy as a reverse proxy for HTTPS, with WebSocket support. - [Admin Interface](https://expose.dev/docs/server/server/admin-interface): Manage users, view shared sites and configure server settings. - [Server Configuration](https://expose.dev/docs/server/server/server-configuration): Auth token validation, message of the day, maximum connection length, custom error messages. ### Guides - [Test Stripe webhooks locally](https://expose.dev/docs/guides/stripe-webhooks): Add the Expose URL as a Stripe webhook endpoint, verify the signature, inspect and replay events. - [Test Paddle webhooks locally](https://expose.dev/docs/guides/paddle-webhooks): Notification destinations, the Paddle-Signature header, simulations and replay. - [Test GitHub webhooks locally](https://expose.dev/docs/guides/github-webhooks): Payload URL, secret and X-Hub-Signature-256 for repositories and GitHub Apps. - [Develop Shopify apps and webhooks locally](https://expose.dev/docs/guides/shopify-webhooks): Expose as the tunnel for the app URL, OAuth redirects and HMAC-signed webhooks. - [Share a Next.js app](https://expose.dev/docs/guides/nextjs): `expose share http://localhost:3000`, `allowedDevOrigins` and auth URLs. - [Share a Vite dev server](https://expose.dev/docs/guides/vite): `expose share http://localhost:5173` and `server.allowedHosts`. - [Share a Laravel app](https://expose.dev/docs/guides/laravel): Herd, Valet, Sail and artisan serve, Vite assets and trusted proxies. - [Invalid Host header: the fix for each framework](https://expose.dev/blog/invalid-host-header): Why dev servers block tunnel hostnames (DNS rebinding) and the narrow allowlist setting for webpack-dev-server, Create React App, Vue CLI, Angular, Vite, Next.js (`**.sharedwithexpose.com`), Django and Rails, plus Host header rewriting in other tunnels. - [Test OAuth callbacks on localhost](https://expose.dev/docs/guides/oauth-callbacks): A stable HTTPS redirect URI for Google, GitHub, Slack and other providers. - [Test a local MCP server or ChatGPT app](https://expose.dev/docs/guides/mcp-server): A public URL for a local Streamable HTTP MCP server, for ChatGPT, Claude and MCP Inspector. ## CLI reference ``` expose # Share the current directory as foldername.test expose share URL # Share a local URL, e.g. http://localhost:3000 expose share URL --subdomain=X # Share with a custom subdomain (Pro) expose share URL --server=eu-1 # Share via a specific server (Pro) expose share URL --domain=X # Share via a custom domain (Pro) expose share URL --basicAuth="user:pass" # Add password protection expose share URL --magic-auth # Ask visitors for their email address expose share URL --lan # Share on the local network, no server or account needed expose share-port PORT # Share a local TCP port expose catch-all # Catch-all endpoint for webhook testing expose login # Log in through the browser expose token TOKEN # Set the authentication token manually expose info # Show the current configuration expose servers # List available servers expose default-server REGION # Set the default server expose default-domain DOMAIN # Set the default custom domain expose plugins # List request plugins expose plugins:manage # Enable or disable request plugins expose self-update # Update the Expose client ```