Skip to content

CloudInfra Proxy Manager

CloudInfra Proxy Manager

A proxy you can actually see into, and change without holding your breath.

CloudInfra Proxy Manager is a management, analytics and policy layer for Squid on AWS, Azure and Google Cloud. Squid is excellent at proxying and offers almost nothing for running it: no traffic visibility, no readable policy, and a configuration file where one typo stops the service. This adds the parts that were missing.

Everything runs on your own instance. No traffic data leaves your network, and there is no cloud service to depend on.

Just launched? Start here How it works Security model


Where do you want to start?

  • Just launched the image?


    Sign in, confirm the proxy is healthy and send your first request through it.

    Your first 10 minutes

  • Want to control what is reachable?


    Write access rules in plain language, and see exactly which rule decided each request.

    Access rules

  • Want to know who, not just which address?


    Authenticate proxy users against Active Directory, Entra ID or OpenLDAP.

    Directory authentication

  • Running Microsoft 365 behind the proxy?


    Keep Teams, Exchange and SharePoint working without maintaining hundreds of endpoints by hand.

    Microsoft 365 endpoints


What it adds to Squid

  • See your traffic


    Live request stream, historical analytics, top destinations and clients, cache effectiveness and blocked-request reporting — read from Squid's own log rather than from an agent.

    Dashboard

  • Readable access policy


    Rules that read as sentences — "Deny clients in 10.20.0.0/16 to reach facebook.com" — generated into correct Squid ACLs. You never edit squid.conf by hand.

    Access rules

  • Changes that undo themselves


    Every change is validated, snapshotted, applied and health-checked. If the proxy does not come back healthy, the previous configuration is restored automatically.

    Applying changes

  • Know which rule blocked it


    Squid has no native field for which rule decided a request. This stamps each one, so a blocked request tells you the policy that blocked it — not just that something did.

    Live traffic

  • Health you can account for


    Fourteen named checks, each with a fixed published weight. The score is arithmetic you can follow, not a number with no explanation.

    Health

  • No SSH required


    Read Squid's access and error logs, and the manager's own, from the console. Search, filter by severity, and look into rotated files.

    Logs


Built to be run, not just installed

14
Scored health checks
10
Privileged operations, closed set
3
Third-party code dependencies
0
Outbound connections by default

The management console runs unprivileged. Anything needing root goes through a small helper over a local socket that accepts a fixed set of named operations and nothing else — no paths, no command fragments, no shell. The whole product is a single static binary with three third-party libraries, because a security appliance's own dependency tree is part of its attack surface.

Read the security model


Where it runs

Available as a pre-built image on the AWS, Azure and Google Cloud marketplaces, built on Ubuntu 24.04 LTS with Squid 7.

The proxy and the management console are deliberately independent: if the console stops, Squid keeps proxying, and if Squid stops, the console still comes up to tell you why.

Deploy the image View our images