Zero-Trust Architecture.
Tyne operates in your local machine. Your code never leaves your ecosystem without your explicit permission.
[ LOCAL-FIRST EXECUTION ]
Tyne's core engine runs entirely within your local VS Code node environment. Guardrail linting, Git staging, and branch management happen locally.
[ GRANULAR GITHUB PERMISSIONS ]
Tyne uses the modern GitHub App protocol. It only asks for Read & Write access to your Code and Pull Requests. It has absolutely zero access to your organization’s billing, team settings, or account management.
[ NO TRAINING ON YOUR CODE ]
We do not use your code to train AI models. We do not record keystrokes. We do collect operational telemetry — feature usage counts, validation run counts, timestamps, and error diagnostics — to enforce plan limits and fix bugs. That list is exhaustive and documented in our Privacy Policy.
[ THE BYOK PROTOCOL ]
Bring Your Own Key. In BYOK mode your requests go directly from your local machine to your chosen provider, and Tyne servers never receive your code. In managed mode, the specific diff under review is sent to Tyne's review service so it can be analysed, then discarded after the report is generated. You choose the mode.
[ WHAT LEAVES YOUR MACHINE ]
In managed mode Tyne sends only the diff boundary under review and the linked ticket text — never your full repository, never files outside the diff, never your git history. Secrets detected during scanning are redacted before transmission.