Tessl
Spec-driven AI development from Snyk founder Guy Podjarny: write what the software must do, and the specification stays the source of truth.
Highlights
- Spec-driven AI coding — engineers write specs, Tessl generates the implementation
- Multi-model backend support across Anthropic, OpenAI, and others
- Test generation and maintenance baked into the spec workflow
- Founded by Guy Podjarny (founder + ex-CEO of Snyk)
- $125M Series A at $750M valuation; Index Ventures lead with Accel, GV, Boldstart
- London HQ; ex-Snyk and ex-Akamai security engineering DNA
- Positioned for production engineering rather than prototyping or single-developer use
External link — opens tessl.io in a new tab. Tessl is a third-party product; we are not affiliated with it.
About Tessl
What it is
Tessl is an AI-native development platform built around specifications. Engineers write a specification of what the software should do; Tessl generates, tests and maintains the implementation against it, with the spec rather than the code treated as the artefact that matters. Founded by Guy Podjarny of Snyk, with a $125M Series A.
Why it's different
The idea addresses the real problem with AI-generated code, which is not producing it but owning it. Code a model wrote and nobody fully understands becomes unmaintainable quickly, and regenerating it produces something different. Making the specification the durable artefact is a coherent answer, and if it works it changes what a codebase is. Whether it works is genuinely unresolved. Natural-language specifications are ambiguous, which is the reason programming languages exist, and the gap between what somebody meant and what they wrote is where defects come from. Treat this as a well-funded bet rather than a settled approach.
How people use it
It is aimed at production engineering teams rather than at prototyping, which is the harder and more interesting target. The realistic way in is a well-bounded service where the behaviour can be stated precisely and verified by tests, rather than anything whose requirements are discovered while building it. Watch how it handles a specification changing after the implementation exists, because that is where the model either holds or collapses.
Written by the n3os team. We are not affiliated with Tessl.
This listing was written from public information, without Tessl’s involvement. If you own it and something here is wrong — or you would rather not be listed at all — email us and we will correct or remove it.
Get the ones worth knowing about
We write one of these for every tool worth the trouble. Get the new ones, plus what we have found genuinely useful lately.
Your address goes to Buttondown, who send the emails on our behalf. One click unsubscribes, and the list is never sold or shared.