StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Build Automation
  4. Localhost Tools
  5. Inlets vs ngrok

Inlets vs ngrok

OverviewComparisonAlternatives

Overview

ngrok
ngrok
Stacks419
Followers457
Votes57
GitHub Stars24.4K
Forks4.3K
Inlets
Inlets
Stacks2
Followers14
Votes0

Inlets vs ngrok: What are the differences?

Introduction: In this comparison, we will outline the key differences between Inlets and ngrok, two popular tools for exposing local services to the internet.

1. Ease of Use: Inlets requires more setup and configurations compared to ngrok, which offers a simpler and more user-friendly interface for tunneling services.

2. Self-hosting: Inlets allows users to self-host their own tunnel server, providing more control and flexibility over the tunneling process, while ngrok relies on their cloud service for tunneling.

3. Pricing: Inlets is open-source and free to use, making it a cost-effective option for those looking to tunnel services without any additional costs. On the other hand, ngrok offers different pricing tiers based on usage, which may be a consideration for users with high traffic volumes.

4. Protocol Support: Inlets supports TCP and UDP protocols for tunneling services, offering more versatility in the types of services that can be exposed. Ngrok, on the other hand, primarily focuses on HTTP and HTTPS protocols.

5. Custom Domain Support: Inlets provides the ability to use custom domains for accessing tunnel endpoints, offering a more personalized and branded experience for users. Ngrok, however, requires users to upgrade to a paid plan for custom subdomains.

6. Security: Inlets offers end-to-end encryption for tunneling traffic, enhancing security and privacy for users. Ngrok also provides a secure tunneling experience but lacks the ability for self-hosted servers, which may raise security concerns for some users.

In Summary, Inlets and ngrok differ in ease of use, self-hosting capabilities, pricing, protocol support, custom domain options, and security features.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

ngrok
ngrok
Inlets
Inlets

ngrok is a reverse proxy that creates a secure tunnel between from a public endpoint to a locally running web service. ngrok captures and analyzes all traffic over the tunnel for later inspection and replay.

You can use it to connect HTTP and TCP services between networks securely. Through an encrypted websocket, it can penetrate firewalls, NAT, captive portals, and other restrictive networks lowering the barrier to entry.

Expose any http service behind a NAT or firewall to the internet on a subdomain of ngrok.com;Expose any tcp service behind a NAT or firewall to the internet on a random port of ngrok.com;Inspect all http requests/responses that are transmitted over the tunnel;Replay any request that was transmitted over the tunnel
Low-maintenance, secure, and quick alternative to a VPN; Provide APIs endpoints to consume data from third-parties and partners; For command and control of: services within private VPCs, IoT devices and Point of Sale (PoS); Create a hybrid cloud between existing servers and public cloud for: CI, e2e testing, or for accessing legacy systems; As an alternative to an expensive data-center uplink such as AWS Direct Connect or Azure Express Route.
Statistics
GitHub Stars
24.4K
GitHub Stars
-
GitHub Forks
4.3K
GitHub Forks
-
Stacks
419
Stacks
2
Followers
457
Followers
14
Votes
57
Votes
0
Pros & Cons
Pros
  • 26
    Easy to use
  • 11
    Super-fast
  • 7
    Free
  • 6
    Awesome traffic analysis page
  • 5
    Reliable custom domains
Cons
  • 5
    Doesn't Support UDP
  • 1
    El tunel SSH cambia de dominio constantemente
No community feedback yet
Integrations
Twilio SendGrid
Twilio SendGrid
GitHub
GitHub
Slack
Slack
Docker
Docker
Kubernetes
Kubernetes

What are some alternatives to ngrok, Inlets?

HAProxy

HAProxy

HAProxy (High Availability Proxy) is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications.

Traefik

Traefik

A modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components and configures itself automatically and dynamically.

AWS Elastic Load Balancing (ELB)

AWS Elastic Load Balancing (ELB)

With Elastic Load Balancing, you can add and remove EC2 instances as your needs change without disrupting the overall flow of information. If one EC2 instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running EC2 instances. If the failed EC2 instance is restored, Elastic Load Balancing restores the traffic to that instance. Elastic Load Balancing offers clients a single point of contact, and it can also serve as the first line of defense against attacks on your network. You can offload the work of encryption and decryption to Elastic Load Balancing, so your servers can focus on their main task.

Fly

Fly

Deploy apps through our global load balancer with minimal shenanigans. All Fly-enabled applications get free SSL certificates, accept traffic through our global network of datacenters, and encrypt all traffic from visitors through to application servers.

Termius

Termius

The #1 cross-platform terminal with built-in ssh client which works as your own portable server management system in any situation.

Envoy

Envoy

Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.

GoTTY

GoTTY

GoTTY is a simple command line tool that turns your CLI tools into web applications.

Hipache

Hipache

Hipache is a distributed proxy designed to route high volumes of http and websocket traffic to unusually large numbers of virtual hosts, in a highly dynamic topology where backends are added and removed several times per second. It is particularly well-suited for PaaS (platform-as-a-service) and other environments that are both business-critical and multi-tenant.

PageKite

PageKite

PageKite is a system for exposing localhost servers to the public Internet. It is most commonly used to make local web servers or SSH servers publicly visible, although almost any TCP-based protocol can work if the client knows how to use an HTTP proxy.

MAMP

MAMP

It can be installed under macOS and Windows with just a few clicks. It provides them with all the tools they need to run WordPress on their desktop PC for testing or development purposes, for example. It doesn't matter if you prefer Apache or Nginx or if you want to work with PHP, Python, Perl or Ruby.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana