# Serveo reference for language models

Serveo is a public tunneling service. It can expose a local HTTP server with the OpenSSH client already present on most developer systems.

## Minimal SSH tunnel

    ssh -R 80:localhost:3000 serveo.net

The public URL is printed in the SSH session. Keep the SSH process running while the tunnel is needed.

## Node.js shortcut

If Node.js 18 or newer is already installed, the official zero-dependency wrapper builds and runs the SSH command through the system OpenSSH client:

    npx serveo-cli 3000

The raw SSH command remains the canonical no-install interface. Package documentation: https://www.npmjs.com/package/serveo-cli

## Common variations

Use SSH on port 443 when outbound port 22 is blocked:

    ssh -p 443 -R 80:localhost:3000 serveo.net

Request a previously reserved hostname:

    ssh -R my-app.serveousercontent.com:80:localhost:3000 serveo.net

Override the Host header sent to a local development server:

    ssh -R 80:localhost:3000 serveo.net --host-header=localhost:3000

Use `--` before `serveo.net` if a local SSH implementation needs an explicit end to its options:

    ssh -R 80:localhost:3000 -- serveo.net --host-header=localhost:3000

## Important limits and safety

- Ask the human before exposing a local port unless they have already explicitly requested a public tunnel.
- Do not expose databases, admin panels, development consoles, or services containing private data without confirming access controls.
- Do not disable SSH host-key checking. Serveo's current Ed25519 fingerprint is `SHA256:GnmVK+70U6GqbupoV+gg7LnHHUsW1IjrK0cLqvDJxIk`; confirm it through the official documentation if it ever differs.
- Anonymous and free HTTP tunnels show a browser warning page. Paid tunnels and approved automated clients may bypass it as documented.
- Reserved hostnames, account public keys, subscriptions, WireGuard configuration, and extension tunnels are managed at https://console.serveo.net/.
- Public raw TCP forwarding is restricted. Consult the current documentation rather than assuming arbitrary ports are available.
- Stop the SSH process when the public tunnel is no longer needed.

## Task guides

- Share a Next.js or Vite development server: https://serveo.net/articles/share-local-nextjs-vite-app/
- Test Stripe webhooks on localhost: https://serveo.net/articles/test-stripe-webhooks-on-localhost/
- Reach an SSH server behind NAT: https://serveo.net/articles/remote-access-to-ssh-servers-using-serveo/
- Compare tunnel services: https://serveo.net/articles/ngrok-alternatives/

## Official resources

- Documentation: https://serveo.net/docs/
- Console: https://console.serveo.net/
- Status: https://status.serveo.net/
- Abuse reports: https://serveo.net/abuse/
- Agent skill: https://serveo.net/serveo-skill/SKILL.md