Altostrat Studio

What does Studio actually automate, and what does it leave to me?

Studio drafts configs, builds runbooks from chat, walks web UIs, documents sessions, and keeps the topology current. It does not push a change to a device until you approve the diff. The copilot is read-only by default. You turn on write mode per session, per device, or never.

Which vendors does it support today?

Full terminal support for anything that speaks SSH, Telnet, Serial, or RDP — so in practice every major vendor. The copilot has deep context for Cisco IOS, NX-OS, IOS-XR, Junos, FortiOS, PAN-OS, RouterOS, ArubaOS, and the usual Linux network stacks. If your gear has a CLI or a web UI, Studio can sit in front of it.

What about devices that only have a web UI?

Studio drives them in a sandboxed browser. The copilot clicks, reads, and screenshots each step, then hands you an annotated trail of what it did. You review the evidence before anything ships. The MikroTik WebFig, the Meraki dashboard, the old Dell iDRAC — all fair game.

How do credentials work, and where do they live?

In your OS keychain, synced to an encrypted vault backed by AWS KMS with per-org customer-managed keys. Studio injects them at connect time, not in chat and not in LLM prompts. Every fetch is audited. FIPS 140-2. If a teammate needs access, you grant it to a person, not to a shared password.

Can my team actually share a session live?

Yes — real-time cursor presence in the same SSH session, a Chime call, live transcription, and an asciicast recording that lands in your knowledge base when you're done. The session, the reasoning, and the fix all stay searchable. That's how you stop losing the network when a senior engineer resigns.

What does rollout look like? How does my team actually adopt this?

One engineer downloads Studio on their laptop tonight. They connect to a few devices, ask the copilot something hard, and use it for one on-call shift. If it earns its seat, you invite the team, move credentials in, and retire whatever you're currently swivel-chairing between. Most MSPs go from "one curious engineer" to "team standard" in under three weeks. No forklift, no migration project.