Products — the Apinizer suite

One platform, ten modules. Same runtime, same identity, same audit across every API and AI request.

Apinizer ships ten modules that snap together into one Kubernetes-native control plane. Start with the API Gateway and add modules as you grow — or run the full suite under one Manager from day one.

Modules

API Gateway — Apinizer API/AI Gateway — multi-protocol data plane for HTTP, gRPC, WebSocket, SOAP, GraphQL, and AI traffic on one Java 25 runtime. 50+ policies for auth, traffic, transformation, and observability — out of the box.
AI Gateway — Token budgets, exact and semantic cache, prompt firewalls, RAG on your own VectorDB, and multi-LLM routing — governing every LLM, MCP, and agent request on the runtime that already runs your REST APIs.
Identity Manager — OIDC, OAuth 2.0, JWT, JOSE — plus mTLS, SAML, LDAP / AD, and database-backed federation. One identity surface for every Apinizer API and AI request, with three-tier permissions and Repository-layer audit.
API Portal — Open the front door for developers, partners, and AI agents. Stand up as many portals as you need — Public, Internal, Partner, Agents — each branded as your own. No own database, fully customizable, MCP-ready, live in regulated environments.
Analytics Engine — Watch every API call. Ship the log everywhere. Answer in seconds. Async traffic capture, fan-out to nine destinations in parallel, dashboards and tracing operators actually use, and anomaly detection with EMA + Bollinger Band — backed by Elasticsearch.
API Designer — Design the API. Ship the proxy. One click apart. OpenAPI 3, Swagger 2, and WSDL editing — with a one-click path from spec to a live, governed API on the same gateway, and instant documentation in every format your team needs.
API Creator — Apinizer API Creator — three ways to ship an endpoint without a microservice. DB to API turns SQL into REST. Mock API gives frontends real-shaped responses with auth. Script to API runs JavaScript or Groovy as an endpoint.
DB to API — Turn SQL queries and stored procedures into REST endpoints. Apinizer DB-to-API ships drivers for 10 databases, named-parameter binding, cursor unwrapping, and the same gateway pipeline as hand-written services.
Mock API — Mock APIs that look like the real ones. Apinizer Mock API ships condition-driven response routing, OpenAPI import, and the same auth + audit pipeline as live proxies — frontends never wait on backends again.
Script to API — Drop JavaScript or Groovy into Apinizer and ship it as an endpoint. GraalVM Polyglot for JS, pre-compiled Groovy classes for hot dispatch — both pass the full gateway pipeline with no microservice to run.
API Integrator — Connect anything to anything. Without writing the integration. Eighteen task types on one drag-and-drop canvas, chained with output keys and JSON Path, fired by cron, HTTP, or another flow — and governed by the same audit and identity stack as the gateway.
Cache — Apinizer Cache is a two-tier cache — a local in-pod tier inside every gateway, a Hazelcast cluster on Kubernetes for the distributed tier. Twelve first-party cache scopes, atomic invalidation on redeploy, throttle and quota on the same cluster.
Monitoring — Apinizer Monitoring — uptime probes from your regions, anomaly detection with EMA and Bollinger bands, ten platform alert triggers ready on day one, and severity-aware action chains to Slack, Microsoft Teams, ServiceNow, email, webhook, and more.

What you get on every module

One identity surface — OAuth 2.0, OIDC, JWT, mTLS, SAML — across humans, agents, and partners.
One audit trail at the persistence layer — every request, every policy decision, every config change.
One observability plane — token spend, latency, error rate, firewall hits, all in the same Analytics Engine.
One deploy posture — Kubernetes-native, air-gap-friendly, no data leaves your cluster.

Book a Demo · Read the docs

Products — the Apinizer suite

Modules

What you get on every module

Links