About Svalin
The governance layer your security team needs — invisible to developers
Regulated companies are caught between two pressures: developers want to use the AI coding tools that make them dramatically more productive, and compliance teams need to prove those tools are governed. The answer most organisations default to is restriction — block the tools, limit access, slow everything down.
Svalin is built on a different premise. Engineering teams should be able to use Claude Code, Cursor, and Gemini CLI freely. The governance layer should be invisible to the developer and transparent to the auditor.
We deploy via MDM, govern what happens on developer machines, and produce tamper-evident evidence of observed activity, control posture, and coverage gaps — so your security team can say yes to AI adoption instead of no.
The Founder
Built by someone who saw the problem firsthand
Raphael is a backend engineer and technical leader with over ten years of experience building and scaling SaaS products. He has led engineering teams through a hypergrowth phase at a messaging automation startup — growing from 10 to 60 people — and has spent years working at the intersection of enterprise software and developer tooling.
Most recently working as a tech lead helping an organisation navigate the shift toward agentic development, he saw something that didn't sit right: developers and non-developers alike adopting AI coding tools across departments, with no visibility into what those tools were accessing, no audit trail, and no way to prove governance was in place.
That observation became Svalin.
"I wasn't looking for a startup idea. I was watching colleagues use Claude Code and Gemini on production codebases and realising nobody — including the security team — could answer the question: what did the AI actually access today?"
Want to co-build the governance layer?
We are looking for 5 forward-thinking engineering and security teams to help shape Svalin as design partners.