Security toolbox | AutoCloudPilot

Available now

Three workflows you can use today.

Live · no account

Website security scanner

Passive website checks with a score and findings grouped by severity.

Checks: TLS, headers, cookies, forms, DNS/email, CORS, WAF and public exposure.
Prepare: A public URL for a site you own or have permission to assess.
Steps: Enter URL → confirm authorization → run scan → review evidence and recommendations.
Data: Runs in memory; scan results are not saved.

Open website scanner

Live · no AWS credentials

AWS IAM policy analyzer

Static review of a policy document for risky permissions and escalation patterns.

Checks: Wildcards, sensitive actions, trust policies, conditions and privilege escalation.
Prepare: Paste JSON or upload a policy file up to 512 KB.
Steps: Provide policy → confirm authorization → analyze → inspect findings and locations.
Data: Analysis runs in memory; no AWS API calls are made.

Open IAM analyzer

Live · deployment requires sign-in

Compose deployment planner

Review a provider-specific plan before resources are created. It does not treat every provider as a Compose runtime.

Prepare: Git repository or ZIP containing your Compose file and project files.
Steps: Choose target → inspect mapped services and warnings → enter target credentials at launch.
Credential handling: Credentials are requested for deploy or destroy and are not saved to your account or history.
Important: Use the provider notes below to check which Compose features carry over.

Open deployment planner

Compose support

Check the deployment model before choosing a target.

A Compose file is a source format. The target provider decides how services, storage and networking run.

EC2 · runs Docker Compose

The deployment provisions an EC2 instance and starts the stack with Docker Compose. You supply AWS credentials and pay AWS charges directly.

Full Compose stack on one VM
Git source required for deploy and redeploy
Review exposed ports, domain, size and region

Preview on AWS

Railway · maps services

The planner creates separate Railway services from supported Compose entries. It is not a production Compose orchestrator, and this converter does not support every Compose setting.

Review generated service plan and variables
Some volume and dependency behavior may need changes
Use app-level retries for dependent services

Preview on Railway

Render · selected Dockerfiles

The planner creates a separate Render service for each supported Git-backed Dockerfile build. This flow does not recreate Compose networking or shared volumes.

GitHub repository connected to Render
Dockerfile required for selected build services
Review skipped settings and service plan

Preview on Render

Planned · not available yet

A security toolbox that can bring findings together.

The direction is inspired by multi-tool workflows like Nubicustos: normalize scan output, prioritize what is exploitable, map controls, and make change over time visible. These integrations are roadmap ideas, not current AutoCloudPilot features.

Cloud posture inputs

Connect cloud audit outputs across AWS, Azure, GCP and Kubernetes with a clear permission review.

Candidate: Prowler · ScoutSuite

Code, image and secret checks

Bring infrastructure-as-code, container and secret findings into one review flow.

Candidate: Checkov · Trivy · Gitleaks

Finding context

Correlate related risks, show possible attack paths, and map findings to selected frameworks.

Planned capability

Scan history and change

Compare runs, track remediation status, and show risk trends without hiding evidence.