Alternatives to Gravitee.io logo

Alternatives to Gravitee.io

Kong, Keycloak, Postman, Amazon API Gateway, and Insomnia REST Client are the most popular alternatives and competitors to Gravitee.io.
17
69
+ 1
1

What is Gravitee.io and what are its top alternatives?

It is a flexible, lightweight and blazing-fast open source API Platform that helps your organization control finely who, when and how users access your APIs.
Gravitee.io is a tool in the API Tools category of a tech stack.

Top Alternatives to Gravitee.io

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

  • Keycloak

    Keycloak

    It is an Open Source Identity and Access Management For Modern Applications and Services. It adds authentication to applications and secure services with minimum fuss. No need to deal with storing users or authenticating users. It's all available out of the box. ...

  • Postman

    Postman

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

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

  • Insomnia REST Client

    Insomnia REST Client

    Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux. ...

  • OpenAPI

    OpenAPI

    It is a publicly available application programming interface that provides developers with programmatic access to a proprietary software application or web service. ...

  • Paw

    Paw

    Paw is a full-featured and beautifully designed Mac app that makes interaction with REST services delightful. Either you are an API maker or consumer, Paw helps you build HTTP requests, inspect the server's response and even generate client code. ...

  • OpenAPI Specification

    OpenAPI Specification

    It defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. ...

Gravitee.io alternatives & related posts

Kong logo

Kong

428
1K
127
Open Source Microservice & API Management Layer
428
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
    Keycloak logo

    Keycloak

    367
    702
    61
    An open source identity and access management solution
    367
    702
    + 1
    61
    PROS OF KEYCLOAK
    • 23
      It's a open source solution
    • 16
      Supports multiple identity provider
    • 11
      OpenID and SAML support
    • 6
      Easy customisation
    • 5
      JSON web token
    CONS OF KEYCLOAK
    • 1
      Lack of Code examples for client side
    • 1
      Poor client side documentation
    • 0
      Okta

    related Keycloak posts

    Joshua Dean KĂźpper
    CEO at Scrayos UG (haftungsbeschränkt) ¡ | 7 upvotes ¡ 250.3K views

    As the access to our global REST-API "Charon" is bound to OAuth2, we use Keycloak inside Quarkus to authenticate and authorize users of our API. It is not possible to perform any un-authenticated requests against this API, so we wanted to make really sure that the authentication/authorization component is absolutely reliable and tested. We found those attributes within Keycloak, so we used it.

    See more
    Shared insights
    on
    FreeRADIUS
    Keycloak

    Hello all, I wanted to see if I could get some advice on how to integrate Keycloak with FreeRADIUS . I wanted our users to be able to use their Keycloak credentials to authenticate to our wifi through FreeRadius. I don't see much online for how the two can work together. I already have Keycloak setup and FreeRadius up and running. Now I need the two to talk to each other. Any help would be greatly appreciated.

    See more
    Postman logo

    Postman

    55.9K
    44.3K
    1.7K
    Only complete API development environment
    55.9K
    44.3K
    + 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
    Amazon API Gateway logo

    Amazon API Gateway

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

    related Amazon API Gateway posts

    A Luthra
    VP Software Engrg at Reliant ¡ | 2 upvotes ¡ 288.4K 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
    Insomnia REST Client logo

    Insomnia REST Client

    509
    420
    34
    The most intuitive cross-platform REST API Client 😴
    509
    420
    + 1
    34
    PROS OF INSOMNIA REST CLIENT
    • 14
      Easy to work with
    • 9
      Great user interface
    • 5
      Works with GraphQL
    • 2
      Preserves request templates
    • 2
      Opensource
    • 2
      Cross platform, available for Mac, Windows, and Linux
    • 0
      Does not have history feature
    • 0
      Vim and Emacs key map
    CONS OF INSOMNIA REST CLIENT
    • 1
      Do not have team sharing options
    • 1
      Do not store credentials in HTTP

    related Insomnia REST Client posts

    Jason Barry
    Cofounder at FeaturePeek ¡ | 4 upvotes ¡ 1.8M views

    We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

    • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
    • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
    • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

    Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

    See more
    OpenAPI logo

    OpenAPI

    255
    224
    0
    Allows the owner of a network-accessible service to give universal access
    255
    224
    + 1
    0
    PROS OF OPENAPI
      Be the first to leave a pro
      CONS OF OPENAPI
        Be the first to leave a con

        related OpenAPI posts

        Joshua Dean KĂźpper
        CEO at Scrayos UG (haftungsbeschränkt) ¡ | 4 upvotes ¡ 184.8K views

        We use Swagger Inspector in conjunction with our universal REST-API "Charon". Swagger Inspector makes testing edge-cases hassle-free and lets testing look easy. Swagger Inspector was also a great help to explore the Mojang-API, that we are dependent on, because it is the central repository for minecraft-account-data.

        We previously used Postman but decided to switch over to Swagger Inspector because it also integrated seamlessly into Swagger UI, which we use for displaying our OpenAPI specification of said REST-API.

        See more
        Paw logo

        Paw

        195
        236
        165
        The ultimate REST client for Mac
        195
        236
        + 1
        165
        PROS OF PAW
        • 46
          Great interface
        • 38
          Easy to use
        • 25
          More stable and performant than the others
        • 16
          Saves endpoints list for testing
        • 13
          Supports environment variables
        • 12
          Integrations
        • 9
          Multi-Dimension Environment Settings
        • 4
          Paste curl commands into Paw
        • 2
          Creates code for any language or framework
        CONS OF PAW
        • 3
          It's not free
        • 2
          MacOS Only

        related Paw posts

        Jason Barry
        Cofounder at FeaturePeek ¡ | 4 upvotes ¡ 1.8M views

        We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

        • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
        • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
        • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

        Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

        See more
        OpenAPI Specification logo

        OpenAPI Specification

        180
        105
        6
        An API description format for REST APIs
        180
        105
        + 1
        6
        PROS OF OPENAPI SPECIFICATION
        • 3
          API Specification
        • 3
          API Documentation
        CONS OF OPENAPI SPECIFICATION
          Be the first to leave a con

          related OpenAPI Specification posts