Connectors allow Acrity to work with code providers that should not be accessed directly by the Acrity cloud.
Use Console > Connectors to create a connector, generate installation secrets, download deployment artifacts, track liveness, and associate repositories.
Connectors require a Workspace admin (platform admins also have access). Roles are fixed capability sets defined by Acrity, so no other role can create, edit, or revalidate a connector.
When to use
Use connectors when:
- the VCS is on a private network;
- the provider is self-hosted;
- VCS access must originate from a network controlled by the organization;
- internal policies prevent VCS tokens from being stored in external services;
- you need to go through a corporate proxy or private CA.
For SaaS providers with official installation, evaluate Console > Connected Apps first.
How it works at a high level
- A Workspace admin creates the connector in the Console.
- The Console displays installation secrets once.
- The team installs the local component in the organization’s environment.
- The connector opens an egress-only outbound connection to Acrity and reaches the private VCS locally.
- Repositories can then be discovered and associated through the Console.
The Acrity cloud holds no VCS credentials. Only the local connector, running inside your network, holds the credentials for your private VCS. The connector opens an egress-only, secure outbound connection to Acrity, so you do not need to open any inbound ports in your network.
Security, retention, and data handling details are in Security > Data handling and Security > Credentials and tokens.
Create a connector
Open connectors
Go to Console > Connectors.
Start wizard
Choose to create a new connector.
Enter data
Fill in name, provider, and instance base URL when applicable.
Generate secrets
Generate the connector token and relay secret when prompted.
Store values
Copy and store the values in a secure vault. They are shown only once.
Download artifact
Download the installation format compatible with the organization’s environment.
Install and validate
Install the connector, wait for the heartbeat, and run Revalidate when available.
Main fields
| Field | Purpose |
|---|
| Name | Identifies the connector in the Console. |
| Provider | Defines the VCS or integration type served by the connector. |
| Instance base URL | Address of the self-hosted installation or organization when required. |
| Connector token | Secret used by the local component to identify itself. Shown once. |
| Relay secret | Secret used to secure the connector’s outbound connection to Acrity. Shown once. |
| Deploy format | Package or manifest used to install the connector in the local environment. |
Health states
The Console shows a health state for each connector, based on the heartbeat and the most recent Revalidate.
| State | Meaning |
|---|
| Connected | The connector is communicating normally and reaching the VCS. |
| Degraded | The connector responds, but with a limitation or partial failure (for example, slow responses or a subset of repositories unreachable). |
| Offline | Acrity has not received recent communication from the connector. |
| Error | There is a failure that requires configuration, network, or local credential correction. |
Download installation artifact
After creating the connector:
- Go to
Console > Connectors.
- Open the connector.
- Choose the deploy format supported by your infrastructure.
- Download the artifact.
- Deliver the package to the team responsible for local installation.
Do not publish artifacts with secrets in shared repositories. Treat configuration files as sensitive material.
Associate repositories
When the connector is online:
- Go to
Console > Repositories > Connect repository.
- Choose the connector as the VCS access source.
- Select or enter the target repositories.
- Complete branch, PM, and review settings.
- Save and validate the repository status.
Rotate secrets
Rotate secrets when:
- someone with access to the secret left the team;
- exposure is suspected;
- internal policy requires periodic rotation;
- the local environment was recreated;
- the connector will move to different infrastructure.
After generating new secrets, update the local installation and run Revalidate to confirm the connector returned to the connected state.
Common issues
| Symptom | What to check |
|---|
| Connector offline | Check local installation, network, proxy, DNS, firewall, and configured secret. |
| Revalidation fails | Confirm base URL, local credentials, and connector access to the VCS. |
| Repositories do not appear | Check VCS permissions, connector scope, and list refresh. |
| I lost the displayed token | Generate a new token and update the local installation. |
| Certificate error | Confirm corporate CA and TLS configuration in the local environment. |
Best practices
- Install connectors in infrastructure administered by the organization.
- Store secrets in a secure vault.
- Use service accounts with minimum scope.
- Monitor the heartbeat and Console alerts.
- Revoke unused connectors.
- Document internally who operates each connector.
