What you can do in Studio
Connect to devices
Organize hosts in folders, attach SSH, Telnet, HTTP, HTTPS, RDP, VNC, Video Stream, or Custom protocols, and reuse credentials from Keychain.
Work in the terminal
Clickable IPs and interfaces, selection-to-Copilot, staged command queues, live error detection, and full session replay.
Troubleshoot with Copilot
Copilot sees your active tabs, hosts, memories, and output. It can run read-only diagnostics, stage commands, and build plans — with approval where it matters.
Turn work into procedures
Promote a successful chat into a parameterized runbook with allowed tools, arguments, and success criteria. Run it again with different inputs.
Draw the network
Editable diagrams with Cisco and cloud service shape libraries, auto-layout, multi-page support, and one-click generation from host inventory or discovery output.
Collaborate in real time
Share a terminal with owner, co-work, or viewer roles. When two people join, promote to a voice or video call without leaving the session.
How Studio is shaped
Studio is a desktop app for macOS and Windows. It reaches your devices directly — runs SSH sessions, captures packets, drives RDP, opens serial consoles — and keeps a local workspace that stays responsive even when your network doesn’t. Your work is organization-scoped once you sign in. Private items stay to you; team items sync across the organization. Credentials and other sensitive fields are encrypted before they leave your machine.The whole story
Studio is meant to hold the full life of operational work:- Inventory the target. Add a host, attach one or more protocols, and reference a Keychain credential instead of copying secrets into device records.
- Open the work. Connect through the terminal, a web UI, RDP, VNC, a video stream, or a custom entry your team tracks.
- Gather evidence. Use terminal output, files, diagrams, diagnostics, connector calls, memories, and active tabs as working context.
- Ask Copilot to reason with that context. Start in Ask or Planning when the situation is uncertain; use Default when you want Copilot to act with normal approval prompts.
- Create artifacts. Turn output into a report, table, diff, diagram, dashboard, or editor tab that stays attached to the work.
- Promote repeatable paths. When a chat solves something cleanly, turn it into a parameterized procedure with arguments, allowed tools, and success criteria.
- Share the result. Bring a teammate into a live session, share the artifact or run transcript, or publish the procedure for the organization.
- Preserve what matters. Save durable facts as memories so future conversations and procedures start with the right network context.
Who Studio is for
Studio is built for the engineers who run real production networks. If you’re an MSP running mixed customer fleets across dozens of vendor platforms, you already know the cost of context-switching — terminal in one window, ticketing in another, monitoring in a third tab, credentials in a fourth, documentation somewhere else. Studio puts those surfaces in one workspace. If you’re at an ISP or WISP running subscriber infrastructure at scale, Studio is where the terminal, the looking glass, the customer-comms drafts, and the post-mortem all sit in the same place. If you run SIP or PSTN platforms as a voice carrier or PBX operator, Studio is where the one-way audio complaint, the SIP trace, the SBC rule change, and the customer reply stop being five different tools. The use cases tab walks through 25 real, end-to-end scenarios — from a Kayako ticket and a failed Dell disk to an upstream BGP outage with bulk customer SMS, to a one-way audio complaint resolved with a SIP trace and a firewall change. Because Studio runs AI against production infrastructure with real credentials and real device access, the AI safety tab is the engineering account of the controls that keep that safe: per-organization FIPS-grade encryption, the human-in-the-loop approval gate, the Bedrock-only data flow, and the honest list of limits that aren’t resolved yet.Studio and the Altostrat platform
Studio is one of two surfaces Altostrat provides for operating real networks. The other is SDX — the control and data platform that manages MikroTik fleets across thousands of deployed sites. SDX handles site onboarding, fleet health, configuration backups, policy distribution, and secure remote access. Studio is the workspace engineers work in day to day. SDX is the platform that keeps fleet state current and coordinates changes across managed sites. The two are built to complement each other. Studio works with any SSH-reachable device and doesn’t require SDX; SDX can be operated entirely through its own dashboard and doesn’t require Studio. But teams running Altostrat-managed MikroTik fleets benefit from using both — the fleet SDX manages is the same fleet Studio operators are working on, and the operational patterns SDX captures across thousands of sites inform how Studio evolves. Read the SDX introduction if you’re already running managed sites and want to understand the platform Studio sits alongside.Where to go next
Install Studio and sign in
Install and sign in walks through the download, the first-run flow, and what you pick during onboarding.
Learn the workspace
Tour the workspace covers the activity bar, tabs, Copilot panel, bottom console, and the layout shortcuts you’ll use all day.
Add your first host and connect
Hosts and credentials shows how to build device inventory and open your first session.
Bring Copilot into the session
AI Copilot covers response modes, context attachment, Autopilot, and approval posture.
Promote successful work into procedures
Procedures turns a one-off investigation into a reusable runbook.
Browse real-world scenarios
Use cases shows how MSPs, ISPs, and VoIP carriers chain Studio together with their existing ticketing, monitoring, vendor, and comms tools.