TOOLS Free security checks for DevOps teams. Preview a Compose deployment before launch. Explore the toolbox

Auto deploy

Preview how your Compose project maps to the cloud.

AWS runs Compose on EC2. Railway maps supported entries into Railway services. Render creates supported Dockerfile services separately. Review the plan and warnings before launching anything.

Start a deployment Deployment history
1. Choose a target
2. Pick the source AWS deployments run from a Git repository so the instance can clone and redeploy the stack. Railway receives separate services from supported Compose entries. This converter does not preserve every Compose option; inspect the warnings in your plan. Render needs a GitHub repository connected to your Render workspace. It creates one service per selected Dockerfile build; Compose networking and shared volumes are not reproduced.
A zip that contains docker-compose.yml and the project files it needs.
Visibility will be checked automatically. Private repositories will ask for a read-only access token.
Choose a branch, or leave the default selected.
3. AWS deployment settings
This prepares the plan; no cloud resources are created yet.

Private repository · read access

Connect your Git provider

This repository isn’t publicly accessible. Enter a read-only source access token so AutoCloudPilot can verify access and load the Compose files for your preview. This token is separate from cloud credentials, which are requested only when you deploy or destroy. It isn’t saved to your account or deployment history.

Use a token scoped to this repository with read access to its contents. A private or inaccessible repository can’t be distinguished from an invalid URL until access is verified.

Preview first · connect at launch

Connect your cloud account

Cloud credentials are only requested when you deploy or destroy. Preview the plan without target-cloud credentials. Credentials are sent only to start this deployment and aren’t saved to your AutoCloudPilot account or deployment history. Use limited-scope or temporary credentials when available. Leave fields empty if the deployment server already has provider credentials configured.

Use a token with access to the workspace where you want to create services. Leave it blank if Railway is configured on the deployment server.

Use the workspace that should own these services, or leave it blank if Render is configured on the deployment server.

Enter both key fields. Use the same AWS account that will own the resources.

For private repository redeploys, this token is stored as an encrypted value in your AWS Parameter Store.

Preview first · connect at launch

Delete the cloud resources behind this deployment?

Cloud credentials are only requested when you deploy or destroy. This permanently removes the resources created in for ; the deployment record remains in history. Credentials are sent only for this cleanup action and aren’t saved to your AutoCloudPilot account or deployment history. Use limited-scope or temporary credentials when available. Leave fields empty if the deployment server has matching credentials configured.

Use the AWS account that owns these resources. Leave fields empty only if the server has matching credentials configured.

Let's get you started

See deployments in action

For a demo, you're one email away. Write to us and we'll show you how AutoCloudPilot can help simplify your cloud deployments.

Email us