Replay

OUR MISSIONAbout Replay

We believe people understand what they can see, and if you cannot see what your software is doing, you cannot understand it.

Recording software so that you can replay it later is not a new idea. It is just incredibly difficult. We've been working on it for the past five years and have just recently gotten good at it.

We see a world where collaborating with Replay is second nature. When an engineer gets stuck, they share a replay. When a test fails, a developer clicks a link to view the replay. When a question is asked on Stack Overflow, folks comment directly in the replay. When an issue is filed in Github, maintainers help directly in replay. You see where we’re going with this!

We believe recording software at scale, will change the way software is understood. Recordings let us show type-hints in your editor and even suggest type improvements. Eventually, we can support the debugging process by suggesting hypothesis and eventually potential fixes.

If you’re excited to be a part of this journey and think Replay could be a good fit for your team please reach out to us at hi@replay.io.

Our Team

We're a distributed company, founded by people who have spent many years working on fully distributed teams. We work across the globe, so we focus less on hours and more on building a great product. We build for the long term: it's a relay, not a sprint.

  • Jason Laster

    CEO

    Jason has contributed to debuggers in several runtimes and prior to Replay was the tech lead for the Firefox Debugger. When not debugging the debugger, you’ll likely find him in the woodworking studio or outside with his pup Walle.

  • Brian Hackett

    CTO

    Brian has had a longtime passion for helping people understand hugely complex software systems, starting with a Stanford Ph.D. and continuing through 10 years at Mozilla, where he worked on JavaScript VM optimizations and developed a precursor to Replay. He is a nomadic adventurer and enjoys sailing around Polynesia and van travel in the western US with his wife.

    • Dan Miller

      Software Engineer

      Dan started his career at Etsy where he worked on PHP runtimes and type systems and has been trying to help developers be more productive ever since. When not trying to express the "is a hot dog a sandwich" question using types, he can probably be found hiking or skiing if the weather is nice, otherwise he's probably playing Super Smash Bros.

    • Kannan Vijayan

      Software Engineer

      Kannan has implemented everything from an IrDA stack for Blackberry devices, to an mRNA sequence analysis platform for biology researchers, to a Javascript JIT for Firefox. Outside of work hours, he is learning his way around creating a nature preserve and small personal farm in a 100-acre patch of exploited land in rural Canada. He has always had his feet in two different worlds at any given time and aims to keep it that way.

    • Logan Smyth

      Software Engineer

      Logan loves diving into complex systems, and before Replay he helped maintain BabelJS, and worked on Firefox's developer tools at Mozilla. Outside work he loves playing games, reading, and finding interesting new things to learn about.

    • Holger Benl

      Software Engineer

      Holger explored the world of programming languages from 6502 machine code to extracting LISP programs from mathematical proofs. These days he's mostly interested in creating developer tools. When he's not working on Replay or one of his VSCode extensions, he likes to read political blogs and books and watch asian movies.

      • Jon Bell

        Designer

        Jon has been excited about designing things on the internet since the 80s, and has led design teams at Twitter and Windows Phone. He lives in windy Wellington, New Zealand with his large family and loves writing, teaching classes, playing soccer, and trying to remember how to play the clarinet.