Use Cases

Portex is designed to solve real-world development challenges. Here are some common scenarios where Portex shines.

1. Webhook Development & Testing

Building integrations with Stripe, GitHub, or Twilio? These services need a public URL to send webhooks. Instead of deploying to staging every time you make a change, use Portex:

        # Start your local server
        npm run dev

        # Expose it with Portex
        portex start --port 3000 --subdomain stripe-test
    

Now configure your webhook URL as https://stripe-test.portex.space/webhooks and see requests in real-time.

2. Client Demos & Prototypes

Need to show a work-in-progress to a client? Don't waste time deploying to a staging server:

portex start --port 8080 --pin 1234

Share the URL with your client along with the PIN. They can access your local environment securely without you exposing it to the entire internet.

3. Mobile App Development

Testing your backend API on a physical device? Portex generates a QR code you can scan:

portex start --port 5000

Scan the QR code with your phone and your mobile app can now talk to your local API over HTTPS.

4. Static Site Sharing

Built a static site with Vite, Next.js, or Hugo? Share it instantly without configuring a web server:

        npm run build
        portex share ./dist
    

Portex starts a lightweight HTTP server and tunnels it automatically.

5. IoT & Embedded Development

Testing IoT devices that need to communicate with a cloud service? Point them to your Portex tunnel and debug locally:

portex start --port 8000 --subdomain iot-gateway

Your devices can now send data to https://iot-gateway.portex.space while you iterate on your local code.

6. API Testing & Documentation

Writing API documentation with tools like Postman or Insomnia? Use Portex to expose your local API and share the collection with your team:

portex start --port 4000 --subdomain api-docs

Pro Tip Combine Portex with tools like ngrok-alternative request inspection to debug complex integrations faster.