KERN SECURITY

Your work stays
with you.

Kern organises access to your tools without becoming the host of your code, your repositories or your accounts.

Technical documentation
OUR PRINCIPLES

A clear boundary between every system.

The desktop app, the website and external platforms only receive what they strictly need.

01

Local code

Folders stay on your computer. The contents of your files never go through kern.salks.me.

02

Native secrets

Final tokens are kept in your system’s credential manager.

03

Ephemeral gateway

OAuth tickets are encrypted, expire after ten minutes and are deleted as soon as they are used.

OAUTH FLOW

The gateway keeps nothing.

It protects the app secrets during authorisation, then hands a single-use ticket to the desktop app.

  • Security state verified
  • PKCE proof required
  • Ticket usable only once
  • Deleted after use
Kern DesktopCreates the PKCE proof
1Authorisation →
kern.salks.meEncrypted ticket · 10 min
2Exchange →
GitHub / TrelloOfficial OAuth

Source code never enters this flow.

WHAT WE DON’T DO

No grey area.

No Kern accountGitHub remains your main identity.No copy of your repositoriesYour code stays local or on your Git host.No long-lived token on the siteThe gateway hands over, then forgets.No forced telemetryEvery option stays explicit.