Security by design, not by promise.
No external backend. Your app data, credentials, and browser sessions never leave your machine. Only the result and screenshots return to Jira.
Four guarantees, built into the architecture.
Ed25519-signed pairing
Your desktop app and Jira establish trust with a public-key signed handshake. No shared secret ever travels over the wire, and only a device you explicitly pair can receive jobs.
OS-keychain secrets
Test credentials are stored in your macOS keychain — write-only. They’re resolved into {{secrets.NAME}} at run time, in memory, on your machine, and are never uploaded or read back.
Per-job JWT
Every run is authorized by a short-lived JSON Web Token scoped to that single job. There are no long-lived API keys sitting on your machine waiting to be exfiltrated.
Data sovereignty
Execution happens on hardware you control, on your network, with your logins. The Forge manifest declares no external fetch and no remote hosts — so there’s literally no path to a third-party cloud, and no AppDash backend to trust.
Where your data goes (and doesn’t).
The test definition leaves Jira. Everything sensitive stays on your machine. Only the verdict and screenshots come back.
Jira
Sends the test definition only. Receives the result.
Your Desktop
Holds secrets and sessions locally. Orchestrates the run.
AI Agent + Browser
Runs against your real, in-network environment.
Proof, not just claims.
For the security reviewer who has to sign off: here’s where secrets actually live.
What’s stored, and where
Secret values live in your macOS keychain, write-only. The app never sees them. They’re resolved in memory at run time to fill {{secrets.NAME}} references, then discarded.
What we send to Jira
A structured result comment: the verdict, duration, per-step outcomes, and screenshots. Secret values are scrubbed from output before anything posts back.
The five scopes
The app requests five least-privilege Atlassian scopes — read and write Jira work, app storage, your Jira user record, and GDPR personal-data reporting. Enough to read the issue, post the result, and store the test — nothing broader, and you can audit every one in the manifest.
Compliance roadmap (the honest version)
We’re early, and we’d rather tell you what’s real than over-claim. The architecture is the strongest control we have today — there’s no external backend to breach. Formal programs like Cloud Fortified are on the roadmap, not done yet. If your review needs a specific artifact, ask us — we’ll tell you straight where it stands.
Forward this to your security reviewer.
Everything here is self-serve and linkable. When they’re satisfied, install VibeTest free on the Atlassian Marketplace.