Choose the task
Scan a public website, review an AWS IAM policy, or plan a Compose deployment.
How AutoCloudPilot works
Review first. Then choose what to run.
Use a security tool for a focused assessment, or inspect a Compose deployment plan before cloud resources are created. Your inputs and the provider’s limits stay visible.
A clear workflow
Three steps from question to next action.
Provide only what it needs
The scanners need a URL or policy document. Deployment credentials are requested only when you choose Deploy or Destroy.
Review evidence and limits
Inspect findings, service mappings and warnings before you decide what to do next.
Compose deployment targets
Different providers, different runtime behavior.
The planner translates supported parts of your Compose project. Preview warnings and update your project when provider features differ.
Amazon EC2
Runs Docker Compose on an EC2 virtual machine. The setup provisions the VM, network access, deployment role and HTTPS configuration.
- Use when you need Compose behavior on a server
- Review instance size, region, public ports and domain
- Requires customer AWS credentials and incurs AWS charges
Railway
Compose services are mapped to Railway services. Railway does not run the Compose file as the production orchestrator, and the current converter supports a subset of options.
- Review the plan for each service and variable
- Check storage, networking and startup dependencies
- Requires a Railway token and workspace
Render
Supported Dockerfile builds become separate Render services. The current integration does not recreate Compose networking, shared volumes or every service type.
- Connect a GitHub repo to the Render workspace
- Review each service and any skipped setting
- Requires a Render API key and owner/workspace ID
Credential handling
Credentials are for the action you choose.
Preview needs no target-cloud credentials. Deploy and destroy ask for the selected provider’s credentials for that request; AutoCloudPilot does not save them to your account or deployment history. Use limited-scope credentials where possible.
Hosting requirement
Deployment work needs an always-on worker.
The marketing and preview pages can run on Vercel. Real provisioning runs in a background worker and needs a long-running host; serverless functions may pause before the job finishes. Check your production worker setup before launching customer deployments.