How Aithrex handles security.
Security is an engineering property at Aithrex, not a marketing line. Here is how we build it into everything we ship, and how each product, Infratrix, the Observability Platform, and the Resume Parser, treats your data and your cloud.
Trust is engineering, not marketing.
We do not list certifications we have not earned. Instead we describe how we build and run, so your security team can verify each property for themselves. These commitments hold across every product we ship.
Reviewed, line by line
AI with accountability
Scoped by default
Only what is true
Infratrix runs inside your AWS account.
Infratrix, our flagship, reads your account as a connected graph and proposes changes. Every part of that runs in your account, under access you grant and can revoke. Here is the model in detail.
In-account by default
Scoped IAM, least privilege
Customer-held kill switch
Audit trail, no surprises
Explicit about scope, not vague about it.
Architecture-aware reasoning needs resource metadata, not application data. Below is what the Infratrix agent reads, what it does not read, and what it never applies without.
- Resource metadata: VPCs, subnets, route tables, security groups, IAM roles/policies, S3 buckets, EC2/EKS/RDS configuration
- Cost & usage signal from Cost Explorer and CloudWatch metrics needed for the finding
- VPC flow log shape (path-level, not packet content) where you've already exported it
- Application data inside S3 buckets, RDS rows, or any workload payloads
- Secrets, parameter store values, KMS plaintext, or anything that decrypts customer data
- CloudTrail entries unrelated to the resources we're reasoning about
- A plan reviewed by your team
- An action-scoped IAM role you've authorized
- A stored inverse operation attached to the change
Two roles, both yours.
Onboarding creates two IAM roles in your account from a documented Terraform template. InfratrixDiscoveryRole is read-only and used for graph construction. InfratrixActorRole is scoped per-action-class and is only assumable to apply a plan you have explicitly approved.
Both roles live in your account. There is no cross-account trust granted to a long-lived Infratrix-side identity for production writes, every write session is short-lived and audit-logged.
The full template, including comments on every Action, is shared during onboarding and reviewed before any role is created.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "InfratrixDiscoveryReadOnly",
"Effect": "Allow",
"Action": [
"ec2:Describe*",
"ec2:Get*",
"vpc:Describe*",
"elasticloadbalancing:Describe*",
"iam:Get*",
"iam:List*",
"s3:GetBucketLocation",
"s3:ListAllMyBuckets",
"s3:GetBucketTagging",
"cloudwatch:GetMetricData",
"ce:GetCostAndUsage"
],
"Resource": "*"
}
]
}Excerpt. The actor role uses a separate template with per-actionCondition blocks.
One revocation. Everything stops.
The trust path is the IAM role. There is no second credential, no SaaS-side backup, no support-engineer bypass. If you delete the two roles, every Infratrix agent loses access to your account immediately.
We test this on every onboarding. A successful kill-switch drill is part of the go-live checklist, before any production write role is created.
# One command halts every Infratrix action in this account.
aws iam delete-role --role-name InfratrixDiscoveryRole
aws iam delete-role --role-name InfratrixActorRoleTested on every onboarding. Documented in the runbook your team keeps.
Your telemetry never leaves your cloud.
The Observability Platform is built bring-your-own-cloud. It runs inside your own account, so the data it watches stays in the environment that owns it. It is in development, and we will publish the same depth of detail we give Infratrix, IAM scope, data paths, and controls, before it is generally available.
Runs in your own cloud
Your telemetry stays put
Agentic triage, in place
Candidate data, under the same practice.
The Resume Parser & Job Finder turns a resume into structured data and matches it to roles, which means it handles candidate information. It is built and operated under the company-level practices above: reviewed code, least-privilege access, and owned end to end.
We are not publishing specific retention or processing claims here until they are documented to the same standard as the rest of this page. If you are evaluating it for sensitive use, ask us and we will walk through exactly how candidate data is handled.
We will not claim what we have not built.
Below is the same status table we keep on the company page, the one that decides what we are allowed to say about ourselves.
- Infratrix, cost and security gap detection for AWS
- Resume Parser & Job Finder, standalone product
- Graph-grounded reasoning across real account state
- Review-ready change proposals with a customer-held kill switch
- Observability Platform, cloud-resident BYOC with agentic AI
- Infratrix on GCP, in parallel with AWS
- Cross-cloud reasoning beyond a single provider
- Compliance certifications (SOC 2, ISO 27001, HIPAA)
- Named customer logos, case studies, or testimonials
- Guaranteed savings percentages or dollar amounts
- Fully autonomous production remediation
Bring your security team. We’ll walk the model with them.
Thirty minutes on a call, with whoever needs to sign off. We answer in plain language and ship the IAM template before the second meeting.