aws-org-instance-pattern-ec2-docker-triggerdev
Runwal Group AWS org instance uses EC2 (m6i.2xlarge, 8vCPU/32GB/gp3 SSD) + Ubuntu 24.04 + Docker, with Nginx as edge proxy and Traefik v3 for internal container routing — same pattern as the Hostinger VPS. Trigger.dev is self-hosted on this instance as the agent orchestration layer. The principle is ‘replicate the Hostinger pattern, not the Hostinger content’ — clean slate purpose-built for SaaS apps and autonomous agents.
Related
- aws-ec2-docker-pattern-mirrors-hostinger-for-org-deployments
- docker
- hybrid-triggerdev-cloud-fargate-over-pure-self-hosted-decisi
- aws-zero-maintenance-stack-for-saas-agent-platform
- cache
- aws-org-platform-mirrors-hostinger-pattern-not-content
- temporal-preferred-over-trigger-dev-for-durable-agent-orches
- trigger-dev-self-hosted-criu-checkpointing-unavailable
- hostinger-nginx-traefik-docker-pattern-portable-to-aws-ec2
- temporal-beats-triggerdev-for-self-hosted-agent-orchestratio
- hostinger-pattern-replicated-to-aws-ec2-stack
- aws-agent-platform-architecture-for-claude-code-ops-model
- x-developer-portal-signup-use-arjtech-not-runwal