Quickstart · 5 minutes

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

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 K8s, OpenShift, Tanzu, Rancher, or any managed cluster.

# Per-module charts on the Docker Hub OCI registry (apinizercloud)
# 1) API Manager — control plane + UI
$ helm install apimanager \
    oci://registry-1.docker.io/apinizercloud/apinizer-apimanager \
    -n apinizer --create-namespace

# Other modules ship as their own charts:
#   apinizer-worker · apinizer-cache · apinizer-apiportal · apinizer-integration

02
Sign in to the Manager
Open the Manager UI on the address printed by the chart. Create a Project — the Gateway Path becomes the URL prefix for your APIs.
```
$ kubectl get svc -n apinizer apinizer-manager
# NAME              TYPE     EXTERNAL-IP  PORT(S)
# apinizer-manager  Service  ...          443/TCP
```
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.
```
proxy:
  name: orders-api
  type: REST
  upstream: orders-service
  endpoints:
    - path: /orders/{id}
      method: GET
```
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.
```
$ apinizer apply -f orders-api.yaml
$ curl https://gateway.example.com/orders/42
```