meshr / Platform / Public Endpoints
Public Endpoints

A stable URL for any internal service.

Expose an HTTP or TCP service on a persistent, TLS-secured URL — no ingress controller, no nginx config, no random subdomains that change on every restart. Multi-target load balancing is on the way.

  • Persistent URLs — survive restarts and redeploys
  • Automatic TLS, always on — zero certbot
  • Zero open inbound ports on your network
  • Scoped to your team, not the public internet

api.your-team.meshr.to

HTTP · TLS · Persistent

Active
1.2kreq/s
18msp50
99.9%uptime

Forwards to

10.0.0.5:8080
up
Coming soon Multiple weighted targets with health checks
Auto TLS
How it works

From private service to public URL in three steps.

No DNS console, no certbot scripts, no LoadBalancer Service YAML.

1

Create the tunnel

Pick a name and a protocol (HTTP or TCP). meshr assigns a stable URL on the spot, with TLS already terminated.

meshr tunnel create api --port 8080
2

Point it at a service

The tunnel forwards to one service on your mesh — a local port or a peer. No public port to open, no inbound firewall change.

meshr tunnel up api → 10.0.0.5:8080
3

Ship the URL

The URL is persistent — it survives restarts and redeploys. Hard-code it in clients, webhooks, and mobile builds.

curl https://api.your-team.meshr.to/health
{"ok":true}
Capabilities

Built for real integrations, not just demos.

Persistent endpoints replace ad-hoc port-forwards and disposable tunnel links for the services your team actually depends on.

Persistent URLs, not session tokens

Endpoint URLs survive restarts, version bumps, and service swaps. Hard-code them in client apps, ship them to mobile builds, paste them in a Postman collection — they keep working.

Disposableu7sj-throwaway-link
Endpointapi.your-team.meshr.to

Automatic TLS — no certbot

Every endpoint is served over HTTPS with a certificate issued and renewed for you. You never run a renewal cron or touch an ACME client.

  • HTTPS on by default
  • Issued and auto-renewed for you
  • No renewal cron, no certbot
  • HTTP and TCP protocols
Coming soon

Multi-target load balancing

Planned: point one endpoint at several mesh peers with round-robin or weighted distribution, active health checks, and a drain mode for graceful rollouts. Today each endpoint forwards to a single service.

  • Round-robin and weighted policies
  • Health checks remove failed targets
  • Drain mode for graceful shutdown
  • Weighted canary / A-B rollouts

Bring your own domain

Map an endpoint to a domain you own with TLS issued and renewed automatically. See Custom Domains for the full setup.

Your domainapi.acme.com
or a free subdomainapi.your-team.meshr.to
Why persistent

A URL you can ship, not just share.

meshr EndpointThrowaway link
URL stability Persistent — survives restarts Spin-up-and-throw-away
TLS Automatic, always on Manual / none
Public ports Zero open inbound ports Port forward / expose
Scope Private to your team Whoever has the URL
Best for Webhooks, demos, mobile, integrations One-off local share

Give your service a real URL.

Persistent, TLS-secured endpoints are free while we're in beta. No credit card, no commitments.