Skipper review
A self-hosted Kubernetes ingress and reverse proxy with advanced traffic controls.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Skipper is an open-source HTTP router and reverse proxy for service composition. It is designed for infrastructure teams operating self-hosted proxy and ingress deployments, either as a standalone proxy or as a Kubernetes Ingress controller. Requests can be matched using paths, methods, hosts, headers, cookies and other predicates, then passed through configurable request and response filters before reaching backend services or load-balanced backend groups.
Routing is Skipper’s defining strength. The published feature set covers dynamically updated routes, response caching with in-memory LRU and optional shared L2 storage, instance-local and cluster-wide rate limiting, TLS termination and mutual TLS. It also supports traffic shadowing, circuit breakers and blue-green deployment patterns, giving Kubernetes operators controls for traffic shaping and service composition beyond basic path forwarding. Integrations with Kubernetes, etcd, Redis and Valkey support its broader infrastructure fit.
Skipper is a strong match for teams that want open-source, self-hosted routing with detailed predicates and operational traffic controls. Its platform coverage includes Linux, Windows and macOS, while its deployment model remains self-hosted rather than hosted SaaS. The breadth of features may be more than needed for a straightforward reverse proxy, and WebSocket handling is documented as an experimental upgrade feature. Choose Skipper when Kubernetes routing, caching, rate limiting, mTLS and deployment controls are central requirements; a simpler proxy is a better fit when those controls are unnecessary.
Skipper pros and cons
- Where it wins
- Predicate-based routing across paths, methods, hosts, headers and cookies
- Cluster-wide rate limiting, caching, mTLS and circuit breakers
- Runs standalone or as a Kubernetes Ingress controller
- Where it doesn't
- Self-hosted deployment requires infrastructure ownership
- WebSocket support is documented as experimental
- Its extensive controls may exceed simpler routing needs
Skipper fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update