Public
Public repositories
For open-source projects, public documentation, SDKs, examples, and release notes.
- open source
- docs
- examples
Zero-knowledge Git hosting
Git hosting with zero-knowledge protection when your work needs it.
Skron gives teams familiar repositories, pull requests, issues, and rooms. For sensitive projects, secret repositories add zero-knowledge end-to-end encryption without turning the product into a separate security tool.
Public and private repositories stay simple for compatibility. Secret repositories unlock protected content on approved devices, with an experimental post-quantum profile under review for key sharing and trust changes.
- Repository visibility
- 3
- Public, private, secret
- Protected content
- Local
- Unlocked on approved devices
- Post-quantum work
- Hybrid
- Experimental profile in review
comstud / skron-core
Repository workspace
Dmytro committed 8 minutes ago4f8a2c1
crates/skron-gitGit-compatible engine
docs/architectureRepository notes
README.mdProject overview
Unlocked here
This device can read protected repository content.
PR #128
Access model update needs two reviews.
Review room
Three unread messages linked to this change.
Vault grant
Signing key access waits for approval.
Choose repository visibility per project.
A Skron repository is either public, private, or secret. Secret mode is the zero-knowledge option: the repository keeps the normal Git workflow, but protected content is encrypted before it reaches the server.
Private
Private repositories
For internal product work where access control matters but normal server-side collaboration is acceptable.
- company code
- internal issues
- team reviews
Protected
Secret repositories
For source code, security research, regulated work, and private conversations that should not be readable by the server.
- protected code
- local unlock
- private rooms
Zero-knowledge E2EE without leaving the repository.
The goal is simple: Skron should help teams collaborate without becoming the place that can read their most sensitive source code, reviews, rooms, or repository keys.
What it means
The server stores encrypted data
In a secret repository, protected code, rooms, keys, and sensitive metadata are encrypted before they leave an approved device. Skron can sync the work without being able to read it.
Why teams need it
Sensitive work can stay in the normal repository workflow
Security fixes, signing keys, customer-specific code, incident notes, and private reviews can live next to branches and pull requests without moving the discussion to a separate secure messenger.
How access works
Trust is granted to devices, not assumed by the server
A secret repository asks for a local unlock. Repository keys are wrapped for approved identities, vault access is scoped, and trust changes require stronger proof.
Familiar repository hosting, with zero-knowledge modules built in.
The core UI stays close to tools developers already know: repositories, branches, pull requests, issues, and releases. Skron adds encrypted rooms, scoped vault grants, and local unlocks where sensitive work needs them.
Git repository hosting
Create public repositories, private company repositories, or protected repositories for sensitive work.
- Branches
- commits
- tags
Code review
Review pull requests with the repository, issue, chat room, and required secrets visible from the same place.
- Pull requests
- reviewers
- checks
Issues and boards
Track work without losing the link to code. Issues can point to branches, pull requests, rooms, and releases.
- Issues
- boards
- milestones
Encrypted collaboration
Use protected rooms and scoped vault grants when a change needs sensitive discussion or short-lived access.
- Rooms
- vault
- audit log
A pull request should have everything it needs nearby.
- CodePublic
Start from the repository
The main workspace stays familiar: files, commits, branches, pull requests, issues, and releases.
- ReviewPrivate
Bring the right context forward
A pull request can show the related issue, room, board card, and required vault access without opening four tools.
- ProtectProtected
Use secret mode for sensitive work
Secret mode keeps the repository workflow intact and asks approved devices to unlock protected content locally.
Pull requests stay focused
Review code first. Related issues, rooms, and vault grants are available when needed, not mixed into the file browser.
Encrypted rooms are contextual
Sensitive discussion can live next to the change it belongs to, while protected messages unlock only on approved devices.
Vault access is scoped
A reviewer can request short-lived access without turning the pull request into a secret-sharing thread.
Built for teams that like GitHub, but need stronger default protection.
Less scattered than GitHub plus chat plus a vault
Skron keeps encrypted discussion, issues, and short-lived secret access close to the pull request.
Less enterprise-heavy than legacy DevOps suites
The core screens stay close to repository hosting, code review, and issue tracking instead of becoming a giant admin portal.
More approachable than developer-only encrypted tools
Secret mode should feel like a repository setting with clear safety cues, not a cryptography product users must learn first.
Demo access