remind101/empire

Health v2 · maintenance only

Adoption not part of the score

2675 stars · 155 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Empire is a Platform-as-a-Service (PaaS) control layer built on top of Amazon EC2 Container Service (ECS) that provides a Heroku-like workflow for deploying Docker containers. It implements a subset of the Heroku Platform API so existing Heroku tooling can manage containerized microservices on AWS.

Use cases

• deploy docker containers to aws ecs with a heroku-like workflow
• self-host a paas for microservices on aws
• use heroku cli tools like hk or emp against my own infrastructure
• run many microservices without managing kubernetes or mesos
• get automatic internal load balancing and dns-based service discovery on ecs
• migrate heroku-style deployment processes to ec2 container service

When to choose

• you run small-to-medium scale microservices on AWS ECS and want simple Heroku-style deploys
• you want Heroku Platform API compatibility on your own AWS infrastructure
• you prefer ECS over the complexity of Kubernetes or Mesos
• you need internal ELB routing and Route53 DNS service discovery for containerized apps

When to avoid

• you are not on AWS or not using ECS
• you want a modern, actively developed PaaS - the project has seen little activity since 2023
• you need full Kubernetes ecosystem features or portability across clouds
• you need a fully Heroku-compatible API - only a subset of endpoints is supported

Facets

service · maturity maintenance

deployment container-orchestration api-framework cli microservices cloud-computing microservices self-hosted cloud go self-hosted paas ecs heroku-compatible aws docker-deployment devops containers docker linux

Member repositories

For agents

markdown · JSON · MCP: product_card(name="remind101/empire")