Alternatives to ngrok logo

Alternatives to ngrok

NGINX, Heroku, PageKite, Postman, and MAMP are the most popular alternatives and competitors to ngrok.
219
356
+ 1
52

What is ngrok and what are its top alternatives?

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.
ngrok is a tool in the localhost Tools category of a tech stack.
ngrok is an open source tool with 20.9K GitHub stars and 3.8K GitHub forks. Here’s a link to ngrok's open source repository on GitHub

Top Alternatives to ngrok

  • NGINX

    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

  • Heroku

    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

  • 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. ...

  • Postman

    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • 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. ...

  • Termius

    Termius

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

  • GoTTY

    GoTTY

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

  • warp

    warp

    warp lets you securely share your terminal with one simple command: warp open. When connected to your warp, clients can see your terminal exactly as if they were sitting next to you. You can also grant them write access, the equivalent of handing them your keyboard. ...

ngrok alternatives & related posts

NGINX logo

NGINX

92.7K
43.1K
5.5K
A high performance free open source web server powering busiest sites on the Internet.
92.7K
43.1K
+ 1
5.5K
PROS OF NGINX
  • 1.4K
    High-performance http server
  • 896
    Performance
  • 728
    Easy to configure
  • 606
    Open source
  • 529
    Load balancer
  • 286
    Scalability
  • 285
    Free
  • 222
    Web server
  • 173
    Simplicity
  • 134
    Easy setup
  • 29
    Content caching
  • 19
    Web Accelerator
  • 14
    Capability
  • 13
    Fast
  • 11
    Predictability
  • 10
    High-latency
  • 7
    Reverse Proxy
  • 6
    Fast and lightweight
  • 6
    Supports http/2
  • 4
    Enterprise version
  • 4
    Lots of Modules
  • 4
    The best of them
  • 4
    Great Community
  • 3
    Streaming media
  • 3
    Embedded Lua scripting
  • 3
    Reversy Proxy
  • 3
    High perfomance proxy server
  • 3
    Streaming media delivery
  • 2
    Slim
  • 2
    Lightweight
  • 2
    Fast and easy to set up
  • 2
    saltstack
  • 1
    Ingress controller
  • 1
    Virtual hosting
  • 1
    Narrow focus. Easy to configure. Fast
  • 1
    Along with Redis Cache its the Most superior
  • 1
    GRPC-Web
  • 0
    A
CONS OF NGINX
  • 8
    Advanced features require subscription

related NGINX posts

Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

See more
Gabriel Pa
Shared insights
on
Traefik
NGINX
at

We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

See more
Heroku logo

Heroku

19.6K
15.2K
3.2K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
19.6K
15.2K
+ 1
3.2K
PROS OF HEROKU
  • 704
    Easy deployment
  • 460
    Free for side projects
  • 374
    Huge time-saver
  • 348
    Simple scaling
  • 261
    Low devops skills required
  • 190
    Easy setup
  • 174
    Add-ons for almost everything
  • 154
    Beginner friendly
  • 150
    Better for startups
  • 133
    Low learning curve
  • 48
    Postgres hosting
  • 41
    Easy to add collaborators
  • 30
    Faster development
  • 24
    Awesome documentation
  • 19
    Simple rollback
  • 19
    Focus on product, not deployment
  • 15
    Natural companion for rails development
  • 15
    Easy integration
  • 12
    Great customer support
  • 8
    GitHub integration
  • 6
    No-ops
  • 6
    Painless & well documented
  • 4
    I love that they make it free to launch a side project
  • 4
    Free
  • 3
    Great UI
  • 3
    Just works
  • 2
    PostgreSQL forking and following
  • 2
    MySQL extension
  • 0
    Security
  • 0
    Sec
CONS OF HEROKU
  • 23
    Super expensive
  • 6
    Not a whole lot of flexibility
  • 5
    No usable MySQL option
  • 5
    Storage
  • 4
    Low performance on free tier
  • 1
    24/7 support is $1,000 per month

related Heroku posts

Russel Werner
Lead Engineer at StackShare · | 29 upvotes · 1.5M views

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.1M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
PageKite logo

PageKite

8
63
0
Make local websites or SSH servers publicly accessible in mere seconds
8
63
+ 1
0
PROS OF PAGEKITE
    Be the first to leave a pro
    CONS OF PAGEKITE
      Be the first to leave a con

      related PageKite posts

      Postman logo

      Postman

      62.2K
      50.3K
      1.8K
      Only complete API development environment
      62.2K
      50.3K
      + 1
      1.8K
      PROS OF POSTMAN
      • 485
        Easy to use
      • 369
        Great tool
      • 275
        Makes developing rest api's easy peasy
      • 156
        Easy setup, looks good
      • 143
        The best api workflow out there
      • 53
        It's the best
      • 53
        History feature
      • 44
        Adds real value to my workflow
      • 42
        Great interface that magically predicts your needs
      • 34
        The best in class app
      • 11
        Can save and share script
      • 9
        Fully featured without looking cluttered
      • 7
        Collections
      • 7
        Global/Environment Variables
      • 7
        Option to run scrips
      • 6
        Shareable Collections
      • 6
        Dead simple and useful. Excellent
      • 6
        Dark theme easy on the eyes
      • 5
        Awesome customer support
      • 5
        Great integration with newman
      • 4
        The test script is useful
      • 3
        Makes testing API's as easy as 1,2,3
      • 3
        Easy as pie
      • 3
        Saves responses
      • 3
        This has simplified my testing significantly
      • 3
        Simple
      • 3
        Documentation
      • 2
        Mocking API calls with predefined response
      • 2
        I'd recommend it to everyone who works with apis
      • 2
        API-network
      • 1
        Easy to setup, test and provides test storage
      • 1
        Continuous integration using newman
      • 1
        Graph
      • 1
        Pre-request Script and Test attributes are invaluable
      • 1
        Postman Runner CI Integration
      • 1
        Now supports GraphQL
      • 0
        <a href="http://fixbit.com/">useful tool</a>
      • 0
        Runner
      CONS OF POSTMAN
      • 9
        Stores credentials in HTTP
      • 7
        Poor GraphQL support
      • 7
        Bloated features and UI
      • 6
        Cumbersome to switch authentication tokens
      • 2
        Expensive
      • 1
        Support websocket
      • 1
        Import curl
      • 1
        Import swagger
      • 1
        Can't prompt for per-request variables

      related Postman posts

      Noah Zoschke
      Engineering Manager at Segment · | 30 upvotes · 2M views

      We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

      Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

      Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

      This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

      Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

      Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

      Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2M views

      Our whole Node.js backend stack consists of the following tools:

      • Lerna as a tool for multi package and multi repository management
      • npm as package manager
      • NestJS as Node.js framework
      • TypeScript as programming language
      • ExpressJS as web server
      • Swagger UI for visualizing and interacting with the API’s resources
      • Postman as a tool for API development
      • TypeORM as object relational mapping layer
      • JSON Web Token for access token management

      The main reason we have chosen Node.js over PHP is related to the following artifacts:

      • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
      • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
      • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
      • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
      See more
      MAMP logo

      MAMP

      49
      95
      1
      A free, local server environment
      49
      95
      + 1
      1
      PROS OF MAMP
      • 1
        Great Support of Native Languages
      CONS OF MAMP
        Be the first to leave a con

        related MAMP posts

        Helfried Plenk
        Senior Partner at IBS IT-DL GmbH · | 1 upvote · 73.6K views
        Shared insights
        on
        MAMP
        XAMPP
        Joomla!

        installing a local Joomla! 3.9 website for testing - I already downloaded an installed XAMPP - when now reading some other docs I found mentioned MAMP ... have I to change?

        See more
        Termius logo

        Termius

        47
        46
        9
        Use modern SSH for macOS, Windows and Linux to organize, access, and connect to your servers
        47
        46
        + 1
        9
        PROS OF TERMIUS
        • 2
          Free
        • 2
          Data Sharing
        • 2
          Mobile and Desktop
        • 1
          Proxy
        • 1
          Mosh
        • 1
          Jump hosts
        CONS OF TERMIUS
          Be the first to leave a con

          related Termius posts

          GoTTY logo

          GoTTY

          15
          47
          8
          Share your terminal as a web application
          15
          47
          + 1
          8
          PROS OF GOTTY
          • 5
            Easy setup
          • 3
            Nice Feature
          CONS OF GOTTY
            Be the first to leave a con

            related GoTTY posts

            warp logo

            warp

            9
            23
            1
            Secure and simple terminal sharing
            9
            23
            + 1
            1
            PROS OF WARP
            • 1
              Lots of safe code
            CONS OF WARP
              Be the first to leave a con

              related warp posts