We’ve raised €1.5M in pre-seed funding to keep building the fastest way to run Playwright end-to-end tests. The round is led by Alliance VC, with participation from First Fellow, Greens, and our earliest backer Antler, who are doubling down on their investment. We’re also joined by angel investors from Netlify, Wolt, Voi, and CTO Roundtable.
What we’re building
Endform runs your Playwright end-to-end tests massively in parallel. Every test gets its own isolated machine. Your suite finishes in the time it takes to run your slowest test, whether you have 10 tests or 1,000.
It’s a drop-in replacement. You don’t change your tests, your config, or your setup. You swap one CLI command and your suite runs on Endform.
If you want the full origin story, I wrote about it when we first introduced Endform, and Oliver wrote about the technical architecture behind how it works.
What’s already happening
Endform has been running in production for a while now, and real teams depend on it daily.
Lovable moved their Playwright suite to Endform and grew their test count by 10x while their suite got 6x faster. They now run more than 400,000 Playwright tests per week on Endform. As Viktor Eriksson from the Lovable team put it:
“End-to-end tests used to slow us down. Endform has unblocked us, giving us results quickly so we can just keep moving.”
Other teams are using Endform in production too, running thousands of tests daily and getting results in seconds instead of minutes.
What the money is for
We’re a two-person team today. Oliver and I have built everything so far: the Rust CLI, the execution infrastructure, the analytics platform. The fundraise lets us grow.
We’re hiring engineers to go deeper on the product, and making our first go-to-market hires to reach the teams that need this most. If either of those sounds like you, please apply.
What’s next
We’ve proven that you can decouple suite size from suite runtime. The core execution engine works and scales. Now we want to go further with deeper analytics to surface flaky and failing tests before they become a problem, and better debugging tools to help you fix them fast.
The goal hasn’t changed since day one: developers should be able to write the tests they need without fighting the infrastructure to run them.
/ Jakob