Terms of Service
By installing the devlink365 package, running it against a local server, or using the software in any form, you agree to the terms below.
1. The software
DevLink365 is free, open-source software that creates a temporary public HTTPS link to a web server already running on your own machine. It does not host your app, deploy anything, or require an account.
2. Open source and license
The code is released under the MIT license. You may read it, modify it, and run your own copy, including for commercial use, subject to that license.
3. Your responsibilities
You are responsible for what you expose through a link. A DevLink365 URL points the public internet at a server on your machine, so do not share anything you would not hand to a stranger, and do not point a link at an app holding production data or real credentials.
4. Acceptable use
Do not use DevLink365 to serve illegal content, distribute malware, run phishing or deceptive pages, or attack or overload other systems. Tunnels used for these purposes are terminated, and abuse may result in a block from the shared relay.
5. The hosted relay
The default relay at relay.devlink365.dev is provided as a convenience, on a best-effort basis, with rate limits and a hard link lifetime. It may be unavailable at times and carries no uptime guarantee. You can always run your own relay instead, as described in the documentation.
6. Prerelease software, provided as is
DevLink365 is early software provided without warranty of any kind, express or implied. To the maximum extent permitted by law, the authors are not liable for any damages arising from its use.
7. Free, with fair use
There are no paid tiers. Reasonable limits apply so that a single user cannot exhaust the shared relay: request bodies are capped, visitors are rate limited per tunnel, and one machine can only hold a bounded number of links at a time.
8. Changes and termination
You can stop using DevLink365 at any time by closing the CLI, which ends the tunnel immediately. These terms may be updated as the product matures; continued use after a change means you accept the new terms.
Privacy Policy
DevLink365 runs on your machine and forwards your traffic. It is built to keep as little as possible.
1. What runs where
The CLI runs locally on your computer. Traffic between a visitor and your app is carried through whichever relay you connect to. By default that is relay.devlink365.dev; you can point it at your own relay instead.
2. What the relay processes
To route a request to your machine and the response back, the relay passes the HTTP traffic of your tunnel through memory. It does not store your request or response bodies.
3. What the relay keeps
Only operational metadata needed to run the service and prevent abuse: a tunnel id, coarse timing and request counts, and rate-limit state. A link and its routing state are discarded when the tunnel closes or expires.
4. This website
The site at devlink365.dev is a static site. It sets no tracking cookies and runs no third-party analytics.
5. Self-hosting
Run your own relay and none of your traffic touches our infrastructure at all. The whole system is designed so you never have to trust a server you do not control.
6. Security
URLs come from a cryptographic random source and are not enumerable, every link expires with a hard 24-hour ceiling, and closing the CLI kills the link immediately. Even so, anyone holding a live URL can reach your app, so treat any active link as public.
Attributions
DevLink365 is built and maintained by Rahul Awasthi, Founder and CEO.
The CLI and library are written in TypeScript with a zero-dependency WebSocket implementation built from the RFC. The relay runs on Fly.io behind a wildcard TLS certificate, and this website is served from Vercel. Thanks to the open-source projects and framework communities whose tools DevLink365 forwards every day.
Typography: headlines and the DevLink365 wordmark are set in MN Celesta. Body text is set in IBM Plex Sans, designed by Mike Abbink for IBM and licensed under the SIL Open Font License 1.1. Interface labels, commands and URLs use the system monospace stack.