One-click deployment, smaller attack surface

Lprintf: publish only what you mean to expose

Copy one deployment prompt to publish your local service at a public HTTPS address. No dedicated public IP or manual certificate setup; expose only explicitly selected routes, then review, disable, or delete them at any time.

See the Agent one-line deployment

No inbound service portOne explicit route at a timeDisable or delete anytime

From local process to public link

One command, one route, visible checks

An Agent can prepare the deployment, but Lprintf still makes the trust boundary explicit: connect the client, choose the target, verify the link, then remove it.

Prepare a Token and prompt

Get a temporary Token without signing in, save it to the project .env, and send the deployment prompt to an Agent on the service machine.

Publish one explicit route

Set a readable subdomain and target port. The gateway handles HTTPS and forwards only the route you configure.

Verify and revoke

Check online status and traffic, then disable or delete a mapping when the link is no longer needed.

Security is part of the workflow

Convenience with a deliberately smaller attack surface

A public link changes the trust boundary. Lprintf keeps it narrow by avoiding a direct inbound port on your service and requiring an explicit route before anything is public.

Outbound client connection

Your service does not need its own public listener. The Client connects out to the managed gateway; the gateway exposes only configured HTTPS routes.

Explicit target, no guessing

The platform never scans or publishes local ports on your behalf. A mapping exists only after you choose its target and name.

HTTPS at the edge

TLS, domain routing and access logs stay at the managed gateway instead of being copied into every local service.

Immediate cleanup

Delete or disable mappings when work ends. The safest public endpoint is the one you no longer need.