# remind101/empire

A PaaS built on top of Amazon EC2 Container Service (ECS)

Repository: https://github.com/remind101/empire
Canonical: https://ross.abutalabs.com/products/remind101-empire
Language: Go
License: BSD-2-Clause
License Family: permissive
Topics: paas, docker, aws, ecs
Last push: 2023-11-25T17:16:08+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 4233, "days_push": 1012, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2675, forks 155 (observed 2026-08-28T04:07:09.729780+00:00)

## What it is
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
- artifact type: service
- maturity: maintenance
- function: deployment, container-orchestration, api-framework, cli, microservices
- domain: cloud-computing, microservices, self-hosted
- platform: cloud, go, self-hosted
- tags: paas, ecs, heroku-compatible, aws, docker-deployment, devops, containers, docker, linux

## Member repositories
- remind101/empire (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:09.729780+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:18:02.925543+00:00, confidence not recorded.
  - readme: https://github.com/remind101/empire (fetched 2026-08-28T04:07:09.729780+00:00, sha 13ddc23fd95d)
- Data as of 2026-08-30T08:39:29.467469+00:00.