Core concepts
The core concepts you’ll encounter when using AppArch:
Workspace
Section titled “Workspace”The tenant boundary. A company creates a workspace and invites users into it. Projects, credentials, and module settings all belong to the workspace.
Project
Section titled “Project”A repository registered to a workspace. Each project receives a project-specific token that the runner uses for authentication.
Module
Section titled “Module”A feature unit enabled by your package: ArchPilot (PR/MR comment bot), ArchScan (quality report), ArchSecurity (SAST), ADR (decision records), Compliance.
Integration
Section titled “Integration”The Git credential used to register projects (GitHub, GitLab including self-managed, Bitbucket Cloud, Azure DevOps Services), along with the workspace’s other connections such as Jira, Trello, SonarQube or Slack. See Integrations overview.
Runner
Section titled “Runner”A language-specific analyzer image (.NET, Java, Python, Go, TypeScript, Ruby, PHP, Kotlin, Swift) that runs in the customer’s CI pipeline. It analyzes the code in place and sends only the results to the Report API.
Report / Run
Section titled “Report / Run”The analyzer output for a project. It is retrieved through the Report API and contains findings, metrics, and scores.
Licence
Section titled “Licence”The installation’s signed licence. It defines the limits (workspaces, users, projects, monthly module usage) and which modules are enabled (see Licence and limits).