majiks← back to home

The ecosystem · Architecture deep dive

majiks · ecosystem

Eight platforms.
One royalty rail.
One identity.

Majiks is not a single app. It's eight verticals running on one shared substrate — Magic Unicorn's Unicorn Commander — federated, sovereign, in-house.

They share one rights layer (Media — the spine), one creator identity (Keycloak SSO), and one royalty rail. Every track flows through the same provenance and settlement infrastructure regardless of which surface it's consumed on.

Cradle to grave. Creator tools, publishing, distribution, sync licensing, education, kids, news, and the rights registry that anchors them all. This page is the architecture.

~8 minute read · architecture · last updated 2026-04-29

The Loop · Cradle to grave

Five steps. No intermediaries. The same circulation.

The verticals are not a portfolio. They're positions on a single loop — the same song moving from creation through provenance, distribution, ownership, and discovery, then re-entering creation as the next track's seed.

CREATEStudioPUBLISHMedia · ISRC + certDISTRIBUTEOnline · MusicOWNListener · $1DISCOVERAI agentsThe Loopcradle to grave

Most music platforms own one segment of the supply chain — generation, distribution, monetization, discovery — and depend on someone else for the other three. Each handoff is a fee, a TOS, a place where the creator's rights can be re-priced or revoked.

In the Majiks loop, every step is owned. Creation happens in Studio. Provenance is minted in Media — ISRC, Chromaprint fingerprint, SHA-256 certificate. Distribution flows through Online (consumer), Music (web DAW), the streaming spine. Ownership lives at the listener — they bought a file, not a stream credit. Discovery happens through the same registry — AI agents asking “is this track legitimate?” get an authoritative answer because the receipt was issued at upload.

Every revolution feeds the next. The data doesn't fragment because the rights data doesn't fragment.

The substrate · Unicorn Commander

All eight verticals run on infrastructure we built, on hardware we own.

Unicorn Commander is Magic Unicorn's federated, distributed infrastructure platform. It is the substrate — the layer below the rail. Every Majiks vertical is a workload on it. Every container, every database, every streaming endpoint, every Keycloak realm. Not a single piece of Majiks runs on a third-party cloud we don't control.

01
Sovereignty

No AWS bill. No GCP TOS. No Vercel rate limit on what we ship. The cost curve scales with hardware we already own — not with vendor pricing pages.

02
Federation-ready

Built so anyone can eventually run a Majiks node. Self-host their music, mint their own provenance certs — and still register back into the authoritative root.

03
Open architecture

The substrate isn't a black box. We document it, ship parts of it open-source, and use it across our other businesses. Majiks is one tenant of many.

UC is its own product, with its own roadmap. Read more →

The federation thesis · Layer 03

DNS for AI music. In plain English.

In a few years, AI-generated music will be everywhere. Millions of tracks per day, distributed across countless platforms — some big, some niche, some not yet built, some run by individuals on hardware in their basement.

In that world, the scarcest resource is not the music. It's the answer to one question — “is this track legitimate?” Who made it, when, with what tools, under what license, owed to whom.

Somebody has to be the authoritative registry. The same way DNS root servers tell the open internet where domains actually live, an authoritative registry will tell AI agents — and DSPs, sync clients, distributors, fans — where AI-music provenance actually lives.

We've designed the architecture to be that registry. Today, we're the spine — issuing real ISRCs, minting Chromaprint fingerprints, signing SHA-256 provenance certs at upload, applying for the wholesale ISRC Manager tier.

Tomorrow, when we open-source the platform, anyone will be able to run a Majiks node. Federate their catalog. Operate their own neighborhood of music. And every one of those nodes will register back here — to the root.

The architectural moves
  1. 01
    Be the spine first.

    Issue every ISRC. Mint every fingerprint. Sign every cert. The root doesn't earn authority overnight — it earns it by being the most-used issuer.

  2. 02
    Apply for ISRC Manager.

    Wholesale tier. The right to issue ISRC blocks to other labels. Approval = registry of registries.

  3. 03
    Open-source the node.

    Anyone can run their own Majiks. Self-host catalog, federation-ready storage, local provenance minting.

  4. 04
    Route discovery back.

    Federated nodes register their catalogs and provenance certs against the root. AI agents query one place, get answers about everywhere.

The royalty rail

Publish once. Earn from anywhere in the ecosystem.

A creator does not negotiate a separate deal with each surface. They publish once, in Studio, and the rights data flows to Media — which is what makes the same track addressable across every other vertical, automatically.

The flow
Step 01
Studio publishes.

Single-click from DAW. Master + stream files + artwork + metadata.

Step 02
Media registers.

ISRC minted. Chromaprint fingerprint computed. SHA-256 cert signed. Receipt issued.

Step 03
The rail opens.

One identity, one rail, one ledger. The same track is now addressable across every surface.

Online

$1 per song · 100% to artist on personal license

Music

Reuse in browser DAW · sample royalty per session

Media

Sync licensing · matched to brand briefs

Academy

Course content licensing · D2C creator education

Training

Corporate-use licensing · enterprise multi-seat

Royalties don't fragment because the rights data doesn't fragment. The same ISRC, the same fingerprint, the same provenance cert — referenced from every surface, settled to the same artist account, on the same ledger.

Why eight, not one

Compliance + audience differentiation forces decomposition.

A monolithic music platform serves no one well. Each vertical has a different audience, a different compliance perimeter, a different commercial model — but they all share the same spine, substrate, and rail.

Majiks Studio
Pro creators · producers

Local-first, latency-sensitive, DAW-grade UX. Native macOS. 629 tests passing.

Majiks Online
Listeners · creators selling D2C

Stripe Connect, fingerprinted catalog, public discovery, $1 D2C economics.

Majiks Music
Casual web users · mobile-first

Web Audio + cloud ACE-Step. Browser DAW. Lower-friction, lower-fidelity entry.

Majiks Kids
Parents · educators · K-8

COPPA + FERPA from day one. Separate database, separate auth, separate everything.

Majiks News
Discovery-driven listeners

Behavioral feed, content decay, TikTok-style consumption — different ML, different metrics.

Majiks Media
Sync clients · brands · agencies

The rights spine. Sales surface for sync licensing. Audit-grade provenance receipts.

Majiks Academy
D2C learners · hobbyists

Self-paced courses, individual subscriptions, marketing-led acquisition.

Majiks Training
Enterprise · agencies · education partners

Multi-seat licensing, certification, SLAs, procurement flow. Different sales motion entirely.

Like Google → Alphabet — but designed that way from day one. Each vertical can grow into its own product. Some will. But they share the spine, the substrate, the rail. A creator's identity, royalties, and rights move with them across every surface.

The technical architecture

The actual stack. Not a marketing diagram.

No reference architecture. This is what's in production today, in our containers, on our hardware.

Substrate
Unicorn Commander · federated, distributed
In-house · zero vendor lock-in
Foundation model
ACE-Step 1.5 · open source
Formal partnership with Junmin Gong's team
Inference
MLX-accelerated on Apple Silicon (Studio)
Cloud option via ACE Music Cloud
Identity
Keycloak SSO
Single creator profile across all eight verticals
Rights layer
ISRC Registrant (approved) · MLC Sound Source (approved) · MLC (registered) · ISRC Manager (applied)
Operational at retail · pending wholesale
Storage
PostgreSQL + Drizzle (rights data) · Milvus (vector similarity) · LanceDB (knowledge graph)
Best-of-breed datastores per workload
Streaming
Icecast-KH + Liquidsoap + HLS adaptive (Relay)
Production · multi-codec output
Audit posture
Chromaprint dual fingerprinting · SHA-256 provenance certs · FLAC archival
Cite-able receipts for every track at upload
DSP
Native Rust crates · 285 Rust + 344 Python tests
629 passing · zero failures
Why now

Four conditions converged in the last twelve months.

None of these existed at this maturity in 2024. The window is open right now — and we're the team standing at it.

April 2025
ACE-Step 1.5 shipped.

The open-source music foundation model we're formally partnered with reached production-quality on-device generation.

Production today
MLX matured.

Apple's MLX framework matured for music workloads. We ship MLX-accelerated inference today — 2-3× faster than CPU/PyTorch.

Filing window
MLC Sound Source is open.

The Music Modernization Act database is still accepting authorized data sources. We're already approved.

Macro
Labels gatekeeping the wrong direction.

The opening for a sovereign, on-device, federated alternative is wider in 2026 than it has been since 2008.