Integrations overview
How Jira, Linear, and GitHub Issues connect on Free vs Pro, and what stays on your machine versus in your online account.
What you connect
- Jira (Atlassian) on Free: connect with your site URL, Atlassian account email, and an API token you create in Atlassian.
- Jira on Pro: one-tap sign-in with Atlassian (the same style of secure browser sign-in many apps use).
- Linear on Free: connect with a Linear API key from your Linear account.
- Linear on Pro: one-tap sign-in with Linear.
- GitHub Issues on Free: connect a repository with owner, repo name, and a personal access token that can read issues.
- GitHub Issues on Pro: one-tap sign-in with GitHub, with the same manual token path still available if you prefer it.
How sign-in works (high level)
- On Free you paste credentials or tokens in the desktop app. On Pro you can start sign-in from the app.
- The browser may open briefly so you can approve access with your provider.
- Sensitive steps run on our servers so vendor secrets never ship inside the web page. Think of it as the same pattern as "Sign in with Google" on other products.
- After approval, the desktop app holds the connection and keeps issue data local-first.
Where your data lives and what the portal stores
- Issues you triage in Mach Triage stay in a local database on your computer, not on our servers.
- Local-only workspaces never talk to Jira, Linear, or GitHub until you choose to connect.
- This website stores basic account details: email, whether you are signed in, and whether you are on Free or Pro so downloads and upgrades line up with the right person.
- Payments run through Stripe; your card details stay with Stripe.
Provider references
Official guides if you configure tokens or OAuth apps yourself.