b-payment-api↻
staging-cluster
develop-4d27c8fActive
Built for AWS ECS
Deploy on AWS ECS.
Without the stress.
A clear console to deploy, monitor and roll back your AWS ECS services on Fargate or EC2. Modern rolling deployments, without Kubernetes.
Private beta access code required · No agent to install
Production deployedIllustrative product preview
⌕ Search services...
LD
staging-cluster
12 services
b-catalog-api↻
staging-cluster
develop-0469dd7Active
b-connect-api↻
staging-cluster
develop-8956d45Active
b-camera-api↻
Production · rollout in progress
release-2.18.0
Rollback availablePrevious revision retained
Built for teams running on
aws Amazon ECS
◆ Fargate
☁ CloudWatch
◎ Amazon ECR
THE PRODUCT
Your team deploys.
Rollout tracks each step.
From a new container image to ECS stability checks, follow deployment progress and keep a rollback target.
1/4
A rollout everyone can understand.
See the active revision, running tasks and deployment events in one place — without navigating multiple AWS screens.
- ✓ Live deployment progress
- ✓ ECS deployment events
- ✓ Task definition revision history
Production rollout LIVE
b-payment-api
FROMrelease-2.17.4
→
TOrelease-2.18.0
Deployment in progress67%
4 healthy 2 starting 3 stopped
✓Task definition registered48 seconds ago
✓New tasks started4 / 6 healthy
Health checks in progress2 tasks remaining
FinalizingWaiting
SETUP
One file to connect AWS.
Then choose what to deploy.
No permanent access keys. No agent in your VPC. A dedicated CloudFormation stack.
awsAccount
Connect your account
A personalized CloudFormation template creates a dedicated IAM role with a unique External ID.
3 clusters18 services2 regions
Automatically discovered
Choose your services
Discover ECS clusters and services in your selected regions, then choose the services to manage.
✓
Ready to deploy
production · eu-west-3
Deploy with visibility
Choose an ECR tag, review the rollout, monitor tasks and confirm a rollback when needed.
SECURITY
Your AWS stays
your AWS.
Rollout uses temporary STS sessions, without storing permanent AWS credentials. Observer is read-only; Operator can update services and pass task roles across the connected account.
Explore the security model →
01Cross-account IAM roleRevoke access from AWS↗
02Explicit access levelsRead-only or account-wide operations↗
03Unique External IDDedicated connection identity↗
04Operation audit trailWho deployed what, where and when↗
PRIVATE BETA
Built with our
first users.
Access requires a beta code while we validate the product. Paid subscriptions are not available yet.
Private MVP
The core features currently available to beta users.
Enter my code →- ✓ ECS cluster and service discovery
- ✓ ECR images, including cross-account registries
- ✓ ECS rolling deployments and rollbacks
- ✓ CloudWatch logs, audit and notifications
Real-world feedback
A private phase to test the product on real ECS environments.
Open the application →- ✓ Access protected by a beta code
- ✓ AWS access through temporary role sessions
- ✓ No permanent AWS credentials stored
- ✓ Shaped by user feedback
After the beta
These features are planned, but are not available yet.
Explore the product →- · Billing and paid plans
- · Invitations, MFA and SSO
- · Canary and blue/green strategies
- · External notification integrations
FAQ
Your questions about ECS Rollout
Which ECS services are supported?
ECS Rollout supports ECS services on Fargate, Fargate Spot and EC2, including capacity providers. Deployments use rolling updates; canary and blue/green strategies are not available yet.
How do I connect my AWS account?
Download your personalized CloudFormation file, create the stack in your account and verify the role in ECS Rollout. Choose the regions and services to manage. No agent or permanent AWS access key is required.
What does Operator access allow?
Observer provides read access. Operator can register revisions, update services across the account and pass its task roles to ECS. Selecting services in the UI does not restrict the IAM scope of the role.
Can my ECR registry live in another account?
Yes. Connect the shared ECR account with read-only access, or use a compatible repository policy. The task execution role still needs its own AWS permissions to pull images.
What happens if a deployment fails?
The engine attempts automatic rollback after a failure following a service update. Ambiguous outcomes may require operator intervention; application availability is not guaranteed.
Your next deployment
could be your simplest yet.
Connect AWS, choose a service and follow your next rollout.
Connect my AWS account → Private beta · Access code required · No paid plans available