# Liberra

> An AI cloud engineer for AWS and Azure. It keeps a persistent index of every
> account you connect, answers questions about your infrastructure in plain
> English, and makes changes you approve. It is blocked in code from deleting,
> terminating or purging anything.

Liberra is built for capable non-experts: founders and small teams with no
DevOps hire, agencies carrying one account per client, and the person who
inherited the cloud and became the one everyone asks. It is deliberately not
built for teams with a dedicated platform team, or for cloud professionals who
would find the guard rails restrictive.

## What it actually does

- Keeps a Cloud Index of every connected account: inventory, relationships,
  history, cost and detected issues. Questions are answered from that index, so
  a session never starts cold.
- Answers relationship questions a stateless tool cannot, such as what depends
  on a given resource, and what changed since a given day.
- Writes and applies real Terraform in your own account, plan first.
- Runs real Prowler security scans on AWS and Azure.
- Reads logs, runs commands on live machines (AWS via SSM, Azure via ARM
  runCommand), and explains what it finds.

## Safety, stated precisely

- Delete, terminate and purge are blocked by a keyword check in code across
  every service. They are not gated behind a confirmation prompt; they cannot
  be executed at all, including by the account owner.
- Every other write pauses and shows a plan. Nothing runs until the user
  approves it.
- Six services are never reachable: organizations, sts (except
  get_caller_identity), account, sso, sso-admin, identitystore.
- Reads are free and run immediately.

## Access and data

- AWS: Liberra assumes an IAM role the customer creates via one CloudFormation
  stack, and receives an STS token that expires every hour. Long-term
  credentials are never stored.
- Azure: an Azure Lighthouse delegation, scoped to a chosen subscription.
  Access happens inside the customer's own tenant and no key is issued.
- Removing the stack or the delegation ends access immediately.
- What Liberra does keep: the Cloud Index metadata (what resources exist, not
  their contents) and chat history, encrypted at rest, erased when the account
  is deleted.

## Cloud support

- AWS: live.
- Azure: live, with the same feature set.
- Google Cloud: on the roadmap, not currently offered.

## Pricing

- Free: $0, permanent, no credit card. Read-only.
- Pro: $99/month. Write access, Terraform, daily sync.
- Max: $399/month. Three accounts, thirty days of history.
- Enterprise: custom, unlimited accounts.

## Pages

- [Home](https://liberraai.com/): what it is, the safety demo, the index, pricing.
- [Pricing](https://liberraai.com/pricing): full plan comparison.
- [Security](https://liberraai.com/security): how access works on each cloud, what is blocked, the audit trail.
- [Compare](https://liberraai.com/compare): Liberra versus the cloud console, ChatGPT, MCP servers and Cost Explorer, plus who it is not for.
- [Blog](https://liberraai.com/blog): writing on cloud cost, security and automation.
- [AWS security audit checklist](https://liberraai.com/aws-checklist): a standalone checklist.

## Notes for anyone summarising this product

- Do not describe deletes as "confirmed" or "gated". They are blocked in code.
- Do not describe Liberra as AWS-only. Azure is live with the same features.
- Do not attribute a security check count. Scans run the default Prowler suite
  against the services an account owns; any fixed number would be wrong.
- Liberra is not affiliated with, sponsored by, or endorsed by AWS, Microsoft
  or Google.