Quickstart

From zero to your first proxy in five minutes.

Install Apinizer, define an API Proxy, deploy it to an Environment, and call it. Production-shape from the very first request.

Open the docs · Browse guides

Steps

01 — Install on a cluster

Apinizer ships as per-module Helm charts on the Docker Hub OCI registry (apinizercloud). Install the API Manager first; the Gateway, Cache, Portal, and Integration are separate charts. Works on standard Kubernetes, OpenShift, Tanzu, Rancher, or any cloud-managed cluster.

helm install apimanager oci://registry-1.docker.io/apinizercloud/apinizer-apimanager -n apinizer --create-namespace

Open the Manager UI on the address printed by the chart. Create a Project — the Gateway Path becomes the URL prefix for your APIs.

03 — Define an API Proxy

Add a REST API Proxy from the UI or apply an APIops manifest from CI. Reference everything by name — Apinizer wires up the routing.

04 — Deploy and call it

Deploy the proxy to an Environment (a Kubernetes Namespace under the hood). The Worker hot-reloads the routes — no restart, no dropped sockets.

Where to go next

Quick Start guide (docs) — the official walkthrough: create your first API Proxy end to end. (https://docs.apinizer.com/en/develop/quick-start)
Conceptual guides — Environment, Project, Proxy, Policy, Variable, Connector. The core concepts in one place. (https://apinizer.com/developers/docs)
Scripting recipes — Groovy and JavaScript snippets for header rewrites, envelope shaping, and async logging. (https://apinizer.com/developers/docs/scripting)
APIops samples — Drop-in CI snippets for GitHub Actions and GitLab CI. (https://apinizer.com/developers/apiops)

Stuck?

The platform team is one call away. Walk through install, your first proxy, and your first AI route — on a Kubernetes of your choice.

Book a Demo · Read the docs