Multiplayer Repositories - Connect your Logical Architecture to your Code

Unifying System Design Elements in One Platform

Traditional diagramming tools often fall into two distinct types:

• Whiteboarding tools, which are great for static visualizations of system architecture but lack context, interactivity and integration with actual code.
• Code mapping tools, which provide a detailed, visual map of your codebase but fail to connect these structures back to the broader system architecture.

This makes it challenging to correlate the high-level architectural plans to the various codebases.

Moreover, tools that can automatically document system architecture while integrating comprehensive system information—like API lists, dependencies, environments, and historical design decisions—are incredibly rare.

Introducing Multiplayer Repositories

Multiplayer is set to streamline this disjointed landscape.

Our new Repositories feature allows you to connect directly to your GitHub, GitLab, or BitBucket repository, linking files directly to components of your system architecture.

You can also connect to a public Git repository.

The ability to manage all system information in one place—instead of having to jump from reviewing static diagrams to searching through your repos—saves immense time and boosts productivity.

Connect your Logical Architecture to your Code

Multiplayer auto-documents your entire system architecture (including all components, APIs, dependencies, and environments), reflecting any changes dynamically.

You don’t have to manually draw a diagram and then connect it to your source code, you can link your repository files to your system components with a few clicks:

‣ Navigate to Repositories

‣ Connect your Git repos or select one

‣ Click the metadata icon

‣ Add a description, tags or link to one or more components in your platform

What's Next

Up next, we will be expanding the scope of our System Architecture Observability (Radar) to include the following:

• Platform Debugger: Create “platform debugging sessions” that include all session data, from front-end screens to back-end traces and logs. Easily add links to these sessions in tools like Jira, Linear, Confluence, and Trello.Teams won’t need to search for the needle in the haystack in their APM data or manually document the steps to reproduce an issue. All of the session data will be captured and shared, making it easy for QA or DevOps to share issues with developers and saving huge amounts of time for everyone on the team.
• Flow Diagrams: Visualize sequence diagrams with detailed dependency information at the component and API level for an easy understanding of low-level relationships.

If this is something that interests you, shoot us an email or let us know on Discord! 💜

You can try Multiplayer now, explore its features, and let us know how we can improve it to better serve your needs.