build edition · integrations

Your real backlog ↔ AI context.
Bidirectional.

AI agents that don't read your Jira or Linear are guessing at requirements. fastpace pulls the real story body, comments, and linked context into the agent — and pushes the agent's work back to the issue, so traceability survives the loop.

Jira

Atlassian Cloud + Server

Pull → context: Stories pulled into AI context. Description, acceptance criteria, comments, linked PRs, parent epic — all on hand when the agent picks up the story.
Push → backlog: AI commit IDs auto-comment back on the issue with a one-line summary. Status transitions when the linked PR merges.
Setup: OAuth via Atlassian Connect, or a personal API token for solo. Per-project or per-instance scope.

Linear

GraphQL native

Pull → context: Issues by team or project. Status, priority, labels, attachments, parent project — pulled as L3 context.
Push → backlog: AI commits attach directly to the issue. PR-merge → issue-status transitions configurable per team.
Setup: OAuth or workspace API key. Linear-native because the GraphQL API is good.

Confluence

Atlassian docs

Pull → context: Pages cached locally as L2 context — architecture diagrams, glossaries, runbooks. Updated on-demand or on a schedule.
Push → backlog: Generated PRDs and ADRs can be exported back to Confluence (optional). Most teams keep them in-repo.
Setup: Same OAuth as Jira. Per-space access.

Google Docs

Drive + Docs API

Pull → context: PRDs and design docs already in Google Docs become L3 context without copy-paste. Body cache local-only and gitignored.
Push → backlog: New PRDs / ADRs created in fastpace can sync to Drive (off by default).
Setup: OAuth via Google Workspace. Per-folder scope.

GitHub

PRs + Actions

Pull → context: PR comments, review comments, CI status, branch context — all available to the agent during reviews and refactors.
Push → backlog: Provenance trailers on every commit. PR descriptions generated from run manifests + linked tickets. Audit-gate workflow ships with the package.
Setup: GitHub App (org-level install) or fine-grained PAT. Pre-built actions in packages/fp/assets/ci/github-actions/.

GitLab

Merge requests + pipelines

Pull → context: MR description + discussions + pipeline status. Same model as GitHub — different host.
Push → backlog: Same provenance pipeline. MR descriptions generated from manifest + ticket.
Setup: Project access token. Self-hosted GitLab supported.

Bitbucket

Atlassian source

Pull → context: PR + pipeline context. Reuses the Atlassian OAuth surface from Jira/Confluence.
Push → backlog: Provenance trailers. PR descriptions.
Setup: OAuth via Atlassian Connect.

Slack / PagerDuty / SIEM

Webhooks bus

Pull → context: —
Push → backlog: F3.10 webhook bus emits events on AI activity, audit-chain breaks, fleet maturity drops, evidence-request transitions. Subscribe from Slack / PagerDuty / your SIEM.
Setup: Configure FLEET_WEBHOOK_URLS env on the org-dashboard. One webhook URL per subscriber.

One install, every integration.

Backlog sync ships in Team tier and up. Webhook bus and audit replication are Org tier features.

See pricing How it works →