Overview
YumaOS gives one organisation a dedicated Next.js application and a Hermes sidecar that talk over localhost. Agents can draft work. Destructive actions queue for a human who holds agents.approve. There is no environment variable that turns that gate off.
The listing images are only those two containers. PostgreSQL and Redis are not shipped as images: the stack creates RDS PostgreSQL 16 (pgvector on migrate) and ElastiCache Redis with TLS in the buyer account, plus a two-AZ VPC, an Application Load Balancer, one Fargate task with YumaOS and Hermes on the same ENI, KMS, Secrets Manager, an uploads bucket, a vault bucket, a Hermes snapshot bucket, and encrypted EFS for the live Hermes home. Amazon Bedrock is pinned to Australian Haiku (au.anthropic.claude-haiku-4-5-20251001-v1:0) in ap-southeast-2.
You subscribe on AWS Marketplace, then launch from https://github.com/yumaitau/YumaOS-aws-deploy with CloudFormation or Terraform on ECS Fargate, or the Helm chart on Amazon EKS. The docker pull snippet AWS shows only proves the subscription can pull the images. It does not create the stack.
The YumaOS web image requires a current AWS Marketplace contract entitlement. It consumes one standard_deployment seat at start and revalidates every 15 minutes with AWS::Marketplace::Usage so the heartbeat does not consume another unit. Hermes is a public sidecar and is not license-gated. Copying the web image, changing environment variables, or cancelling the subscription does not keep YumaOS usable. Product identity is baked at image build; stack parameters cannot disable or retarget that check.
First visitor registers. Then lock public signup if you want. Support: https://os.yumait.com.au/contact
Highlights
- Buyer-owned VPC, RDS, Redis, S3, EFS, and KMS. The publisher does not host your data.
- YumaOS and Hermes share one Fargate task and talk on 127.0.0.1. Destructive agent actions wait for human approval; the gate has no off switch.
- Launch with Terraform, CloudFormation, or Helm from https://github.com/yumaitau/YumaOS-aws-deploy. One task or one pod only (MaxCount=1).
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
- Monthly subscription
- $0.001/month
Vendor refund policy
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
YumaOS 1.0.3 on ECS Fargate and Amazon EKS
- Amazon ECS
- Amazon EKS
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
Gated multi-arch listing (linux/amd64 and linux/arm64) of YumaOS web plus Hermes. Web consumes one standard_deployment seat at start and revalidates with AWS::Marketplace::Usage. Launch from https://github.com/yumaitau/YumaOS-aws-deploy . Do not use 1.0.0, 1.0.1, or 1.0.2.
Additional details
Usage instructions
- Subscribe to YumaOS on AWS Marketplace. Wait until the subscription is active before you pull images or create a stack.
- Open https://github.com/yumaitau/YumaOS-aws-deploy . Use CloudFormation (cloudformation/yumaos-fargate.yaml) or Terraform (terraform/) for ECS Fargate. For Amazon EKS use charts/yumaos with values-aws-marketplace.yaml after you provision RDS, Redis, S3, and an IRSA / Pod Identity role.
- Create the stack in ap-southeast-2. Australian Bedrock Haiku is not available as this listing's default in other Regions.
- Pin both listing images from Marketplace ECR (web + Hermes) to tag 1.0.3. Do not use :latest. Do not use 1.0.0 or 1.0.1 (no license gate) or 1.0.2 (arm64-only). Set Cpu architecture to X86_64 or ARM64 (Graviton). Postgres is the RDS instance this stack creates, not a third image.
709825985650.dkr.ecr.us-east-1.amazonaws.com/yuma-it/yumaos-aws:1.0.3 709825985650.dkr.ecr.us-east-1.amazonaws.com/yuma-it/yumaos-hermes:1.0.3
- The published YumaOS web image consumes one contract seat at start (CheckoutLicense PROVISIONAL, dimension standard_deployment, Count=1) and revalidates every 15 minutes with AWS::Marketplace::Usage (Unit=None). Hermes is not license-gated. Task-definition environment variables cannot disable the web check. Product identity is baked into the web image at build.
- Set AllowedIngressCidr / allowed_ingress_cidrs to your office, VPN, or client CIDR. Leave AllowInternetIngress false. 0.0.0.0/0 is rejected unless that flag is true.
- Enable Bedrock in the buyer account before the first chat. Open Amazon Bedrock in ap-southeast-2, request Claude Haiku 4.5, and confirm au.anthropic.claude-haiku-4-5-20251001-v1:0. The task role may invoke only au.anthropic.* profiles.
- Create the stack. Keep one web+Hermes task (WebDesiredCount / web_desired_count / Helm replicaCount = 1). MaxCount=1. Leave deployment rollback off on first create. ECS health checks use node and python3. On EKS, attach iam-policy.json and set AWS_REGION.
- Open the ApplicationUrl output. Register the first administrator. Then set AUTH_DISABLE_SIGNUP=true if you want to lock public registration.
- Health: GET /livez (process) and GET /readyz (database). Hermes health is http://127.0.0.1:8642/health inside the task only.
Do not change HERMES_URL=http://127.0.0.1:8642 , HERMES_DASHBOARD_URL=http://127.0.0.1:9119 , or HERMES_YUMAOS_MCP_URL=http://127.0.0.1:3000/api/hermes/mcp .
Marketplace contract: USD 600 per month for one standard_deployment. You also pay AWS directly for Fargate, ALB, NAT, RDS, ElastiCache, S3, EFS, KMS, Secrets Manager, CloudWatch, Bedrock tokens, and optional WAF/Backup.
Resources
Vendor resources
Support
Vendor support
Yuma IT Pty Ltd (ABN 62 684 389 839). Contact: hello@yumait.com.au . Product information: https://os.yumait.com.au/ . Support: https://os.yumait.com.au/contact . You run YumaOS in your AWS account on ECS Fargate or Amazon EKS. Yuma IT does not host your data. Terms: https://os.yumait.com.au/terms . Refund policy:
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.