Getting Started
📌 If you have any questions shoot us an email or join us on Discord! 💜
👋 Welcome to Multiplayer!
Sick of grepping through log files, hot-potato hand offs, and relying on multiple tools?
In just a few steps, you'll be able to:
- Capture and share deep session replays that combine frontend screens with backend traces, logs, and metrics
- Use interactive notebooks to reproduce issues, test hypotheses, and hand off knowledge cleanly across teams and time zones
- Auto-document your architecture in real-time and gain full insight into your running system
Step-by-Step Guide​
(1) Sign up​
Visit go.multiplayer.app to sign up using Google, GitHub, GitLab, or your preferred email address. If you run into any login issues, check our troubleshooting steps.
🔑 Pro Tip: Once signed up, your workspace, project, and example content (Platform, Notebook, and Sketch) are automatically created.
(2) Capture Your First Session Replay​
Install the Multiplayer debugger browser extension to start recording session replays with frontend screens, public API calls, and request/response content.
(3) Get Deeper Insights into Your Debugging Sessions​
Enrich each debugging session with backend context from your existing telemetry data, automatically linking frontend screens to the relevant traces, logs, and metrics.
Navigate to the Platform Debugger in your Multiplayer project and configure OpenTelemetry.
(4) Start Designing, Testing, and Documenting your APIs​
Explore Platform Notebooks to collaboratively design, test, document, and debug your APIs and integrations.
🔑 Pro Tip: You can create a Notebook from a debugging session. This auto-generates a runnable test scripts, complete with real API calls, payloads, and code logic—that mirrors the failure path.
(5) Auto-Document your Architecture​
Automatically generate always-accurate system documentation and architecture diagrams so that your team can immediately understand how the whole system works and move faster when things break.
You can visulize your system architecture (components, APIs, dependencies, flows, etc.) in list format in the System dashboard or as a Platform architecture diagrams.
(6) Invite Your Team​
Bring your team on board for real-time collaboration in designing, developing and managing your system information and architecture.
Next Steps​
If you have any questions shoot us an email or join us on Discord!
If you’re interested in a particular feature send us a note - this will help us prioritize what you need the most!