Skip to main content
Studio is a desktop app. It reaches your devices directly — opens terminal sessions, drives RDP, opens serial consoles — and keeps a local workspace that stays responsive even when your network doesn’t. Sign-in uses your Altostrat account, which carries your organization membership, saved hosts, credentials, and work history across machines you install Studio on. The first time you launch Studio you’ll go through a short onboarding that tailors defaults to the vendors you work with and the role you play on your team.

​
Download Studio

macOS (Apple Silicon)

For M1, M2, M3, and M4 Macs.

macOS (Intel)

For Intel-based Macs.

Windows

64-bit installer for Windows 10 and 11.
Install the package, launch Studio, and the sign-in screen appears.

​
Before you install

Make sure the workstation can reach the networks you intend to operate. Studio runs locally and connects from your machine, so VPN, routing, firewall policy, serial adapters, and OS permissions matter.

​
Sign in

Use your Altostrat account. If you don’t have one, the sign-in screen has a link to create it — you’ll come back and sign in once the account is ready.

​
First-run onboarding

1

Sign in with your Altostrat account

Enter your credentials. If you’re already signed in on another device, a secure sign-in prompt confirms the new install.
2

Pick your organization

Choose the organization this workspace belongs to. If you’re new, create one — you can rename it or invite teammates later.
3

Choose your role

Tell Studio whether you’re a network engineer, operations lead, NOC operator, or something else. The role biases default views and the Copilot system prompt.
4

Pick the vendors you work with most

Select the device vendors you touch day to day. Studio uses this to prioritize parsers, command hints, and diagram shape libraries.
5

Finish

You land in the workspace with a primary sidebar, an empty canvas, and Copilot on the right.

​
What you get after sign-in

  • Copilot configured for your role and vendors, ready to answer questions and stage work.
  • Sync across devices so your hosts, procedures, and memories follow you between machines.
  • Team collaboration once you invite others into the organization or join one that already exists.
  • Cloud backup of your workspace, so a fresh install restores inventory and history.

​
First useful setup

After onboarding, do these before the first real incident:
  1. Open Settings and confirm theme, terminal behavior, AI model, and Autopilot / YOLO mode.
  2. Add or import your first host.
  3. Create the Keychain entry that host should use.
  4. Connect once and let Studio detect device identity.
  5. Save one known-good operational fact as a memory.
  6. Try one read-only Copilot prompt against selected terminal output.
This gives Studio enough context to become useful: a host, a credential reference, a detected device identity, a memory, and a conversation pattern.

​
Install on more than one machine

Sign in on every machine you use. Hosts, diagrams, procedures, memories, and conversations sync across installations within the same organization. Credentials in Keychain sync in encrypted form so you don’t re-enter them per machine.
If you move between a laptop and a workstation, keep both signed in. Studio keeps each install consistent with the organization as long as it can reach the network.

​
Having trouble?

If sign-in hangs, the app won’t update, or a session refuses to open, start with troubleshooting. Most first-run issues are covered there.

​
Where to go next

Tour the workspace

Walk through the activity bar, tabs, Copilot panel, bottom panel, and shortcuts.

Hosts and credentials

Build device inventory and open your first session.