Side by side

Apache Traffic Server vs Squid

Both stand on caching software. Which one you can start free with, which one lets you read the code, and what each costs once you pay.

Apache Traffic Server

Free plan Open source APILinuxMac+1

Apache Traffic Server combines caching, proxying, and layer 7 load balancing in a self-hosted server. Its deployment options and plug-in APIs suit organizations that need to tailor proxy behavior.

Visit Apache Traffic Server

Squid offers self-hosted caching, access controls, and multiple cache arrangements without a software charge. Basic authentication has a stated credential-security limitation, and direct project contact is not a user-support channel.

Visit Squid

The facts

	Apache Traffic Server	Squid
Free plan	Yes	Yes
Open source	Yes	Not published
Runs on	API, Linux, Mac, Self-hosted	Linux, Mac, Self-hosted, Windows
Lowest paid plan	Free or on request	Free or on request
Plans published	1	1
Maker	Not published	Not published
Website	trafficserver.apache.org	squid-cache.org
On caching software	#1 of 27	#12 of 27

Apache Traffic Server: what it does well

Free and open source under Apache License 2.0.
Supports HTTP/1.1 and HTTP/2.
Offers proxy, reverse proxy, and cache hierarchy deployments.
Plug-in APIs support custom behavior.
Includes SSL termination and client access controls.

What to know first

Self-hosted deployment requires managing the installation.
The listed stable release is 10.2.0; 9.2.15 is the LTS release.

Squid: what it does well

Free to download, use, and modify.
Supports HTTP, HTTPS, FTP, and gopher data.
Can form content clusters for load balancing.
Offers several authentication methods and backend helpers.
Available for Linux, macOS, and Windows.

What to know first

Basic authentication does not encrypt credentials.
Direct project contact is not for user support.
Commercial support may be available through third parties.

Alternatives to Apache Traffic Server Alternatives to Squid The whole list