Tool profile
localtunnel: cost, fit and limits
localtunnel is an open source tool that shares a local web service on a public HTTPS URL, installed with Node.js and npm. The project page names @TheBoroer as running the project pages and @defunctzombie as its creator, lists client libraries on a wiki, and shows sponsorship and donation options rather than prices.
What to know first
localtunnel's project page is short. It says the tool installs with Node.js and npm, shares a local web service over HTTPS, points to client libraries for other languages on its wiki and links the source on GitHub. It lists no pricing, limits, data handling statement or support terms, and it does not say whether the tool is free or open source. Only sponsorship and donation options are shown.
localtunnel at a glance
| Maker | Not stated on the vendor pages (run by @TheBoroer on the project pages; created by @defunctzombie), Not stated on the vendor pages |
|---|---|
| Free plan | Free trial only |
| Entry price | Quote only |
| API access | No |
| Category | Best AI Localhost Tunneling Tools in 2026, rank 11 of 12 |
| Website | localtunnel.me |
Who localtunnel is best for
Node.js developers who need a fast link
Installation through npm fits a JavaScript workflow, so a developer can publish a local web port without adding another package manager.
Developers using other languages
The wiki documents client libraries for languages beyond JavaScript, so a team can script a tunnel from its own stack.
Users who want to read the code
The source is on GitHub, which lets a security-minded developer inspect how the client behaves before using it for demos.
localtunnel plans and pricing
| Plan | Price | What it includes |
|---|---|---|
| Open source client | Not stated on the project page | Install with Node.js and npm, with client libraries documented on the wiki and the source code available on GitHub for review. |
Checked November 2026.
What localtunnel does
- Public HTTPS URL
- The tool shares a local web service on a public HTTPS URL, which covers quick demos, mobile testing and receiving a webhook while you are still developing the handler.
- npm installation
- Installation uses Node.js and npm, so developers who already work in JavaScript do not need a separate runtime, a system-level package or a container to start a tunnel.
- Client libraries
- A wiki documents client libraries for languages beyond JavaScript, which lets projects written in other stacks open a tunnel from inside their own code instead of shelling out.
- Public source code
- The source code is on GitHub, so users can read the client and follow the project's issues and releases before relying on it for demos or for webhook testing.
- Funding model
- The page shows sponsorship and donation options instead of a plan list, so there is nothing to buy on it and no price to compare against other tools.
How localtunnel handles your data
The project page we read says nothing about whether tunnel traffic is stored, whether it is used to train AI models, where the public relay runs or whether any certification applies, so the vendor's policy was not checked for those points. It names @TheBoroer as running the project pages without giving a company or headquarters. Because a public relay carries your requests, avoid sending secrets or customer data through it until you have read the source or run your own server according to the project documentation.
Where localtunnel falls short in practice
- No stated limits. The page publishes no tunnel count, time limit or bandwidth cap, so a user learns the limits only by running into them in the middle of a demo.
- Unclear commercial status. The page does not say whether the tool is free, open source or supported, and it shows only sponsorship options, which makes procurement review difficult.
- Thin documentation on the page. One page was read, so features such as custom subdomains, authentication or request inspection are unverified for this review and need checking in the repository.
Works with
Alternatives to localtunnel
localtunnel: common questions
How do I install localtunnel?
The project page says it installs with Node.js and npm. Client libraries for other languages are documented on a wiki, and the source is on GitHub. The page does not list system requirements beyond Node.js, so check the repository for the current version support.
Is localtunnel free?
The project page lists no prices and does not say whether the tool is free or open source. It shows only sponsorship and donation options. The source is on GitHub, so read the repository license before using it commercially. Confirm that before commercial use.
Who runs localtunnel?
The page names @TheBoroer as running the project pages and @defunctzombie as the creator. It gives no company, address or contact for support, so treat it as a community project and read the GitHub issues before depending on it. Ask there about upkeep.
Does localtunnel give HTTPS?
Yes, the page says it shares a local web service on a public HTTPS URL. How certificates are issued, and whether custom subdomains are possible, were not described on the page we read, so test the behavior before registering the address with a webhook sender.
Can I use localtunnel from languages other than JavaScript?
The page points to a wiki that documents client libraries for other languages. It does not list which languages or how well maintained each library is, so check the wiki and the library repositories before building a workflow around one.