Zuplo
Developer Portal

A developer portal that ships every time you do

Auto-generated from your OpenAPI, interactive API explorer, self-serve API keys, monetization-aware pricing, custom React pages, your custom domain — built into every Zuplo project and hosted for you.

Start for Free Read the Docs
developers.acme.com/docs/api
Zuplo developer portal — interactive API reference with code samples
Why this matters

The portal is the API for everyone outside your team

Every developer's first impression of your API is your portal. If the docs are stale, the keys are slow, or the experience feels stitched together, the rest of your product can't recover the trust. The portal is the product surface — it should ship with the gateway.

×

Docs out of date the moment you ship

Every release adds a manual sync — update the spec, regenerate the docs, redeploy the static site, watch the search index reindex. Two of those steps eventually get skipped, and your customers' first impression is wrong.

×

Customers waiting for keys

Sales-led API key issuance — emails, Slack DMs, plaintext keys — is how trial users abandon. The signup-to-first-call gap is where most developer-led growth dies.

×

Three vendors for one experience

Docs in Mintlify. Pricing on Stripe. API keys in a custom dashboard. Three login flows, three sets of credentials, three places that drift. Customers feel the seams; your team maintains the seams.

×

Customization or maintainability — pick one

Off-the-shelf doc tools look great until you need a custom landing page or a usage dashboard. Then you fork it, maintain a private copy, and inherit a 6-month upgrade backlog the next time the upstream changes.

What you get

A docs site, an API console, a billing portal — one experience

Always in sync with your spec

OpenAPI is the source of truth. The same OpenAPI file that powers your gateway powers your developer portal — every new endpoint, schema change, and parameter update appears in the docs at the moment the gateway ships. Zero publishing step. Zero docs lag.

Self-serve, key to invoice

Customers sign up, create keys, run their first call, subscribe to a paid plan, watch their usage — all from one branded portal at your domain, without filing a ticket or talking to your team.

Customizable to React, hosted by Zuplo

Drop in MDX, custom React pages, any theme — but the build, deploy, and hosting are managed for you. Customization ceiling of an open framework, with the operational cost of a SaaS.

Custom pages, just a prompt away

Beautiful custom pages, just a prompt away

The portal ships with a rich component library — cards, callouts, code blocks, tabs, hero sections, pricing tables, search. Tell your AI assistant to build a /changelog or /case-studies page using those components and you get a polished page that already matches your brand. No design system to invent, no React boilerplate to write.

TypeScriptWire the page into navigation
export default {
  topNavigation: [
    { id: "docs", label: "Docs" },
    { id: "api", label: "API Reference" },
    { id: "pricing", label: "Pricing" },
  ],
  // Stripe-connected pricing, subscriptions, usage dashboard
  plugins: [monetizationPlugin()],
  customPages: [
    { path: "/changelog", component: "src/Changelog.tsx" },
    { path: "/case-studies", component: "src/CaseStudies.tsx" },
  ],
};
src/Changelog.tsx · using built-in components
import { Hero, Card, Stack, Badge } from "@zuplo/ui";

export default function Changelog() {
  return (
    <Stack>
      <Hero title="What's new" subtitle="Updates, weekly" />
      <Card>
        <Badge>v2.4.0</Badge>
        <h3>Streaming responses on /generate</h3>
        <p>...</p>
      </Card>
    </Stack>
  );
}
Auto-generated from OpenAPI
Self-serve API keys
Try it · live API explorer
Markdown / MDX / React
Custom domain · managed cert
Built-in usage dashboards
Read the Developer Portal Docs
What makes Zuplo different

A portal you can ship with, not against

The same portal that ships zuplo.com/docs

What you see at zuplo.com/docs is the developer portal that ships with every Zuplo project — battle-tested, performant, and built on an open framework on top of Vite + React. You're never locked into a black-box doc tool.

One gateway, multiple audiences

Public retail self-serve, partner with sales-reviewed onboarding, internal team behind SSO — all served by the same gateway with different visible API surface, different sign-in, and different brand. Run them as separate portal deployments or as one portal that branches on the user's identity.

First-class API key + monetization UX

Self-serve key management is included — not a paid add-on. Enable monetization and you also get pricing, subscription management, and a usage dashboard. Stripe-quality UX, without writing a Stripe Customer Portal integration.

Your domain, your brand

Custom domain via CNAME in minutes. Theme tokens for fonts, colors, spacing. Custom React pages for everything the auto-generation doesn't cover. The portal feels like part of your product, not a vendor's hosted site.

Real questions, real answers

What teams use this for

“We need docs at docs.acme.com that match our marketing site.”

Configure the custom domain (CNAME → cname.zuplodocs.com), drop your design tokens into the portal theme, and the portal serves at docs.acme.com with the same fonts, colors, and brand the rest of your product uses.

“The marketing team owns the home page; engineering owns the docs.”

Marketing writes MDX or custom React pages for landing/quickstart/marketing surfaces. Engineering owns the OpenAPI spec that drives the reference. Both ship through the same Git repo with the same review process.

“We need a public retail portal AND a sales-reviewed partner portal.”

Run two portals against the same gateway. Public at developers.acme.com — self-serve signup, free-tier API key minted on signup, only the public spec visible. Partners at partners.acme.com — sign-in via your IdP, applications go through an approval queue, the full API surface and contract pricing become visible after approval. Same gateway, same OpenAPI source of truth, two distinct audience experiences.

“Internal teams should see endpoints we don't expose externally.”

Stand up an internal portal at internal-apis.acme.com behind your corporate SSO. Wire in the internal-only OpenAPI specs alongside the public ones. Engineers see every endpoint and every internal service; external developers never know they exist. No duplicated docs site, no second source of truth.

Frequently Asked Questions

Common questions about the developer portal.

Ship a portal your developers actually want to read

Free Zuplo project, point it at your spec, and you're hosting docs.acme.com tomorrow.

Start for Free Read the Docs