Beta Purple Coda · DAW Bridge

Codex

Async collaboration between Ableton and FL Studio, without the stem folder chaos. One file does everything.

Apply for Beta →
Beta testers receive a lifetime license Limited spots · hello@purplecoda.com
♩

How It Works

One file.
Everything inside.

You and your collaborator are on different DAWs. Getting projects back and forth has always meant bouncing stems manually, losing MIDI, and having no idea what changed between sessions.

Codex fixes that. Export your session into a single .dawb file: one clean handoff instead of a folder full of stems and guesswork. Your collaborator drops it in, and everything is right where it should be.

No stem folders. No version confusion. Just send the file and get back to making music.

Inside a .dawb file
project.json: metadata, structure, tempo, markers
tracks/
*.mid: editable MIDI clips
*.wav: audio stems for non-translatable content
history.json: full collaboration lineage
manifest.json: asset checksums & metadata
Every export carries the full history of who sent what, from which DAW, and what was editable at each step.
♩

Interface Preview

Export. Send. Import.

A look at what the Codex interface will feel like, from exporting your session to receiving a handoff and seeing exactly what changed.

Codex: Export Session
Ableton Live
Project
Midnight Loop v4 16 bars
Tracks
Kick + Clap
MIDI · Editable
Bass Line
MIDI · Editable
Serum Pad
VST · Stem
Reverb Fx Chain
Complex FX · Stem
Sub Bass
MIDI · Editable
Export Mode
Stem
Render untranslatable tracks to audio
Flag
Export with warnings, recipient decides
MIDI Only
Strict: discard non-MIDI content
◈
midnight_loop_v4.dawb
2.4 MB
→
Codex: Import
FL Studio
Incoming Project
Midnight Loop v4 from Producer A
Collaboration History
Producer A Ableton
Created · 5 tracks · 3 MIDI, 2 stems
Today, 2:14 PM
Tracks
Kick + Clap
MIDI · Editable
Bass Line
MIDI · Editable
Serum Pad
Audio Stem
Reverb Fx Chain
Audio Stem
Sub Bass
MIDI · Editable

Concept UI, interface in active design

♩

Features

Built for how producers
actually work

⇄
Universal Interchange Format

Export from either DAW into a .dawb file. One format, both directions. MIDI, stems, tempo maps, markers, and plugin metadata, all in one portable file.

⧖
Collaboration History

Every handoff carries the full lineage: who sent what, from which DAW, what was editable vs. stemmed. No more guessing what changed between sessions.

◈
Intelligent Translation

Native FL instruments, complex Ableton effect chains: when a track can't fully translate, you choose at export: render as audio stems or flag as MIDI with warnings.

◉
See What You're Sending

Before you export, Codex shows you the full picture: which tracks are MIDI-editable, which had to render as audio, and why. No surprises on the other end.

♩

Get Involved

Built with producers,
not just for them.

Codex is early. If you're a producer who's dealt with the stem-folder headache, your real-world workflow is exactly what we're building for. Beta testers get lifetime licenses and a direct line into the product.

Apply for Beta →
🎛
Music Producers If you collaborate across Ableton and FL Studio, you already know this pain. We want to build Codex around your actual workflow. Beta testers receive lifetime licenses.
⌨️
Developers The data layer, CLI framework, and parser architecture are ready. Want to help build an open DAW interchange standard? Let's talk.
🏷
Industry Partners Studios, labels, or platforms interested in building Codex into collaborative workflows. We're open to early conversations.