The Apinizer suite
Five modules. One operational surface.
Manager, Worker, Portal, APIops, and Cache — installed together, but versioned as separate modules so you only operate what you need. All on Kubernetes.
- CORE PRODUCTOpen the Gateway page
Worker — data plane
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.
- NEWOpen the AI Gateway page
AI Gateway — agentic plane
AI Gateway
Govern every LLM, MCP, and agent request on the Apinizer AI Gateway. Token budgets, cost attribution, response caching, prompt firewalls, and multi-LLM routing across 17+ providers — on the same runtime as your REST APIs.
- Open the Identity page
Identity Manager
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.
- Open the Portal page
API Portal
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.
- Open the Analytics page
Analytics Engine
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.
- Open the Designer page
API Designer
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.
- DIFFERENTIATOROpen the Creator page
API Creator — three ways to skip the microservice
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.
- ZERO MICROSERVICEOpen the DB to API page
API Creator · DB to API
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.
- FRONTEND UNBLOCKEDOpen the Mock API page
API Creator · Mock API
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.
- NO MICROSERVICEOpen the Script to API page
API Creator · Script to API
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.
- Open the Integrator page
API Integrator · Task Flow Manager
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.
- Open the Cache page
Cache
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.
- Open the Monitoring page
Monitoring
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.
The whole suite
One platform. Five modules.
See Manager, Worker, Portal, APIops, and Cache — running together on a Kubernetes of your choice.