Security

Isolated Jobs

Instead of scheduling workloads on a shared, multi-tenant execution platform — whether a CI runner such as GitHub Actions or GitLab CI, or a container orchestrator like Kubernetes — InfraWeave launches each job in its own single-tenant VM via the cloud provider’s serverless-container service (for example, AWS Fargate or Azure Container Instances).

Distroless images

All containers for InfraWeave are built on minimal alpine or distroless images, allowing for small and secure containers.

No credential handling

Regardless of the cloud you use, InfraWeave will use the authentication you’ve provided locally for the clouds SDK, meaning if you run e.g. a command with AWS credentials set in your environment variabels, these will be used.