# pulp_ansible vs galaxy_ng

Here is some content that distinguishes the intent and features of pulp_ansible and galaxy_ng.

The high level summary is that galaxy_ng provides a UI and set of workflows on top of pulp_ansible, which only provides UIs.

## pulp_ansible

* supports both role and collection content
* Can sync from galaxy.ansible.com and cloud.redhat.com, and other pulp_ansible or galaxy_ng installations
* Can serve both role and collection content to the `ansible-galaxy` CLI
* Can receive both uploaded role and collection content from the `ansible-galaxy` CLI
* Does *not* support any kind of specific workflow, it's just repositories, remotes, sync, and upload operations

## galaxy_ng

* galaxy_ng comes with a UI
* uses pulp_ansible as a dependency
* provides role based access control (next release)
* provides a specific workflow for bringing content in and then promoting it to one or more repositories.
* [bmbouter] we could use more detail on this workflow