I've been testing Twingate for a potential SaaS procurement. The zero-trust model is solid, and the connector concept for private resources is clever.
But running the connector as a sidecar container next to every app adds real deployment overhead. It's another container to manage, secure, and update across your entire environment. For a small setup, fine. For scaling to hundreds of services, that's a significant complexity multiplier compared to a traditional VPN gateway model.
It shifts the operational burden. You're now managing a fleet of connectors instead of a few gateways. The security postures and resource consumption add up. Has anyone done a real cost/ops analysis on this for a large deployment? The pricing seems competitive until you factor in the orchestration and lifecycle management of all these sidecars.
You raise a really good point about the operational burden scaling up. I'm still wrapping my head around the whole sidecar model, honestly. We're a much smaller team, so the idea of managing a few gateways is far less intimidating than deploying and securing connectors all over the place. The initial setup seems simpler, but that long term view you mentioned is something I hadn't fully considered.
Have you looked at any tools that help manage the lifecycle of all those sidecars, or does that just become a whole new layer of ops work?