it’s 11pm. your DAW is open. you have an idea. you don’t want a loading spinner. you don’t want to “sign in to continue.” you don’t want a service-degraded banner. you want the tool.

most music software you use today started cloud-first because that’s where the easy money was: subscriptions, telemetry, network effects. but the rig you work on between sessions — the catalog you flip through, the masters you bounce, the references you a/b — none of that needs to be in someone else’s data center.

GRIDWERK runs on your machine. always offline-capable. always opens instantly. that’s not a feature. that’s the entire premise.

what local-first actually means

it’s not just “you can use it offline.” that’s the floor.

local-first means:

your audio never leaves your machine. not for stem separation, not for mastering, not for reference analysis. demucs runs on your CPU. the mastering chain is real DSP, not a cloud round-trip.
your library is yours. SQLite on your disk. you can copy it. you can back it up to whatever you want. if GRIDWERK disappears tomorrow, you still have the data.
features keep working when the internet breaks. the only things that need a network are: license validation (with a 7-day offline grace), optional integrations like Spotify or YouTube reference fetching, and the day you click “publish” on a release.
nothing GRIDWERK does on your machine becomes a per-minute bill. cloud stem separation costs money per song. local stem separation costs CPU time, which you already paid for.

what we lose by being local-first

i should be honest here.

we don’t have real-time collaboration. you can’t share a session with another producer over the internet and have you both editing it. we picked the wrong half of CRDT-vs-local-database and the right half is on the roadmap, not in the box today.

we don’t get free network-effect virality. people don’t accidentally see GRIDWERK because their friend shared a Splice pack with them. we have to earn each user one at a time.

we don’t get to upsell cloud storage. every cloud SaaS makes most of its money on the moment a user runs out of free tier. we make $19/mo for the tool, period. honestly, this is a feature.

why it matters for producers specifically

producers ship work that’s worth real money. unreleased beats are inventory. a leaked stem is theft. a vocal sent to the wrong cloud is a lawsuit waiting to happen.

every producer i know has a horror story about uploading something to the wrong place. “i swear i set it to private.” “the link was supposed to expire.” “they used my unreleased loop in a tiktok.”

local-first kills that whole category of problem. there’s no link to leak. there’s no service to misconfigure. the audio is on your disk; the only person who uploads it is you, when you decide to release it.

what’s still on the network

i’m not trying to oversell the offline angle. some things genuinely need it:

license validation — Pro is a subscription, and the app re-checks your license every so often (with a 7-day offline grace period so a bad airport wifi day doesn’t lock you out)
reference analysis — when you drop a YouTube link to A/B against, we have to actually fetch the audio. that’s a network call. but the analysis happens locally after the download.
distribution prep — when you’re ready to ship to DistroKid or TuneCore, we hand them the metadata and files. that’s the point.
crash reports — if the app crashes and you’ve left the opt-in on (default), we get an anonymous stack trace. no audio, no project names, no file paths.

everything else — your library, your projects, your masters, your stems, your references-on-disk — never leaves the machine.

the philosophical part

most SaaS treats your data as their leverage. they keep it, they index it, they decide who else gets to see it. when you cancel, they make leaving as painful as they legally can.

i don’t want to build that. i want to build the rig that’s quietly there at 11pm when you have the idea. you open it. it opens. it works.

if i ever stop being a person who makes music, i still have to be able to look at GRIDWERK and use it without flinching.

key takeaways

GRIDWERK runs entirely on your machine; audio, projects, library, stems all stay local
only network calls: license check (with 7-day offline grace), optional integrations, your explicit publish/distribute action
you give up real-time collaboration for now; you keep speed, privacy, and ownership of your work
the cost model isn’t “pay more as you grow” — it’s $19/mo for everything, regardless of catalog size

if any of this sounds like the rig you wanted, join the waitlist. we’re in private build — drop your email and you’ll get the install link the day it ships. the library, project tracker, and DAW integrations are free forever. Pro is when the production suite and business tools turn on.