Let AppArch come to where your team already works.
The Integrations module connects AppArch to the tools your team already uses: deployment platforms, issue trackers, incident sources and the AI provider your installation chooses.
Connecting takes three steps
Every integration follows the same path: you enter the credential, AppArch verifies the connection, the flow starts.
- 01
Connect
You enter a token, a server address or an API key. Credentials are stored encrypted and never reach the browser.
- 02
Verify
The connection is tested before it is saved. A wrong token or an unreachable server surfaces right there, not at the first notification.
- 03
Let it flow
Findings turn into Jira or Trello issues, deployments show up in the catalog, incidents feed the DORA metrics.
What can you connect?
Everything here works today, except the ones marked soon: those are not open yet, and we do not present them as if they worked.
CI pipelines
The analyser runs as one job in your own pipeline: ready-made snippets for four providers, a plain docker run for the rest.
Deployment
Which version runs in which environment is written onto the service catalog.
Observability
With Dynatrace, New Relic or Percona PMM connected, incident records flow in, and DORA's two empty metrics, change failure rate and time to restore, fill from real data. Percona PMM also adds database query times.
Quality and testing
SonarQube measurements and findings sit next to AppArch's own; JMeter test summaries land on the project's performance tests page.
AI
The installation's operator connects one provider; requests go from that account and nothing passes through AppArch.
Issue tracking
Findings open as issues on the board your team already uses. Project mapping is configured per workspace.
Sign-in and notifications
People sign in with their LDAP or Active Directory account; notifications go out by e-mail through your own SMTP server. Slack and Teams channels are on the way.
What does connecting actually change?
An integration is not a feature on its own. It shows up in these three moments.
Tech debt lands on the board
With Jira connected, findings do not wait in a separate tool - they sit as issues on the board the team plans from. Debt you cannot see never gets planned.
Delivery flow, read from the board
With Jira connected, the issue history is read back too: how long work sits in each status shows up in Engineering Analytics without anyone filling in a form.
Which version was out there?
With Argo CD, Flux or Kubernetes connected, the service catalog knows which version went where and when. You look it up instead of guessing.
Git and CI providers
These are not integrations you toggle but the first step of setup: where your code reaches AppArch from. Each one has its own page.
Frequently asked
Where are my credentials stored?
Whose AI key is used?
When do the ones marked soon arrive?
Do integrations work in an on-premise install?
What happens to the data if I remove an integration?
Start with one integration
You do not need to connect them all at once. Pick the channel or board your team looks at most and see the difference within a week.