Oh wow, service mesh identities are a layer I hadn't even considered. That's a great point and feels like a huge blind spot for teams focused on CI/CD audits.
So basically, any internal service with its own mTLS cert talking through Access is now on the bill? That's going to add up so fast.
That guardrail for new accounts is a smart move. Have you found that the added friction in your CI/CD playbook actually slows down developer onboarding for new projects? I'm curious if teams start looking for ways to bypass it.
The finance ask for a forecasting dashboard is exactly the kind of shift I was wondering about. It ties software cost directly to headcount, which feels like it could change hiring approvals. Does your dashboard track service account creation separately from human hires? That seems like it would be two very different growth curves.