Share this page

# Architecture overview

The PulseUno environment consists of the PulseUno server, Git server, Vault server, and agents. The following table provides an overview of the PulseUno components.

To manage licenses, PulseUno uses the AutoPass License Server (APLS). For details, see PulseUno licensing.

Component | Description
--- | ---
PulseUno server | This is the central module of a PulseUno environment that: Contains the PulseUno web application. Stores the PulseUno configuration data. Provides access to the database. For details about server configuration, see Configuration settings.
Vault server | This server provides a secure storage for packages, or collections of software components, such as binaries, artifacts, and metadata. Vault packages can be used in builds and continuous integration pipelines. The Vault server supports the following package managers: Maven Docker npm Python PIP Vaults enable you to maintain your own and third-party packages with the help of audit trails, license and security issue detection, reviews, and approvals. For details, see Use vaults to manage artifacts.
Git server | This is the server for Git repositories that supports standard Git-based functionality, such as creating and cloning Git repositories, collaborating on projects with individuals and teams, committing, reviewing, and merging changes. For details, see Create Git repositories.
PulseUno agents | These are small applications associated with the PulseUno server and used for running chains. To increase the capacity of your system, you add more agents. For details, see Agent architecture.

The PulseUno components can be installed on the same system or on different machines.

See also:

- Install PulseUno
- PulseUno licensing

https://admhelp.microfocus.com PulseUno 8942
Tips to improve your search results... PulseUno Help Center PulseUno Help 24.2 - 25.2 All View Local Help Center View Online Help Center Version: