Launch API products with auth, limits, and plans

Create a product, choose auth, set rate limits, and publish pricing without stitching together gateway config by hand.

Four pieces your API launch flow already understands

The product wizard keeps the core setup loop consistent from first draft to published plans.

product()Define the API name, base URL, and draft description before rollout.

auth()Choose how consumers authenticate, starting with API keys and leaving room for OAuth.

limits()Set request, token, or concurrency limits as the default contract for the product.

plans()Publish free, flat, or pay-as-you-go plans without rebuilding the gateway by hand.

The site keeps the Wubber-style rhythm, but the workflow is about your product setup: draft, controls, and publish.

Start with product basics and keep the workflow resumable while you shape the API surface.

Choose auth and rate limits before the product goes live, so the contract is defined up front.

Add plans, review the local stack status, and publish when the product is operational.

`web-ui` still reads `core`, and `core` reports whether Postgres is actually ready.

Web UI

Running

Next.js server component rendered successfully.

Core API

Reachable

Responding from https://fs-core-stage.up.railway.app

Postgres

Ready

Readiness confirmed at Mar 25, 2026, 9:00 AM UTC

Turn API setup into a repeatable product launch workflow.