FAQ
Questions, Answered
What Lizrd is, who it's for, what you connect, how pricing works, and how we keep you safe.
General
- What is Lizrd?
- An engineering excellence platform that sits where FinOps, cloud monitoring, and engineering meet. From your real usage and billing data, it shows engineering teams exactly where their infrastructure money goes and why — then guides them, step by step, through quick, low-risk optimizations.
- Who is Lizrd for?
- Engineering leaders and engineers. Leaders get transparency and realize savings with predictable, minimal engineering time; engineers get the exact fix and the confidence to ship it. Your FinOps and finance stakeholders get numbers they can trust.
- What do I connect?
- Your clouds (AWS, GCP, Azure) and your code hosts (GitHub, GitLab) — all read-only. Connecting code lets Lizrd tie each recommendation to the exact file to change.
- Do I need infrastructure-as-code?
- No — Lizrd works without it. But it is strongest when your infrastructure is defined as code (Terraform and more): every recommendation ties to the exact code to change, so acting is a copy-paste diff.
- Does Lizrd change my infrastructure?
- No. Access is read-only. Every optimization is a recommendation you review and apply yourself — you are always in control.
Pricing & billing
- Is Lizrd free during the beta?
- Yes. While we are in private beta, design partners use Lizrd free of charge. We are still shaping our value-based pricing with early customers and will always share it before it applies — no surprises.
- How will Lizrd be priced?
- One flat monthly fee based on your cloud spend under management — your real, billed cloud cost across the accounts you connect — in predictable bands. Never per-seat.
- What counts as "cloud spend under management"?
- Your real billed cloud cost across the accounts you connect (AWS, GCP, Azure), net of discounts and credits — the actual total from your bill, not an estimate.
- What about Enterprise?
- For large spend, or teams needing SAML/SCIM, custom access controls, a security review, SLAs and a DPA, we tailor a plan with dedicated support. Talk to us.
AI & GPU workloads
- Does Lizrd find waste in AI and GPU infrastructure?
- Yes. Lizrd reads real GPU utilization, inference-endpoint traffic, and accelerator sizing to find idle and over-provisioned AI infrastructure — then gives you the exact fix, with the same evidence, confidence level, and one-step guidance as every other recommendation.
- What kinds of AI waste does it detect?
- Idle and underused GPU instances and managed inference endpoints, over-provisioned accelerators (right accelerator, right size), endpoints that should scale to zero between bursts of traffic, and batch or fine-tuning jobs that belong on cheaper Spot GPUs.
- Which AI services are covered?
- Across all three clouds: AWS SageMaker and Bedrock, Google Vertex AI, and Azure ML and Azure OpenAI — plus the GPU instances (like EC2 g5/p-series) behind your own training and inference.
- How does Lizrd see GPU utilization?
- From your cloud’s own GPU metrics, read-only — so an endpoint running at 1% GPU with no traffic, or a four-GPU box sitting at 14%, shows up with the evidence behind it, not a guess.
- Is it safe to act on an AI recommendation?
- Yes. Access stays read-only and nothing changes without your approval. Each fix spells out effort, risk, and rollback — deleting an idle endpoint keeps the model and config, and rightsizing is a reversible one-line change.
Security & trust
- What access does Lizrd need?
- A least-privilege, read-only role that you approve — for example an AWS role granting read-only access for cloud, or a scoped, read-only connection for your code repositories.
- What does Lizrd read — and what does it never touch?
- It reads infrastructure inventory, configuration, utilization metrics, and billed cost, plus infrastructure-as-code metadata. It never reads your application or customer data, source secrets, or environment variables — and never writes, modifies, or deletes anything.
- How is my data protected?
- Credentials are sealed with AES-256-GCM envelope encryption with rotation-ready keys, and every organization is isolated at the database layer so data never crosses tenants.
- Can I revoke access at any time?
- Yes. Remove the role or revoke the token and Lizrd immediately loses all access — no lingering credentials.
Still have a question? Email hello@lizrd.ai. Found a vulnerability? Email hello@lizrd.ai.
Start Optimizing and Reducing Cost
Connect read-only and see your first optimizations — the exact fix included.