Your team's engineering brain
The why behind your code lives in a few heads and sessions that evaporate on close. Skillsync keeps it. Think git, but for your sessions: every session is a commit, and the brain is your team's history of why
- Trace decisions. Read the session they came from, and what got rejected
- Turn sessions into reusable skills your team and their agents run
- Formalize your engineering culture: your team's taste, made explicit
Decision traceorg-private
Why is the relay a single server?
01The relay stays one server; scale is per-customer allocation
No shared state between instances; Redis adds latency. A box per customer also isolates their traffic.
↳ view in session · relay-architecture #m-142
02Rejected: horizontal scaling behind a shared store
03End-to-end encrypted so the relay host can't read sessions