Available on AWS Marketplace
ECS clusters in your AWS account, without the DevOps backlog.
Describe an environment once. Torquer turns it into VPC, load balancer, ECS services, database, CI/CD and HTTPS domains, inside your account, with a plan review before anything changes.
-day free trial · Billed on your AWS invoice · Runs in your account
configSpec acme-api-prod.json account 123456789012 · eu-west-1 ✓ VerifyAccess bootstrap v1.13 · OK ✓ TerraformPlan +42 add · 0 change · 0 destroy ✓ PlanGate add-only · auto-approved ✓ TerraformApply vpc · alb · ecs · rds · acm ✓ RolloutEcs api · worker · 2/2 healthy ✓ CicdPipelines api · worker endpoint https://api.acme.example elapsed 11m 48s
- Procured through AWS Marketplace
- Counts toward your AWS commitment
- Infrastructure stays in your account
- Every action audited in CloudTrail
Why teams switch
Repeatable environments, not hand-built ones.
Every new ECS environment should take minutes, be reviewed before it changes, and be visible in one place. Most teams get none of the three.
Days of setup become one JSON file
The configSpec is the single source of truth. Services, env vars, database, domains and CI/CD are declared once and applied consistently to every environment.
No surprise destroys
Every change goes through plan, analysis and a gate. Add-only plans proceed. Anything that deletes or replaces a resource waits for your approval.
One console for every cluster
Jobs, pipelines, logs, service health and parameters for all your environments, with your team's actions recorded by email.
From subscribe to first cluster
Three steps. No tickets, no manual IAM.
Torquer uses AWS Marketplace Quick Launch, so the connection to your account is created by a CloudFormation stack you review and launch yourself.
Subscribe on AWS Marketplace
Accept the offer with your AWS account. Billing goes on your AWS invoice. No credit card, no vendor onboarding forms.
Quick Launch connects your account
From the Marketplace page, launch the provided CloudFormation stack. It creates the TorquerProvisionerRole with an external ID and a management-events trail. Nothing else is touched.
Describe and provision
Sign in to your Torquer console, paste or build your first configSpec, run CREATE. Your cluster, pipelines and HTTPS endpoint are ready in minutes.
The stack and your sign-in link are also in the email you receive after subscribing.
Included
Everything a production ECS environment needs.
Networking and compute
VPC, subnets, NAT, ALB and an ECS cluster on EC2 capacity, sized from the configSpec.
Data services
RDS PostgreSQL with an application user created for you, DynamoDB tables, S3 buckets, EFS volumes, Cognito user pools.
CI/CD per service
CodePipeline and CodeBuild in your account: build from GitHub, push to ECR, deploy to ECS. Tag-based releases when you need control.
Domains and HTTPS
Route 53 records and ACM certificates for your custom hostnames, attached to the load balancer.
Operations
Service logs, compute status, parameter updates, rollouts and 12-hour remote access to cluster hosts, all audited.
MCP server for AI agents
Operate every cluster from Claude, Cursor or any MCP client. Same permissions, same audit trail, same plan gate.
Pricing
One price per managed cluster.
No seats, no tiers to decode. You pay for the environments Torquer operates, on your AWS invoice. AWS resources in your account are billed by AWS as usual.
- Unlimited users and AWS accounts
- All modules: networking, ECS, RDS, CI/CD, domains, Cognito
- Web console and MCP server
- Email support, business hours
- -day free trial, cancel from the AWS console
Billed monthly by AWS. A destroyed cluster stops counting at the end of the month.
- Volume pricing for 10+ clusters
- Dedicated Torquer instance
- Support SLA and onboarding session
- Delivered as an AWS Marketplace private offer
FAQ
Short answers.
Where does my infrastructure run?
In your AWS account and region. Torquer only holds the control plane. Resources are named and tagged per cluster, with ManagedBy=torquer, so you can see exactly what it created.
What access does Torquer get?
A single IAM role, created by the Quick Launch CloudFormation stack, trusted with an external ID unique to you. You can review the template before launching and remove the stack at any time, which revokes access immediately.
Can Torquer delete something by mistake?
Any plan that deletes or replaces a resource stops and waits for an explicit approval for up to 7 days. Destroying a cluster always requires approval.
What counts as a managed cluster?
One environment of one application: for example acme-api-prod. It can contain any number of services, databases and pipelines. Staging and production are two clusters.
Do I still pay AWS for the resources?
Yes. EC2, RDS, NAT and the other resources Torquer creates appear on your AWS bill as usual. Torquer's fee is the only line added by the Marketplace subscription.
How do I cancel?
Unsubscribe from the AWS Marketplace console. Your clusters keep running: they are your resources. Delete the CloudFormation stack to revoke Torquer's role.
Launch your first cluster today.
Subscribe, run Quick Launch, provision. Your first environment is live before the next stand-up.