Renaming Remotion to Multi

Remotion is now Multi.

This rename completes the product shift we announced earlier this year to refocus on helping technical teams build together, faster. We’ve been iterating on new features—and deleting some old ones—based on user feedback. In the last two weeks, we shipped the final major features of that refocusing.

So why the rename?

As soon as we decided to refocus, the name and brand “Remotion” no longer felt right. We’d initially landed on the name Remotion because it allowed collaboration, well, remotely. We also liked that it contained the words “emotion” and “motion,” both of which are harder to sense from your team remotely.

The move to remote work was profound, and we’d set out to build a tool that supported new ways of working. But, only supporting remote teams—or having a name that suggests that’s all what we do—was limiting. In fact, it’s telling that what ended up being the winning tools for remote work like Slack, Teams, and Zoom, were not specifically designed for remote teams.

With this new product focus, we’re building tools that all technical teams can use to collaborate better, whether they’re right next to each other or on different continents.

So, the final step of our shift in direction is our new name: Multi.

Multi exists to make building together truly multiplayer. By facilitating frictionless collaboration on code, teams can work faster, be more productive, and have a better working experience. You leverage your team more, get more help, and have a delightful time doing it. This idea isn’t new across the product tech stack. Other functions have gained new multiplayer tools that make working together faster—think Figma for designers—but engineers don’t have anything nearly as powerful. Sure, we have great pull request and repo tools like GitHub and co., but that’s akin to being stuck in the Dropbox + Sketch days of design. It works, but it could be much faster.

Our long-term goal is to create a multiplayer layer across all the tools you work in, be they web-based or native. It should feel as though your entire operating system was upgraded for teamwork.

Our starting point for this vision is video calls for pairing, code walkthroughs, live code reviews, and other collaborative sessions.

Multi calls instantly make your apps multiplayer so that anyone can point, draw, or edit. Share one app and you’re pairing. Share two and it’s like you’ve blended your workspaces.