Alternatives to Runscope logo

Alternatives to Runscope

Postman, BlazeMeter, New Relic, Pingdom, and Apigee are the most popular alternatives and competitors to Runscope.
128
153
+ 1
59

What is Runscope and what are its top alternatives?

Keep tabs on all aspects of your API's performance with uptime monitoring, integration testing, logging and real-time monitoring.
Runscope is a tool in the API Tools category of a tech stack.

Top Alternatives to Runscope

  • Postman

    Postman

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

  • BlazeMeter

    BlazeMeter

    Simulate any user scenario for webapps, websites, mobile apps or web services. 100% Apache JMeter compatible. Scalable from 1 to 1,000,000+ concurrent users.<br> ...

  • New Relic

    New Relic

    New Relic is the all-in-one web application performance tool that lets you see performance from the end user experience, through servers, and down to the line of application code. ...

  • Pingdom

    Pingdom

    Pingdom is an uptime monitoring service. When problems happen with a site that Pingdom monitors, it immediately alerts the owner so the problem can be taken care of. ...

  • Apigee

    Apigee

    API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world. ...

  • Assertible

    Assertible

    Reduce bugs in web applications by using Assertible to create an automated QA pipeline that helps you catch failures & ship code faster. ...

  • Kong

    Kong

    Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform. ...

  • Amazon API Gateway

    Amazon API Gateway

    Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management. ...

Runscope alternatives & related posts

Postman logo

Postman

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

related Postman posts

Noah Zoschke
Engineering Manager at Segment · | 30 upvotes · 1.9M 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 · | 24 upvotes · 1.7M 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
BlazeMeter logo

BlazeMeter

52
113
12
The Load Testing Platform for Developers
52
113
+ 1
12
PROS OF BLAZEMETER
  • 9
    I can run load tests without needing JMeter scripts.
  • 3
    Easy to prepare JMeter workers
CONS OF BLAZEMETER
  • 1
    UI centric

related BlazeMeter posts

New Relic logo

New Relic

18.1K
6.3K
1.9K
SaaS Application Performance Management for Ruby, PHP, .Net, Java, Python, and Node.js Apps.
18.1K
6.3K
+ 1
1.9K
PROS OF NEW RELIC
  • 414
    Easy setup
  • 345
    Really powerful
  • 244
    Awesome visualization
  • 194
    Ease of use
  • 151
    Great ui
  • 107
    Free tier
  • 81
    Great tool for insights
  • 66
    Heroku Integration
  • 55
    Market leader
  • 49
    Peace of mind
  • 21
    Push notifications
  • 20
    Email notifications
  • 17
    Heroku Add-on
  • 16
    Error Detection and Alerting
  • 12
    Multiple language support
  • 11
    SQL Analysis
  • 11
    Server Resources Monitoring
  • 9
    Transaction Tracing
  • 8
    Apdex Scores
  • 8
    Azure Add-on
  • 7
    Analysis of CPU, Disk, Memory, and Network
  • 6
    Detailed reports
  • 6
    Performance of External Services
  • 6
    Error Analysis
  • 6
    Application Availability Monitoring and Alerting
  • 6
    Application Response Times
  • 5
    JVM Performance Analyzer (Java)
  • 5
    Most Time Consuming Transactions
  • 4
    Easy to use
  • 4
    Top Database Operations
  • 4
    Browser Transaction Tracing
  • 3
    Application Map
  • 3
    Pagoda Box integration
  • 3
    Custom Dashboards
  • 3
    Weekly Performance Email
  • 2
    Easy visibility
  • 2
    App Speed Index
  • 2
    Easy to setup
  • 1
    Real User Monitoring Analysis and Breakdown
  • 1
    Incident Detection and Alerting
  • 1
    Real User Monitoring Overview
  • 1
    Worst Transactions by User Dissatisfaction
  • 1
    Metric Data Resolution
  • 1
    Metric Data Retention
  • 1
    Team Collaboration Tools
  • 1
    Super Expensive
  • 1
    Time Comparisons
  • 1
    Access to Performance Data API
  • 1
    Background Jobs Transaction Analysis
  • 1
    Free
  • 1
    Best of the best, what more can you ask for
  • 1
    Best monitoring on the market
  • 1
    Rails integration
  • 0
    Exceptions
  • 0
    Ddd
CONS OF NEW RELIC
  • 19
    Pricing model doesn't suit microservices
  • 10
    UI isn't great
  • 7
    Expensive
  • 7
    Visualizations aren't very helpful
  • 5
    Hard to understand why things in your app are breaking

related New Relic posts

Farzeem Diamond Jiwani
Software Engineer at IVP · | 5 upvotes · 522.9K views

Hey there! We are looking at Datadog, Dynatrace, AppDynamics, and New Relic as options for our web application monitoring.

Current Environment: .NET Core Web app hosted on Microsoft IIS

Future Environment: Web app will be hosted on Microsoft Azure

Tech Stacks: IIS, RabbitMQ, Redis, Microsoft SQL Server

Requirement: Infra Monitoring, APM, Real - User Monitoring (User activity monitoring i.e., time spent on a page, most active page, etc.), Service Tracing, Root Cause Analysis, and Centralized Log Management.

Please advise on the above. Thanks!

See more
Sebastian Gębski

Regarding Continuous Integration - we've started with something very easy to set up - CircleCI , but with time we're adding more & more complex pipelines - we use Jenkins to configure & run those. It's much more effort, but at some point we had to pay for the flexibility we expected. Our source code version control is Git (which probably doesn't require a rationale these days) and we keep repos in GitHub - since the very beginning & we never considered moving out. Our primary monitoring these days is in New Relic (Ruby & SPA apps) and AppSignal (Elixir apps) - we're considering unifying it in New Relic , but this will require some improvements in Elixir app observability. For error reporting we use Sentry (a very popular choice in this class) & we collect our distributed logs using Logentries (to avoid semi-manual handling here).

See more
Pingdom logo

Pingdom

2.4K
1.4K
580
Uptime and performance monitoring made easy
2.4K
1.4K
+ 1
580
PROS OF PINGDOM
  • 225
    Simple and reliable
  • 103
    Monitoring your websites
  • 75
    Easy to use dashboard
  • 65
    Email, text & twitter alerts
  • 43
    Free tier
  • 23
    Performance data
  • 14
    Detailed Reports
  • 11
    Email Reports
  • 9
    Mobile App
  • 9
    Root Cause Analysis
  • 1
    30-day risk free trial
  • 1
    Easy setup
  • 1
    IOS app
CONS OF PINGDOM
  • 3
    UI is incredibly complicated
  • 3
    Expensive
  • 2
    Hard to set up alerts properly

related Pingdom posts

Jerome Dalbert
Senior Backend Engineer at StackShare · | 4 upvotes · 255.6K views

We currently monitor performance with the following tools:

  1. Heroku Metrics: our main app is Hosted on Heroku, so it is the best place to get quick server metrics like memory usage, load averages, or response times.
  2. Good old New Relic for detailed general metrics, including transaction times.
  3. Skylight for more specific Rails Controller#action transaction times. Navigating those timings is much better than with New Relic, as you get a clear full breakdown of everything that happens for a given request.

Skylight offers better Rails performance insights, so why use New Relic? Because it does frontend monitoring, while Skylight doesn't. Now that we have a separate frontend app though, our frontend engineers are looking into more specialized frontend monitoring solutions.

Finally, if one of our apps go down, Pingdom alerts us on Slack and texts some of us.

See more
Nikola Yovchev
Head of Engineering at Relay42 · | 2 upvotes · 111.2K views

#Datadog #Relay42 #Monitoring

With Datadog unveiling their Synthetics product (https://www.datadoghq.com/blog/introducing-synthetic-monitoring/), we at Relay42 are considering moving out of Pingdom.

The rationale is simple:

  • 90% of our monitoring is on Datadog, apart from the external requests. It'd be nice to identify regional issues in one place, so this is great in our monitoring consolidation efforts.

  • The lack of a non-community Terraform provider for Pingdom

We have yet to get in the beta and test it out but we feel very excited about this announcement.

See more
Apigee logo

Apigee

176
482
26
Intelligent and complete API platform
176
482
+ 1
26
PROS OF APIGEE
  • 10
    Highly scalable and secure API Management Platform
  • 5
    Quick jumpstart
  • 5
    Good documentation
  • 3
    Fast and adjustable caching
  • 3
    Easy to use
CONS OF APIGEE
  • 6
    Expensive

related Apigee posts

A Luthra
VP Software Engrg at Reliant · | 2 upvotes · 297.7K views
Shared insights
on
Apigee
Amazon API Gateway

Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

See more
Assertible logo

Assertible

7
12
0
Automated QA tools to test and monitor your web services across deployments and environments
7
12
+ 1
0
PROS OF ASSERTIBLE
    Be the first to leave a pro
    CONS OF ASSERTIBLE
      Be the first to leave a con

      related Assertible posts

      Kong logo

      Kong

      429
      1K
      127
      Open Source Microservice & API Management Layer
      429
      1K
      + 1
      127
      PROS OF KONG
      • 36
        Easy to maintain
      • 30
        Easy to install
      • 22
        Flexible
      • 20
        Great performance
      • 5
        Api blueprint
      • 4
        Custom Plugins
      • 3
        Kubernetes-native
      • 2
        Agnostic
      • 1
        12312312
      • 1
        123123
      • 1
        1
      • 1
        123
      • 1
        Documentation is clear
      • 0
        12
      CONS OF KONG
        Be the first to leave a con

        related Kong posts

        Al Tsang
        Problem/Challenge

        We needed a lightweight and completely customizable #microservices #gateway to be able to generate #JWT and introspect #OAuth2 tokens as well. The #gateway was going to front all #APIs for our single page web app as well as externalized #APIs for our partners.

        Contenders

        We looked at Tyk Cloud and Kong. Kong's plugins are all Lua based and its core is NGINX and OpenResty. Although it's open source, it's not the greatest platform to be able to customize. On top of that enterprise features are paid and expensive. Tyk is Go and the nomenclature used within Tyk like "sessions" was bizarre, and again enterprise features were paid.

        Decision

        We ultimately decided to roll our own using ExpressJS into Express Gateway because the use case for using ExpressJS as an #API #gateway was tried and true, in fact - all the enterprise features that the other two charge for #OAuth2 introspection etc were freely available within ExpressJS middleware.

        Outcome

        We opened source Express Gateway with a core set of plugins and the community started writing their own and could quickly do so by rolling lots of ExpressJS middleware into Express Gateway

        See more
        Anas MOKDAD
        Shared insights
        on
        Kong
        Istio

        As for the new support of service mesh pattern by Kong, I wonder how does it compare to Istio?

        See more
        Amazon API Gateway logo

        Amazon API Gateway

        1.1K
        802
        39
        Create, publish, maintain, monitor, and secure APIs at any scale
        1.1K
        802
        + 1
        39
        PROS OF AMAZON API GATEWAY
        • 35
          AWS Integration
        • 4
          Websockets
        CONS OF AMAZON API GATEWAY
        • 1
          Less expensive
        • 1
          No websocket broadcast

        related Amazon API Gateway posts

        A Luthra
        VP Software Engrg at Reliant · | 2 upvotes · 297.7K views
        Shared insights
        on
        Apigee
        Amazon API Gateway

        Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

        See more