Infrastructure
CostGraph Cloud runs on AWS, and your data is hosted in theus-east-2
region. The app and API are served over HTTPS. Database storage is encrypted at
rest with AWS KMS.
Sign-in
People sign in with one of:- Email and password. Passwords need at least 8 characters, with upper and lower case letters, a number, and a symbol. People can add an authenticator app as a second factor under their account’s Security settings.
- Google.
- Your identity provider through SAML or OpenID Connect single sign-on. Owners can require single sign-on for everyone with an email address at a verified domain.
Access control
Every member has a role: owner, admin, billing admin, or member. See Roles and permissions for what each one can do. An organization holds one or more tenants. Every request that reads or changes tenant data names the tenant, and CostGraph checks that the caller can access it before it runs. An API key or app token is bound to one tenant and can’t reach another.Machine credentials
- API keys carry scopes and act with their creator’s current role. CostGraph stores a keyed hash of each key, never the key itself, and shows only its last four characters. A key can have an expiry date.
- Apps that use Sign in with CostGraph get tokens limited to the scopes the person approved. App tokens can’t manage API keys, single sign-on, or alert destinations.
- SCIM tokens are stored as hashes and shown once.
Integration credentials
When you connect a provider, CostGraph prefers access that doesn’t need a long-lived secret:- AWS: an IAM role that CostGraph assumes with an external ID. Access keys are also accepted.
- Google Cloud: workload identity federation. A service account key is also accepted.
What CostGraph collects
CostGraph collects cost and usage data, not your application data.
The operator’s cluster role lists the Kubernetes resources it can read.
Secrets, ConfigMaps, and service accounts aren’t on that list, so the operator
can’t read them.