history_edu 30 years in the field

Built by someone who's been on both sides of this problem.

Tim Fraser has spent 30 years in infrastructure, from building an ISP in the late 1990s through sysadmin and cloud lead roles across Australia. He's been the person expected to explain the bill, debug the production issue, and work out what changed after a messy handover.

Tim isn't a startup founder who read about DevOps. He's still doing the job. plainfra is the tool he built because he wanted a safe, plain-English way to inspect AWS without giving another product write access.

engineering

I've seen what gets missed

In 30 years of infrastructure work, I've watched the same pattern repeat. The team is busy deploying, maintaining, and keeping the lights on. Cost drift, old security group rules, missing CloudWatch alarms, and forgotten resources sit just outside the daily queue until somebody asks a hard question.

visibility

plainfra is the independent check I wanted

I built plainfra to look at an AWS environment the way a senior engineer would. Not to replace your team, but to give the person responsible for the account a plain-English view of what's there, what's changed, and what needs attention.

verified_user

Safe by design

plainfra runs through a read-only CloudFormation role in your AWS account. It can inspect security groups, Cost Explorer, CloudWatch alarms, and S3 bucket configuration. It cannot start or stop resources, modify IAM, deploy anything, read S3 object contents, read database rows, or read Secrets Manager secret values.

See what your AWS account is actually telling you.

Start a trial. See what plainfra finds in your AWS account in minutes.

50K tokens • 48 hours free • Read-only access • Cancel anytime