emp

{
  "aliases": [],
  "alternatives": [],
  "build_dependencies": [
    "go"
  ],
  "categories": [],
  "caveats": null,
  "conflicts_with": [],
  "dependencies": [],
  "deprecated": 0,
  "deprecation_reason": null,
  "desc": "CLI for Empire",
  "disable_reason": null,
  "disabled": 0,
  "enrichment_fetched_at": "2026-06-20T23:37:18+00:00",
  "first_seen": "2026-06-20T23:34:18+00:00",
  "full_name": "emp",
  "github_default_branch": "master",
  "github_last_commit_at": "2023-11-25T17:16:08Z",
  "github_readme_excerpt": "# Empire\n\n[![readthedocs badge](https://readthedocs.org/projects/pip/badge/?version=latest)](http://empire.readthedocs.org/en/latest/)\n[![Circle CI](https://circleci.com/gh/remind101/empire.svg?style=shield)](https://circleci.com/gh/remind101/empire)\n[![Slack Status](https://empire-slack.herokuapp.com/badge.svg)](https://empire-slack.herokuapp.com)\n\n![Empire](empire.png)\n\nEmpire is a control layer on top of [Amazon EC2 Container Service (ECS)][ecs] that provides a Heroku like workflow. It conforms to a subset of the [Heroku Platform API][heroku-api], which means you can use the same tools and processes that you use with Heroku, but with all the power of EC2 and [Docker][docker].\n\nEmpire is targeted at small to medium sized startups that are running a large number of microservices and need more flexibility than what Heroku provides. You can read the original blog post about why we built empire on the [Remind engineering blog](http://engineering.remind.com/introducing-empire/).\n\n## Quickstart\n\n[![Install](https://s3.amazonaws.com/cloudformation-examples/cloudformation-launch-stack.png)](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#cstack=sn%7Eempire%7Cturl%7Ehttps://s3.amazonaws.com/empirepaas/cloudformation.json)\n\nTo use Empire, you\u0027ll need to have an ECS cluster running. See the [quickstart guide][guide] for more information.\n\n## Architecture\n\nEmpire aims to make it trivially easy to deploy a container based microservices architecture, without all of the complexities of managing systems like Mesos or Kubernetes. ECS takes care of much of that work, but Empire attempts to enhance the interface to ECS for deploying and maintaining applications, allowing you to deploy Docker images as easily as:\n\n```console\n$ emp deploy remind101/acme-inc:master\n```\n\n### Heroku API compatibility\n\nEmpire supports a subset of the [Heroku Platform API][heroku-api], which means any tool that uses the Heroku API can probably be used with Empire, if the endpoint is sup",
  "github_repo": "remind101/empire",
  "github_stars": 2677,
  "github_topics": [
    "aws",
    "docker",
    "ecs",
    "paas"
  ],
  "homepage": "https://github.com/remind101/empire",
  "homepage_og_description": null,
  "homepage_og_image": null,
  "homepage_title": null,
  "installs_30d": 10,
  "installs_365d": 74,
  "installs_90d": 11,
  "keg_only": 0,
  "keg_only_reason": null,
  "last_seen": "2026-06-20T23:34:18+00:00",
  "license": "BSD-2-Clause",
  "llm_generated_at": null,
  "llm_model": null,
  "name": "emp",
  "oldnames": [],
  "one_liner": null,
  "optional_dependencies": [],
  "rank_30d": 8615,
  "rank_365d": 10006,
  "rank_90d": 11520,
  "raw_hash": "76386d01bb5ef30c",
  "recommended_dependencies": [],
  "revision": 0,
  "ruby_source_path": "Formula/e/emp.rb",
  "tap": "homebrew/core",
  "test_dependencies": [],
  "uses_from_macos": [],
  "version_head": "HEAD",
  "version_stable": "0.13.0",
  "versioned_formulae": [],
  "why_use_this": null
}