StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Product

  • Stacks
  • Tools
  • Companies
  • Feed

Company

  • About
  • Blog
  • Contact

Legal

  • Privacy Policy
  • Terms of Service

© 2025 StackShare. All rights reserved.

API StatusChangelog
  1. Stackups
  2. Stackups
  3. Hipache vs Seesaw

Hipache vs Seesaw

OverviewComparisonAlternatives

Overview

Hipache
Hipache
Stacks6
Followers11
Votes5
Seesaw
Seesaw
Stacks12
Followers70
Votes0
GitHub Stars5.7K
Forks508

Hipache vs Seesaw: What are the differences?

What is Hipache? A distributed HTTP and websocket proxy. Hipache is a distributed proxy designed to route high volumes of http and websocket traffic to unusually large numbers of virtual hosts, in a highly dynamic topology where backends are added and removed several times per second. It is particularly well-suited for PaaS (platform-as-a-service) and other environments that are both business-critical and multi-tenant.

What is Seesaw? Google Open Source Load Balancer in Go. Seesaw v2 is a Linux Virtual Server (LVS) based load balancing platform. It is capable of providing basic load balancing for servers that are on the same network, through to advanced load balancing functionality such as anycast, Direct Server Return (DSR), support for multiple VLANs and centralised configuration.

Hipache and Seesaw can be categorized as "Load Balancer / Reverse Proxy" tools.

Hipache and Seesaw are both open source tools. Seesaw with 4.81K GitHub stars and 460 forks on GitHub appears to be more popular than Hipache with 2.25K GitHub stars and 264 GitHub forks.

Detailed Comparison

Hipache
Hipache
Seesaw
Seesaw

Hipache is a distributed proxy designed to route high volumes of http and websocket traffic to unusually large numbers of virtual hosts, in a highly dynamic topology where backends are added and removed several times per second. It is particularly well-suited for PaaS (platform-as-a-service) and other environments that are both business-critical and multi-tenant.

Seesaw v2 is a Linux Virtual Server (LVS) based load balancing platform. It is capable of providing basic load balancing for servers that are on the same network, through to advanced load balancing functionality such as anycast, Direct Server Return (DSR), support for multiple VLANs and centralised configuration.

Statistics
GitHub Stars
-
GitHub Stars
5.7K
GitHub Forks
-
GitHub Forks
508
Stacks
6
Stacks
12
Followers
11
Followers
70
Votes
5
Votes
0
Pros & Cons
Pros
  • 3
    Redis as backend
  • 1
    Easy setup
  • 1
    Fast
No community feedback yet

What are some alternatives to Hipache, Seesaw?

HAProxy

HAProxy

HAProxy (High Availability Proxy) is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications.

Traefik

Traefik

A modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components and configures itself automatically and dynamically.

AWS Elastic Load Balancing (ELB)

AWS Elastic Load Balancing (ELB)

With Elastic Load Balancing, you can add and remove EC2 instances as your needs change without disrupting the overall flow of information. If one EC2 instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running EC2 instances. If the failed EC2 instance is restored, Elastic Load Balancing restores the traffic to that instance. Elastic Load Balancing offers clients a single point of contact, and it can also serve as the first line of defense against attacks on your network. You can offload the work of encryption and decryption to Elastic Load Balancing, so your servers can focus on their main task.

Fly

Fly

Deploy apps through our global load balancer with minimal shenanigans. All Fly-enabled applications get free SSL certificates, accept traffic through our global network of datacenters, and encrypt all traffic from visitors through to application servers.

Envoy

Envoy

Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.

node-http-proxy

node-http-proxy

node-http-proxy is an HTTP programmable proxying library that supports websockets. It is suitable for implementing components such as proxies and load balancers.

DigitalOcean Load Balancer

DigitalOcean Load Balancer

Load Balancers are a highly available, fully-managed service that work right out of the box and can be deployed as fast as a Droplet. Load Balancers distribute incoming traffic across your infrastructure to increase your application's availability.

Google Cloud Load Balancing

Google Cloud Load Balancing

You can scale your applications on Google Compute Engine from zero to full-throttle with it, with no pre-warming needed. You can distribute your load-balanced compute resources in single or multiple regions, close to your users and to meet your high availability requirements.

F5 BIG-IP

F5 BIG-IP

It ensures that applications are always secure and perform the way they should. You get built-in security, traffic management, and performance application services, whether your applications live in a private data center or in the cloud.

GLBC

GLBC

It is a GCE L7 load balancer controller that manages external loadbalancers configured through the Kubernetes Ingress API.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana