What SpanDock needs to run
One app, no database to install and no open ports. Size the hub for your team below, then install it.
Hardware calculator
Drag the sliders to match your team. The numbers update as you go.
Records a day
150,000
Data a day
0.2 GB
Stored history
7 GB
Hub server
- CPU
- 2 vCPU
- Memory
- 4 GB
- Disk
- 20 GB
Stores the history, serves the dashboard and forwards to your destinations. Peak ingest about 21 records a second. Set its retention to 30 days and its size limit to at least 8 GB (the default is 2 GB).
Each developer machine
About 100 MB of memory and 500 MB of disk, including the queue it keeps while offline. Nothing else to install.
Plan: Standard or above (more than 3 clients). See pricing.
How we estimate: about 1.5 KB of disk per stored record, measured, plus 30% headroom and 10 GB for the system and updates. A developer sends about 1,000 (light), 3,000 (typical) or 8,000 (heavy) records a working day; that varies by tool and workflow, so watch the real numbers on your dashboard during the first week. A cloud VM or any always-on machine works; the hub should have a local SSD.
Supported systems
| System | Version | Processor |
|---|---|---|
| macOS | 13 Ventura or later | Apple Silicon and Intel |
| Linux | glibc 2.38 or later: Ubuntu 24.04, Debian 13, RHEL 10, Fedora 39 or newer | x86-64 and ARM64 |
| Windows | Windows 10 or 11, 64-bit | x86-64 |
Clients and servers are the same app, so the same systems run either role. The download is about 35 MB; installed, about 100 MB.
What runs where
Client
Every developer machine
Receives the AI coding tools' telemetry on the machine and sends it to your server over the encrypted tunnel. Queues on disk while offline.
Hub server
One always-on machine
Stores the history, serves the dashboard, runs the model proxy and forwards to your destinations. A single developer can run it on their own computer.
Satellite
Optional extra servers
Take clients and forward their records to the hub, so the load is shared and clients fail over between servers. Premium and Enterprise.
Network
- No inbound ports. Clients and servers connect out over an encrypted tunnel, through firewalls and NAT.
- Outbound internet on every machine, for the tunnel and for updates.
- Servers reach spandock.com to activate and for a daily license check. Air-gapped sites use an Enterprise offline license.
- Local only by default. The dashboard and the telemetry receiver listen on the machine itself; you choose whether to publish the dashboard.