Name: Zuplo
Rating: 4.71 (7 reviews)

Serverless API Management, designed for developers. Launching today, Zuplo’s Free plan (beta) helps developers ship a public API in record time by taking care of the boring but necessary things, like authentication and rate limiting, that every public API needs.

Building an API is straightforward, but monetizing it effectively requires more—excellent documentation, authentication, and security. Zuplo provides all these and today introduces a way to monetize your API with pricing pages, API keys and usage billing.

Hi everyone, I’m Josh Twist, co-founder and CEO of Zuplo. I’ve dedicated my career to building developer tools, including founding the Azure API Management team at Microsoft, which Zuplo competes with - fun! My co-founder, Nate Totten, has also dedicated his career to building developer tools, notably being an early member of the Auth0 team. Today, we’re announcing the release of native API monetization in Zuplo. Zuplo is a fully managed API Management platform designed for developers. If you haven’t used API Management before, it can handle all the stressful, boring things needed to ship an API securely. You get non-trivial but critical features like rate limiting, Authentication, developer documentation, analytics, and more - out of the box in minutes. So far, we’ve been working on bringing together the main ingredients for any successful API program: 🚀 Authentication that is easy to use and secure: Authentication is the first thing any developer using your API stumbles with. We’ve worked hard to make this process have the least amount of friction and yet still be incredibly powerful and extensible to fit your needs. 📖 Beautiful developer portals (a.k.a API docs): you need a Stripe-like developer portal where your customers can access your API documentation and their API keys, have a test console to try things out, and even see their analytics. 🔒 Powerful security (a.k.a Rate-limiting): it’s not the boogeyman that will take you down; it’s a lazy for-loop in your customers’ code. Every public API needs this stuff, but you shouldn’t have to build it yourself. Our company’s primary value is building the best developer experience that helps achieve a robust, ready-to-use API, which is how we believe Zuplo can become a success. Think what Vercel did for the frontend world, but for APIs, that means code and text files for everything, unlimited environments by opening a Github PR, and deploying your API gateway to the CDN edge, making it incredibly fast from day 1. Once we’ve achieved the basic building blocks, we’re now adding the possibility to monetize APIs directly in Zuplo, offering the following: - Generated pricing pages in your API documentation - Self-serve API keys once a customer subscribes to your API - Self-serve analytics so your customers can understand how they’re using your API - API key leak detection in case a customer has committed a key by mistake to Github - Unlimited customizability you can make a request-based API plan for your API, or dynamically count the usage based on the response you send to a user. ∞ Check out our example portal with the Rick and Morty API: https://rickandmorty.zuplo.io/

@molmorg Wow this looks awesome - I love how it's specialized to charging for API usage (as compared to a full stack product). The example portal is helpful in understanding how it works quickly. Congrats on the launch!

@vit_aver We are planning many new features right now - please let us know what you are interested in so we can prioritize!

Congrats on the launch guys, this looks really neat! The example docs look really beautiful and clear. Looks like a no-brainer for usage-based API businesses. Does this also help for a regular SaaS where the API is just the back-end for an application (with an open API for integrations)?

@jopie Thanks for the kind words Joep! Yes - a regular SaaS backend with an OpenAPI is definitely the main use case here. You'd import your OpenAPI to Zuplo and enable auth & monetization on your routes: https://zuplo.com/docs/articles/...