Two of the best (in my opinion) features in [Konnect](https://konghq.com/kong-konnect)Konnect are the ServiceHub and Dev Portal. However, they're also two of the most misunderstood. Aren't they the same thing? Why would you need a ServiceHub vs. Dev Portal?
Well, I'm glad you asked! The really quick version is that ServiceHub is like your warehouse, where all your products are stored. It's a comprehensive collection of everything that you have. Your Dev Portal is more like your storefront. It contains only the things you want to promote, and you present them in a more user-friendly way.
That's the 20-second explanation. Continue reading, and we'll explore the differences between the two and dive deeper into the functionality of each.
Let's start with the ServiceHub, as it's the first thing you'll see when you register for Konnect. This is where you'll see all of your running services and have the ability to configure your service versions, routes and plugins.
My sample project for Konnect is Gorilla Bank, a fake banking institute. This means I have services related to account management, money collection and foreign exchange rates.
ServiceHub is the system of record for all available services at Gorilla Bank. It allows developers to discover and consume existing services, speed up development and reduce duplication.
At Gorilla Bank, we have some legacy systems that don't use Kong, but I still want them to be discoverable for developers. By creating a ServiceHub entry and an associated version, we can provide metadata and documentation for the service without linking it to a [Kong Gateway](https://konghq.com/kong)Kong Gateway implementation.
If you use Kong Gateway for any of your services, usage within that service will show up in the Runtime Manager, which lives within ServiceHub. That way, you can keep track of usage at a glance, including any errors.
Having a single source of truth that shows any available APIs across a business is key to building alignment across your API strategy. A team rarely builds their own service because they want to—more often than not, they do so because they don't know that a service already exists. ServiceHub helps your teams understand what's available, how to use it and how each service is performing.
Let's move on to the Dev Portal. Whilst the ServiceHub is for your internal development teams, the Dev Portal targets both internal and external consumers. You can control which APIs people can see and provide an easy-to-use console that allows consumers to try out the API directly in the docs.
By default, Kong secures your Dev Portal behind a login. This is useful if your APIs aren't ready for the general public to use. Once consumers register, their requests will show up in Konnect for approval.
Once you approve the registration request, the consumers will be able to log in to the developer portal and see any published services. At Gorilla Bank, we've published the Account Inquiry, Collect Money and FX Rates APIs for use by the public. The other APIs, such as Account Creation, are still private.
If your APIs are usable by the general public, you may want to explore the [portal settings](https://cloud.konghq.com/settings/portal-settings)portal settings section of Konnect. You can make the portal entirely public or enable automatic approval of any registrations if you need to capture email addresses but want the content to be available to anyone without the added approval process.
No matter how well you design an API, some context is usually required when working with it. To help with this, Konnect allows you to upload a *Service Document* within ServiceHub, which Kong will show within the Dev Portal.
The Service Document is a markdown file containing any information you need to share with consumers. It can also contain anything that is valid markdown, including images.
In addition to the service document, the Dev Portal also allows you to upload an OpenAPI specification. The spec shows the available endpoints for the API, plus any available parameters and an example response.
You may have noticed the *Try it Out* section on the right. That section allows your customers to try out your API directly in the documentation. It provides the executed request in various languages (powered by our open-source [httpsnippet](https://github.com/Kong/httpsnippet)httpsnippet project).
If you have different versions of an API available, switching between them is as easy as using the version dropdown at the top of the page. Likewise, suppose you've got many environments — in that case, you can specify multiple entries in the servers block in your OpenAPI specification. The developer portal will let your customers choose which environment to test against.
Finally, the *View Raw* button enables your consumers to download your specification and use it for anything they need. The Dev Portal uses it for documentation, but your customers could use it for mocking, code generation or a whole lot more.
Thanks for sticking with me this far! We've taken a tour of Konnect's ServiceHub and Dev Portal. Hopefully, you're clearer on how they're different from each other and how each of them can enhance your API experience.
We're just getting started with Konnect, and I can't wait to share some advanced workflows using the Developer Center API with you, but that will have to wait for a future post.
[Start a free trial](https://cloud.konghq.com/register)Start a free trial, or [contact us](https://support.konghq.com/support/s)contact us if you have any questions as you're getting set up.
Now that you have a better understanding of Kong Konnect's ServiceHub and Dev Portal, you may find these other tutorials helpful:
Today, we’re excited to release the Kong Konnect EKS Marketplace add-on as a means to deploy your Kong Gateway dataplanes in AWS. The add-ons are a step forward in providing fully managed Kubernetes clusters. It is here to simplify the post-procurem
[](https://konghq.com/blog/engineering/kong-konnect-eks-marketplace-add-on)
A developer portal is a storefront to your APIs (the products) that internal and external developers are trying to consume. The Kong Developer Portal provides a single source of truth for all developers to locate, access and consume services. With
[](https://konghq.com/blog/engineering/customize-kong-developer-portal)
Want to learn more about the nuts and bolts of APIOps? Download our eBook, Unlocking the Full Potential of your APIs with APIOps , and learn about the stages of APIOps, get an understanding of the technical assets required, and explore the tooling
[](https://konghq.com/blog/engineering/automating-developer-pipeline-apiops)
In this Kong Gateway tutorial, you'll learn how to: Download and install Kong Add a service Add a route Add the key authentication plugin Add the proxy cache plugin Test plugins using Insomnia Keep in mind that these instructions are a starting poi
[](https://konghq.com/blog/engineering/kong-gateway-tutorial)
Traditional APIs are, in a word, predictable. You know what you're getting: Compute costs that don't surprise you Traffic patterns that behave themselves Clean, well-defined request and response cycles AI APIs, especially anything that runs on LLMs
[](https://konghq.com/blog/engineering/monetize-ai-apis)
Architecture Overview A multicloud DCGW architecture typically contains three main layers. 1\. Konnect Control Plane The SaaS control plane manages configuration, plugins, and policies. All gateways connect securely to this layer. 2\. Dedicated C
[](https://konghq.com/blog/engineering/dedicated-cloud-gateways-managed-redis-multi-cloud)
Managed Redis cache is a turnkey "Shared State" add-on for Kong Dedicated Cloud Gateways. It is designed to combine the performance of an in-memory data store with the simplicity of a SaaS product. When you spin up a Dedicated Cloud Gateway in Kong
[](https://konghq.com/blog/product-releases/multicloud-cloud-gateways-managed-redis-cache)