How to Build a Developer Portal for Apigee

Centauri Launchpad is a developer portal platform for Apigee. It allows organizations to create developer portals connected to their Apigee environments and publish APIs, documentation, and onboarding workflows for developers. It deploys in 48 hours and integrates natively with Apigee X and Apigee Edge.

Why Apigee Needs a Developer Portal

Apigee is an API gateway. It handles API proxies, security policies, rate limiting, traffic management, and analytics. What it does not include is a full-featured developer portal where external or internal developers can discover APIs, read documentation, request API keys, and test endpoints.

Google offers the Apigee Integrated Portal as a built-in option. It provides basic functionality: a page listing your API products, simple documentation rendering, and a developer registration flow. However, it has significant limitations that make it unsuitable for most production use cases.

•No white-label branding. The portal carries Apigee styling that cannot be fully customized.
•Limited layout and page customization. You cannot build custom workflows or pages.
•No interactive API testing (try-it-now). Developers must use external tools like Postman.
•No role-based access control for portal content. You cannot show different APIs to different audiences.
•No SSO integration beyond Google Identity. Enterprise IdP support is missing.

For teams exposing APIs to external partners, internal developers, or paying customers, a dedicated developer portal is a requirement. The question is how to build one.

Options for Building an Apigee Developer Portal

There are four main approaches. Each has different tradeoffs in cost, flexibility, time-to-launch, and maintenance burden.

1. Apigee Integrated Portal

Built into the Apigee console. Free with your Apigee subscription. Provides basic API catalog, developer registration, and static documentation pages.

•Cost: Free (included with Apigee)
•Setup time: Hours
•Limitation: No white-labeling, no interactive docs, minimal customization
•Best for: Internal prototyping or teams with very basic needs

2. Drupal Developer Portal

Google's original recommended approach. Uses the Apigee Drupal module (apigee_edge) to connect Drupal CMS to Apigee. Requires a Drupal hosting environment and PHP expertise.

•Cost: $50K-150K initial build + $30K-80K/year maintenance
•Setup time: 2-4 months
•Limitation: Drupal expertise is increasingly rare; most teams are migrating away
•Best for: Teams that already have Drupal infrastructure and expertise

3. Custom React/Next.js Portal

Build a portal from scratch using modern frontend frameworks. You call the Apigee Management API directly to sync API products, developers, and credentials.

•Cost: $196K+ initial build + $120K-200K/year for engineering team
•Setup time: 6-12 months
•Limitation: You own every line of code, every Apigee API integration, every upgrade
•Best for: Teams with unique requirements that no existing platform can meet

4. Centauri Launchpad

A managed developer portal platform built specifically for Apigee X and Apigee Edge. Handles Apigee integration, API documentation rendering, developer onboarding, and credential management out of the box.

•Cost: $480-3,000/month depending on tier
•Setup time: 48 hours
•Includes: Interactive docs (Scalar), RBAC, SSO, custom branding, Apigee sync
•Best for: Teams that want a production-ready portal without building or maintaining it

What a Good Apigee Portal Should Include

Regardless of which approach you choose, your Apigee developer portal needs these capabilities to be useful to developers.

Feature Checklist

•API catalog synced from Apigee. API products should appear automatically when published in Apigee, not manually re-entered.
•Interactive API documentation. Developers should be able to make test calls directly from the docs, not copy-paste into Postman.
•Developer self-service registration. New developers should sign up, browse APIs, and get API keys without manual approval for standard tiers.
•API key and credential management. Developers create and rotate their own keys. The portal writes credentials back to Apigee via the Management API.
•OpenAPI spec rendering. Upload an OpenAPI 3.0 or Swagger 2.0 spec and get complete, navigable reference documentation.
•Sandbox and production environment support. Developers should be able to test against a sandbox before requesting production access.
•Custom branding. The portal should look like your company, not like a third-party tool.
•Role-based access control (RBAC). Show different APIs and documentation to different developer groups. Internal teams see internal APIs; partners see partner APIs.
•Analytics. Track which APIs are being viewed, which developers are active, and where onboarding breaks down.

Want to see a live Apigee portal?

Book a 15-minute demo and see Launchpad connected to a real Apigee environment.

Build vs. Buy Decision

This is the core question. The answer depends on your team size, timeline, and how unique your portal requirements are.

Build (Custom Portal)

•Timeline: 6-12 months to production
•Initial cost: $196K+ (3-4 engineers for 6 months)
•Ongoing cost: $120K-200K/year for maintenance and Apigee API updates
•Team required: Frontend engineers, backend engineers, DevOps
•Risk: Apigee API changes can break your integration. You maintain everything.

Buy (Managed Platform)

•Timeline: 48 hours to production
•Initial cost: $0 (no build phase)
•Ongoing cost: $480-3,000/month ($5,760-36,000/year)
•Team required: None. Portal is managed by the vendor.
•Flexibility: Supports custom branding, SSO, RBAC, and on-premises deployment for compliance needs.

The math is straightforward. A custom build costs $196K+ upfront and $120K+/year to maintain. A managed platform like Centauri Launchpad costs $5,760-36,000/year total with zero engineering overhead. For most teams, building a custom portal only makes sense when you have requirements that no existing platform can meet.

Getting Started

Whether you build or buy, the evaluation process is the same. Follow these steps to scope your Apigee developer portal project.

1.
Identify which APIs you need to expose. List every API product in Apigee that external developers or internal teams need access to. Categorize them by audience (public, partner, internal).
2.
Decide build vs. buy. If you have fewer than 50 APIs and no highly custom workflow requirements, a managed platform will save you six months and six figures.
3.
Set up an Apigee service account. Your portal needs a GCP service account with permissions to read API products, manage developer apps, and sync OpenAPI specs from Apigee. This is required regardless of which approach you choose.
4.
Deploy the portal. For a managed platform, this means connecting your Apigee org and configuring branding. For a custom build, this means standing up infrastructure, implementing Apigee API integration, and building the frontend.
5.
Import your API specs. Upload OpenAPI specs for each API product. Good specs produce good documentation automatically. If your specs are incomplete, fix them first.
6.
Configure branding and access controls. Apply your company's visual identity. Set up RBAC so different developer groups see the right APIs. Configure SSO if you need it.