Integrations overview
AppArch reaches your code through a credential for your Git platform. Everything else - CI, issue tracking, notifications, AI - is optional and connected separately.
Git platforms
Section titled “Git platforms”Git connections are added under Credentials → Add credential. The wizard has three steps: pick the provider, follow the provider-specific setup, then paste the values.
| Platform | Authentication | Where it can live |
|---|---|---|
| GitHub | Personal access token (fine-grained or classic) | github.com only |
| GitLab | OAuth application or personal access token | gitlab.com or a self-managed GitLab (by URL) |
| Bitbucket | OAuth client or workspace / repository access token | Bitbucket Cloud only |
| Azure DevOps | Personal access token | Azure DevOps Services (dev.azure.com) only |
There is no generic “custom Git” connection. The only self-hosted server AppArch can reach is a self-managed GitLab - see Self-hosted Git.
A pasted token is checked against the provider before it is stored: an invalid or expired token, or one without read access, is refused. Credentials are stored encrypted with the installation’s master key.
The installation operator decides which providers are offered at all (Administration → Settings → Policies (/management/settings/policies)). A closed provider disappears from the wizard and the Api refuses it.
CI systems
Section titled “CI systems”The runner (collector) is a container image that runs inside your own CI. It recognises a pull/merge request from the CI’s own environment variables on:
- GitHub Actions
- GitLab CI
- Bitbucket Pipelines
- Azure Pipelines
Any other CI runs the same image with docker run and passes the PR context explicitly - see Jenkins. Setup for all of them: Add the runner to CI.
Other integrations
Section titled “Other integrations”Connected per workspace under Integrations:
- Jira, Trello - issue tracking for findings (Jira).
- SonarQube - project mapping and measurements next to AppArch’s own.
- Slack, Microsoft Teams - an Incoming Webhook; today AppArch posts only a connection test message there (Slack).
- Kubernetes, Argo CD - deployment state for the Service Catalog (details).
- Dynatrace, New Relic, Percona - incident and performance sources.
- JMeter - load test summaries posted with a project token.
The operator can close any of these for the whole installation under Administration → Settings → Policies (/management/settings/policies).
AI is not a workspace integration: one provider and key for the whole installation, set by the operator. See AI (Claude / OpenAI / Gemini).