> ## Documentation Index > Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # System requirements > Desktop platforms, network reach, privileges, and usage limits you should know before rolling out Studio. Studio is a desktop app. It reaches your devices directly, captures packets, opens serial consoles, and keeps a local workspace that stays responsive even when your network doesn't. For most teams the answer is "a reasonably modern machine with outbound internet." A few features — packet capture, Layer 2 monitoring, interface changes — need elevated privileges on the workstation that runs them. This page is the short list. ## Supported platforms | Platform | Supported | Notes | | ------------------ | ------------------- | -------------------------------------------------------------- | | macOS 13 and newer | Yes | Apple Silicon is the primary target; Intel Macs are supported. | | Windows 10 and 11 | Yes | 64-bit. | | Linux | Not in this release | Planned. | ## Network Studio's network needs are modest, but they are non-negotiable: * Outbound internet access to your Altostrat account endpoints and the AI provider endpoints. * Reachability from your machine to the devices you want to manage — VPN, jump host, or direct. * Open outbound on standard ports (443 for sync; 22/23 and device-specific ports for terminal sessions). If your organization runs restrictive egress, make sure those destinations are reachable before rolling Studio out to a team. ## Workstation reachability Studio connects from the workstation where it is running. If your laptop cannot reach a management subnet, Studio cannot magically reach it either. Use the same network path you would use for manual operations: * Corporate VPN for private device networks. * Jump hosts for segmented management zones. * Local network access for discovery, packet capture, and Layer 2 monitoring. * Serial adapter access for out-of-band console work. Document jump hosts in the host editor rather than relying on an operator to remember the path. ## Privileges Some diagnostics talk to the operating system directly. Running them needs elevated permission on the workstation that hosts the session. | Feature | Requires | | --------------------------------------------- | ------------------------------------------------------------ | | Packet capture | Administrator or sudo / capture capability on the interface. | | Passive ARP and Layer 2 monitoring | Interface access and local network visibility. | | Rogue DHCP / STP monitoring | Access to the relevant broadcast domain. | | Interface IP or route changes on your machine | Administrator or sudo. | You don't need any of these to use the product — only to use the specific features that touch the OS at that level. ## OS permissions macOS and Windows may prompt the first time Studio uses a protected capability. | Capability | Prompt you may see | | ----------------------- | ------------------------------------------------------- | | Voice and video calls | Microphone and camera access. | | Screen share | Screen recording or screen capture access. | | Packet capture | Administrator approval or capture-interface permission. | | Serial console | Permission to access the attached serial device. | | Local network discovery | Local network or firewall prompt. | Approve only the capabilities your team uses. If a feature fails immediately after first launch, check OS privacy and security settings before changing Studio configuration. ## Quotas and limits Studio applies soft limits per organization to keep the product responsive. Your plan determines the exact numbers; the dashboard shows current consumption. | Limit | Typical default | | -------------------------------------- | -------------------------------------------------------------------------------------- | | Hosts per organization | Thousands. Large-fleet orgs should contact support. | | Procedures per organization | Low thousands. | | Session recordings per organization | Capped by total recorded size; oldest are first to be pruned when quota is approached. | | Image attachment size | 20 MB per image. | | Concurrent shared-session participants | Up to nine in a call. | ## A note on the local helper On desktop, Studio runs a small local helper process that lets the app reach your devices and your machine's network stack. You don't manage it — it starts and stops with the app, and it stays on your workstation. If Copilot says it can't see your devices, restart Studio and see [troubleshooting](./troubleshooting). ## Related Get the desktop app and sign in with your Altostrat account. Common symptoms and what to check first.