Beta Testers Needed for New AWS Cost Tracking Tool

I'm building a free web application that helps AWS users track their cloud spending over time. The application allows users to upload their AWS billing CSV files and see: Monthly AWS spending Spending by AWS service Spending trends Month-over-month changes Project-level costs using AWS Project tags Untagged spending Historical AWS cost data Multiple months/years of billing history I have added my report to this application. I'm looking for multiple beta testers with different AWS environments to help me make sure the application works correctly across real-world scenarios. What you'll do You'll receive access to the application and be asked to: Create an account. Download an AWS billing CSV from your AWS account. Upload it to the application. Review the results. Try different date ranges and billing periods. Test uploading multiple months at once. Test uploading historical data. Look for incorrect totals or missing services. Try the Project/tagging features if your AWS data supports them. Report anything confusing, incorrect, or broken. You do NOT need to give me access to your AWS account. You will upload your own AWS billing CSV to the application. Never provide AWS access keys, passwords, IAM credentials, or other AWS login information. Who I'm looking for I'd especially like testers with different types of AWS accounts, including: Small personal AWS accounts Developer/lab accounts Accounts with multiple EC2 instances Accounts using S3, CloudFront, Lambda, RDS, etc. Accounts with AWS resource tags You don't need to be an AWS expert, but you should be comfortable navigating AWS Cost Explorer and downloading a CSV. Deliverable At the end of the test, you will update a short form containing: What worked What didn't work Any confusing screens Any errors Suggestions for improvement Approximately 30–60 minutes per tester. I'm initially hiring multiple testers because I specifically want to test the application against different AWS billing environments and CSV formats. Important Do not provide AWS credentials. The application is designed specifically so that it does not need access to your AWS account. Your AWS billing CSV may contain information about your AWS environment, so only participate if you're comfortable uploading that information to a beta-testing application. In your proposal, please tell me: Approximately how many AWS services you currently use. Whether your resources use AWS tags. I'm looking for testers who are curious, detail-oriented, and willing to tell me when my numbers are wrong. keyword block Full Stack Developer, Full Stack Engineer, Full Stack Web Developer, Software Engineer, Web Developer, Backend Developer, Frontend Developer, AWS Developer, AWS Engineer, Cloud Engineer, DevOps Engineer, DevOps, AWS, Amazon Web Services, AWS Cost Explorer, AWS Billing, AWS Billing CSV, AWS Cost and Usage, AWS Cost Analysis, AWS Cost Management, AWS Cost Optimization, FinOps, Cloud Cost Management, AWS Resource Tagging, AWS CLI, EC2, S3, Lambda, CloudFront, RDS, DynamoDB, Route 53, CloudWatch, SaaS, SaaS Development, SaaS Testing, Web Application Testing, QA, QA Testing, Quality Assurance, Software Testing, Functional Testing, Manual Testing, Exploratory Testing, Beta Testing, User Acceptance Testing, UAT, Bug Testing, Bug Reporting, Data Validation, CSV Testing, API Testing, Frontend Testing, Backend Testing, Database Testing, Full Stack QA, Application Testing, Regression Testing, Edge Case Testing, Usability Testing.