Building Axion Cloud: sync, storage and the TONE3000 integration

How I built Axion Cloud: preset sync, version history, and a TONE3000 integration that never routes audio through my servers.

You dial in a tone on one device, and it stays on that device. Axion Cloud syncs presets, rigs and captures between all of them.

The sync model

Axion Cloud follows one rule. The client owns the truth. Every preset edit goes into a local, append-only log first, and the cloud holds a replica of that log.

Sync should be invisible when it works and specific when it fails.

Version history costs nothing extra in this design, because the log is the history. Restoring a previous rig moves a pointer and copies no data.

Integrating TONE3000

The TONE3000 API brings thousands of community amp captures into Axion. I did it without proxying audio through my servers. Capture files stream directly from TONE3000's CDN to the client, a worker compiles them to the internal DSP graph, and they never touch my backend.

What's next

Next are shared rig links, collaborative preset folders and an offline-first conflict resolver that needs no input from the musician.

Written by Alopex ↗Developer, maker, explorer. I build tools, games and systems for creators and players.