Today we’re thrilled to announce a brand new product area for Kong – Kong Studio, an integrated design and test environment for [Kong Enterprise](https://konghq.com/products/kong-enterprise)Kong Enterprise customers. We are excited to make the leap in extending our service control platform to include pre-production use cases focused on improving the way that customers build and test their [microservices and APIs](https://konghq.com/solutions/gateway)microservices and APIs. With Kong Studio, customers can easily adopt a modern, spec-driven approach to development while also automating many of the tedious aspects of maintaining API documentation in increasingly complex service environments.
As organizations worldwide increasingly [adopt microservices](https://konghq.com/blog/learning-center/what-are-microservices)adopt microservices, they face new challenges in standardizing documentation, managing deployment risks and maintaining efficiency across their development teams. We built Kong Studio builds on top of the popular open source [Insomnia API testing platform](http://www.insomnia.rest)Insomnia API testing platform (now a part of the Kong family) to provide a design and test suite focused on solving these challenges. With its native integration to Kong Enterprise, Kong Studio allows users to seamlessly edit, test and publish REST and GraphQL services directly onto the Kong Enterprise runtime and [Dev Portal](https://konghq.com/products/kong-enterprise/dev-portal)Dev Portal.
Some of the benefits Kong Enterprise customers will see by adopting spec-driven development with Kong Studio include:
The journey to spec-driven development starts with authoring specifications. Kong Studio streamlines development by providing the ability to generate code snippets in numerous languages, automate testing via OpenAPI linting, directly sync to Git, and enable inspection of responses beyond just JSON and XML. Integrating these into a team's development workflow offers enterprises the opportunity to increase efficiency regardless of their existing environments.
The next step in spec-driven development is updating your services in production. Native integration to Kong Enterprise allows you to automate this as well and push updates to Kong directly from Studio. Before doing so you can also minimize deployment risk with tests that reflect your production environments. Chain requests to understand dependencies throughout the end user's entire journey.
Finally, spec-driven development also improves your ongoing compliance with your organization’s policies. Kong Studio lets you test service interactions with popular authentication methods, including OAuth. You can also encrypt end-to-end to ensure appropriate data privacy and security within Kong Studio.
Kong Studio is available as a standalone add-on to Kong Enterprise. To learn more about how Studio can help your developers build better services, check out our [Data Sheet](https://konghq.com/wp-content/uploads/2019/09/Studio.pdf)Data Sheet.
The widespread adoption of Kafka and event streaming platforms is evident across several enterprises, where they serve as the backbone of critical operations, ranging from financial transactions to AI inference pipelines. However, in the domains of
[](https://konghq.com/blog/product-releases/kong-event-gateway-1-1)
Agents are ultimately decision makers. They make those decisions by combining intelligence with context, ultimately meaning they are only ever as useful as the context they can access. An agent that can't check inventory levels, look up customer his
[](https://konghq.com/blog/product-releases/introducing-kong-context-mesh)
Microservices have an entirely new set of problems due to their distributed service-oriented architecture. As a result, microservice design patterns have surfaced. This post will consider the specific design patterns that can help us build reliable,
[](https://konghq.com/blog/enterprise/microservice-design-patterns)
This is the second of two blogs examining considerations for transitioning to a microservices-based architecture. For more information, check out our e-book Blowing Up the Monolith: Adopting a Microservices-Based Architecture . In our previous blog
[](https://konghq.com/blog/engineering/transition-to-microservices-what-now)
The Stakes Keep Rising The security implications are severe. OWASP's 2025 Top 10 for LLM Applications ranks prompt injection as the number one critical vulnerability. Attackers manipulate LLM inputs to override instructions, extract sensitive data,
[](https://konghq.com/blog/engineering/5-best-practices-securing-microservices-scale)
The Anatomy of Architectural Complexity Modern architectures now juggle three distinct traffic patterns. Each brings unique demands. Traditional approaches treat them separately. This separation creates unnecessary complexity. North-South API Traf
[](https://konghq.com/blog/enterprise/microservices-to-ai-traffic-kong-as-the-unified-control-plane)
Running Kong in front of your Solace Broker adds real benefits: Authentication & Access Control – protect your broker from unauthorized publishers. Validation & Transformation – enforce schemas, sanitize data, and map REST calls into event topics.
[](https://konghq.com/blog/engineering/smarter-event-driven-apis-kong-solace)