We just GA’d the new Kong Konnect Developer Portal as part of our broader API discovery initiative, and it represents a fundamental rethink of what a developer portal should be. Built from the ground up on a modern tech stack, it delivers both the simplicity teams need to get started fast and the deep customization capabilities required for professional, on-brand experiences.
TL;DR: The new Kong Developer Portal delivers professional, branded API experiences in minutes with our starter template, then lets you customize every detail through our intuitive MDC framework and live portal editor. Modern spec rendering, self-service workflows, and enterprise-grade access controls mean developers actually want to use your portal. No more choosing between easy and powerful: Kong Konnect's new Developer Portal delivers both.
The developer portal landscape forces an impossible choice.
On one side, you have modern documentation platforms that developers love with clean interfaces, great authoring experiences, and seamless workflows. But they're disconnected from your API runtime, lacking self-service access capabilities, usage analytics, and enterprise controls. They're beautiful documentation sites, not true developer portals.
On the other side, traditional API management platforms bundle portals that provide deep runtime integration and enterprise features. The catch? Their portals come in two equally frustrating flavors: bare-bones templates with minimal customization, or full-featured offerings built on legacy content management systems (CMS) like Drupal. The latter were cutting-edge a decade ago but now feel clunky and dated, bringing their own baggage like complex theming systems, plugin dependencies, and constant security patching.
Option 1: Beautiful but disconnected – Modern documentation platforms that developers actually enjoy using. Clean interfaces, markdown-based authoring, instant previews. But they're islands. No connection to your API runtime means no self-service key management, no real usage analytics, and no enterprise access controls.
Option 2: Integrated but compromised – Traditional APIM portals promise runtime integration, but force yet another choice:
The available options have left teams frustrated.
Platform engineers, typically backend-focused without dedicated frontend resources, want to ship a brand-compliant portal quickly without working with raw HTML/CSS that inevitably becomes a maintenance nightmare when frontend engineers arrive to polish things up.
Marketing wants pixel-perfect brand compliance.
Developers just want to find and use APIs without friction.
The new Kong Developer Portal breaks this pattern. As we'll show in our walkthrough, you can go from zero to a professionally branded portal in minutes, then progressively enhance it with deep customizations as needed. No more compromises: beautiful, integrated, and customizable — without needing a team of frontend developers.
We chose to build on the latest versions of Nuxt, Vue.js, and TypeScript and contributed back to these open-source ecosystems along the way. This isn't just about using the latest frameworks; it's about delivering real benefits:
At the heart of our customization system are Markdown Components (MDC). MDC is a Vue/Nuxt-based framework that makes creating rich, interactive content as simple as writing Markdown. But this isn't your standard Markdown; it's Markdown with superpowers.
Think of MDC as bringing component-based development to content creation. Portal pages are made up of multiple, pre-built MDC building blocks that are as easy to parse as any Markdown document. Here's how it breaks down:
::component-name
--- YAML frontmatter ---
#slot-name
Let's see this in action with a real example:
::page-section
---
full-width: true
background-color: "#FFFEF8"
---
::page-hero
---
title-font-size: "clamp(36px, 5vw, 64px)"
title-line-height: "clamp(42px, 5vw, 72px)"
title-font-weight: "700"
title-tag: "h1"
description-font-size: "clamp(16px, 3vw, 24px)"
description-line-height: "clamp(24px, 3vw, 32px)"
description-font-weight: "400"
text-align: "center"
image:
position: "bottom"
src: "https://imgur.com/C6A0H4v.png"
---
#title
Kong API Dev Portal
#description
Code. Collaborate. Innovate. Your Gateway to Development Excellence.
#actions
::button
---
size: "large"
to: "/getting-started"
---
Get started
::
::
::
Here we're using two components:
::page-section - A container that spans the full width with a light background::page-hero - A hero section nested inside, with customized typography and an imageThe YAML frontmatter between the --- markers is where you can configure fonts, sizes, colors, and layout without touching CSS. The #title, #description, and #actions slots are where your actual content goes.
The result? A professional hero section with responsive typography, properly positioned image, and interactive button, all from readable Markdown. The image below shows this exact code in our Portal Editor with live preview.
While MDC provides a rich set of pre-built components, the real power comes with Snippets: your own reusable, parameterized components that work across your entire portal.
Think of Snippets as your component library. Create once, use everywhere. Need a custom call-to-action that appears on multiple pages? Build it as a Snippet. Want consistent API authentication instructions across your docs? Snippet. Complex pricing tables that need regular updates? You guessed it, Snippet.
Here's what makes Snippets powerful:
Dynamic Parameters: Build flexible Snippets with defaults that can be adapted to match the context. Define default values in the Snippet, then override them wherever it's used.
Let's say you create an api-quickstart Snippet with defaults:
# In the Snippet (with front matter defaults)
---
apiName: "Our API"
authMethod: "API Key"
docsLink: "/authentication"
---
Get started with {{ $doc.snippet.apiName }} using {{ $doc.snippet.authMethod }}.
See our [authentication guide]({{ $doc.snippet.docsLink }}) for details.
Then customize it per API:
# In your Payments API page
::snippet
---
name: api-quickstart
data:
apiName: "Payments API"
authMethod: "OAuth 2.0"
docsLink: "/payments/oauth"
---
::
One Snippet, infinite variations. Update the template once, and every API's quickstart guide updates automatically while keeping their specific details intact.
Publishing and privacy Controls: Snippets support both visibility states (public/private) and publishing states (published/unpublished), giving you granular control over what developers see and when.
Private snippets only appear for authenticated users, making it perfect for things like beta features, internal documentation, or partner-specific content.
The publish/unpublish toggle enables proactive content management. Pre-stage a maintenance banner across all pages but keep it unpublished. When downtime hits, one click publishes the alert portal-wide. No scrambling to update individual pages during an incident.
Nested composition: Snippets can include other Snippets and any MDC components. Build complex layouts by composing smaller, focused Snippets together.
The beauty is maintenance at scale. Update a Snippet once, and every page using it updates automatically. No more hunting through dozens of pages to change that support email or update your onboarding flow. This is how you build a portal that scales with your API program.
Gone are the days of edit-save-refresh-evaluate-repeat. Our Portal Editor provides a side-by-side experience where you write MDC on the left and see live updates on the right. It's like having a design tool and CMS rolled into one.
The editor understands MDC syntax, providing autocomplete for components and their properties. Made a mistake? The preview shows exactly what went wrong. Want to test mobile views? Switch viewport sizes instantly.
For teams with strict design requirements, you have the option to implement custom CSS. The editor provides full access to pre-built design tokens, exposed via CSS Custom Properties, letting you fine-tune every pixel while maintaining the benefits of the component system.
We need to talk about API documentation. The standard Swagger UI that most portals use? It looks like it was designed in 2010 because, well, it was. API documentation doesn't have to be ugly or hard to navigate.
That's why we built our own spec renderer from scratch. It supports both OpenAPI 3.x and AsyncAPI specs (perfect for our Event Gateway), renders beautifully on any device, and includes features developers actually want:
The best part? We're open-sourcing it. The same renderer powers our Dev Portal, Service Catalog, and our own API docs. Soon, any developer will be able to use it in their projects.
A great portal is more than just good looks and documentation. The new Developer Portal delivers on the complete developer journey.
Developers can register, create applications, and obtain API keys, with or without manual approval, depending on your portal settings.
As your API catalog grows, developers need tools to quickly find what they’re looking for:
region: [us-east, eu-west]) and use them to pre-filter API lists or provide dynamic filter sidebars
Enterprise teams need granular control over who sees what:
Every touchpoint matters. Customize the entire email experience to match your portal’s branding:
The new portal provides analytics for both the portal owners and developers using the portal. This data provides actionable intelligence for improving your API program:
In the above walkthrough of Kong Konnect's new dev portal, we'll cover:
This is just the beginning. The new Developer Portal is now officially GA, but we’re not done here. We have an exciting and jam-packed roadmap, and we're actively building based on user feedback.
But honestly? What's available today already represents a massive leap forward for developer portals that no longer makes you choose between simple and powerful. Whether you need a portal live in the next hour or want to craft a completely custom experience, the combination of MDC components, live portal editing, and progressive customization has you covered.
Ready to see what a modern developer portal looks like? Schedule a demo with our in-house experts to learn how the new Kong Developer Portal can support your API program.
As of September 2025, Kong Gateway Enterprise 3.8 will enter its End Of Life (EOL) phase and will no longer be fully supported by Kong. Following this, Kong Gateway Enterprise 3.8 will enter a 12-month sunset support period, focused on helping cus
We're very excited to announce Kong Mesh 2.12 to the world! Kong Mesh 2.12 delivers two very important features: SPIFFE / SPIRE support, which provides enterprise-class workload identity and trust models for your mesh, as well as a consistent Kuma R
Meet Emily. She’s an API product manager at ACME, Inc., an ecommerce company that runs on dozens of APIs. One morning, her team lead asks a simple question: “Who’s our top API consumer, and which of your APIs are causing the most issues right now?”
Today, we’re announcing that Kong has acquired OpenMeter , the open source and SaaS leader for real-time usage metering and billing. OpenMeter’s capabilities will be integrated into Kong Konnect, enabling usage-based pricing, entitlements, and invo
It’s been almost a year since we released our Konnect Terraform provider . In that time we’ve seen over 300,000 installs, have 1.7 times as many resources available, and have expanded the provider to include data sources to enable federated managem
We're happy to announce the 3.5 release of Kong Ingress Controller (KIC). This release includes the graduation of combined services to General Availability, support for connection draining, as well as the start of deprecating support for some Ingre
Update Includes Data Orchestration, CyberArk Support, Solace Integration, and Kafka Schema Validation We’re excited to bring you Kong Gateway Enterprise 3.11 with compelling new features to make your APIs and event streams even more powerful, includ