Integrations
Read-only connections to what you already run.
Pacia never asks for write access to anything. Every provider is normalised into one model before storage, so an organisation running three different code hosts still gets one comparable set of numbers.
Code and issue providers
GitHub Code
One-click GitHub App with live webhooks, or a read-only access token.
GitLab Code
Read-only personal access token. No app registration needed.
Azure DevOps Code
Code (Read) personal access token. No app registration needed.
Bitbucket Code
Read-only access for repositories and pull requests.
Jira Issues
Sprints, epics, QA stages and defect flow — mapped to your site’s own vocabulary.
How credentials are handled
Read-only scopes throughout
Pull requests (read), Metadata (read) and Members (read) on GitHub; read_api on GitLab; Code (Read) on Azure DevOps; a read-only Jira token.
Encrypted at rest
Every access token is AES-256-GCM encrypted in a dedicated credentials table and is never included in any API response.
Never file contents
Pacia reads pull request metadata — timings, reviews, sizes, checks — not your source code.
Nothing is written back
No integration writes to your repositories, your Jira board or your CI. Connecting Pacia changes nothing in your systems.