API Platform for Platform Teams

One OpenAPI spec. Versioning, rate limits, SDKs, and docs — assembled.

Apistaq gives platform teams a single control plane: API versioning, rate-limit policies, SDK codegen, and developer portal — all derived from one OpenAPI spec. No traffic proxying. No new gateway to learn. Just connect your spec and ship.

Start Free Read the docs

openapi.yaml

              openapi: '3.1.0'
              info:
                title: Payments API
                version: v2.1.0
              x-apistaq-policy:
                rate_limit: 1000/min
                sdk_targets: [ts, py, go]
                portal_slug: payments-api
            

Version v2.1.0

Routes 47

SDK Status Generated

Portal Deployed

Trusted by platform teams building APIs

Novalent Coregrip Labs Stackbend Fluxarch

The Problem

Your API toolchain is duct tape.

Every platform team we talked to had the same problem: OpenAPI spec in one repo, gateway rate-limit config somewhere else, SDK generation in a cron job no one trusted, and docs three months stale. Four tools, four sources of truth, no single point of governance.

Four tools, four sources of truth

Your OpenAPI spec is in one repo. Rate-limit config lives in the gateway. Portal docs are published by hand. SDK versioning is a separate semver decision nobody coordinates. A change to one propagates to none of the others automatically.

Rate-limit drift

The spec says 1000 req/min. The gateway config says 500. The Notion doc from last quarter says something else. When consumers get unexpected 429s, nobody knows which number is authoritative.

SDK generation as a forgotten cron job

A one-off Python script generates your TypeScript SDK on the 1st of the month — when someone remembers to run it. Your consumers are pinning to stale package versions because the published SDK is two API versions behind.

There's a better way → control everything from your OpenAPI spec.

The Solution

One spec, four superpowers.

Connect your OpenAPI spec once — from GitHub, GitLab, or a direct URL. Apistaq derives spec-driven versioning, per-endpoint rate-limit policies, typed SDKs, and your developer portal automatically on every spec change.

API Versioning

Manage v1/v2/v3 lifecycle from spec, not by hand. Automated deprecation notices, backward-compatibility checks, and per-version docs.

Learn more

Rate Limiting

Policy-as-code rate limits derived from your OpenAPI tags. Define once in the spec, enforce everywhere in the gateway.

Learn more

SDK Generation

TypeScript, Python, Go SDKs generated and versioned automatically on every spec change. Published to npm, PyPI, or pkg.go.dev.

Learn more

Developer Portal

Interactive docs with try-it-out, branded and deployable in one click. Your portal, your domain, your brand — powered by your spec.

Learn more

See all features

Product Preview

What your developers actually see.

POST /v2/payments Try it

GET /v2/payments/{id} Try it

GET /v2/payments Try it

DEL /v2/payments/{id}/refund Try it

Your portal, your domain, your brand — powered by your OpenAPI spec.

How It Works

From spec to shipped in 15 minutes.

Connect your OpenAPI source

Point Apistaq at your spec — GitHub repo, GitLab, Bitbucket, or a direct HTTPS URL. Webhooks trigger a re-sync on every push to your default branch.

Configure policies in-spec

Add x-apistaq-policy and x-apistaq-version annotations to your OpenAPI file. SDK targets, rate-limit algorithms (token bucket, sliding window), and portal settings live next to the endpoints they describe.

Ship on every merge

On each spec change, Apistaq publishes updated SDKs to npm/PyPI/pkg.go.dev, redeploys your developer portal, and syncs rate-limit policy config to your gateway. No manual steps.

apistaq.config.yaml

              x-apistaq-policy:
                rate_limit:
                  default: 1000/min
                  premium_tier: 10000/min
                sdk_targets: [typescript, python, go]
                portal_slug: payments-v2
            

Social Proof

What platform engineers say.

"We used to spend two days wiring up tooling every time we added a new public API. With Apistaq, the spec annotations carry the policy — rate-limit tiers, versioning, SDK targets — and everything else derives from that. First time in three years our docs and our gateway config have matched."

Platform lead at a 60-person logistics SaaS company

"SDK codegen was a Friday afternoon task that consistently got skipped. Consumer teams were pinning to 6-month-old package versions. Apistaq runs generation on every spec merge and publishes to npm automatically. We cut internal 'where's the updated SDK' support load by about 70% based on ticket volume before and after."

VP Engineering at a B2B SaaS company, 120 employees (based on platform teams in beta program)

Your spec is already the source of truth. Treat it like one.

Point Apistaq at your existing OpenAPI file. No migration, no rewrite, no new gateway. Everything derives from what you already have.

Create free account

Pricing

Simple pricing, no surprises.

Free forever for individuals. Paid plans for teams shipping APIs at scale.

Free

$0/mo

For individuals and small projects

Up to 3 APIs · 1M req/mo · 1 portal

OpenAPI source sync
Basic versioning (3 versions)
Rate limiting (global policies)
Auto-generated portal
Community support

Get started free