Go Meow Server
One session clock for players in different places. Run the coordinator on your studio computer or server, then connect clients that prepare and play their audio locally.
Start together
The host approves members and schedules shared starts, stops, tempo changes and beat positions. Clients estimate their clock offset and schedule ahead, so an arriving beat packet is never the cue to play. The included browser page provides an audible metronome and connection controls.
Connect Desktop or a custom host
Desktop’s Live Session panel supports Studio patterns, native arrangements and finite MusicScript scores. A TypeScript SDK exposes client connections, timing, metronomes and a scheduling-adapter contract for scripting hosts. The standalone MusicScript CLI still needs a network adapter; its local session service is a different protocol.
Know what is shared
The service shares session state and scheduled event data. It does not stream audio, copy projects or samples, or execute incoming scripts. All participants need their own local content. Native arrangement transitions can have a short restart gap; clock estimates and audio-device latency affect audible alignment.
Self-hosted setup
Requires Node.js 22 or newer. Local setup listens on 127.0.0.1:4455 and uses individual API keys. Remote Desktop connections require WSS, an allowed client origin and a reachable server. There is no built-in public relay or NAT traversal.