Everything MixLens publishes, in one place.
How the analyzer works, how to wire it into your stack, what we just shipped, and the trust posture. New surface? Start here.
Learn the product
Producer-readable explainers for everything MixLens computes and why.
Task-based guides for reading graphs, choosing fixes, preserving tone, and using the app as a workflow instead of a blog archive.
Five things we check on every mix, what they mean, what the bands signify, and how the per-platform readiness matrix is computed.
Exact DSP, library versions, citations for every threshold. Includes a live MixLens-vs-FFmpeg loudnorm comparison table.
Launches, case studies, and opinion pieces. The blog stays useful, but the learning center now owns the evergreen workflows.
Plug into your stack
Wire MixLens into Discord, Claude Desktop, Cursor, your CI runner, your DAW export folder.
Bearer-token API, signed webhooks, desktop CLI with watch-folder, MCP server for Claude / Cursor, Discord relay example, CI gate.
Generate and manage long-lived tokens for desktop apps, scripts, and third-party clients. Reveal-once, hashed at rest.
HMAC-signed POST delivery on analysis.complete / render.complete, retried with exponential backoff, every delivery logged.
Keep up
What we've shipped, what's next, what to email us about.
Every meaningful change with a producer-readable lead and an optional under-the-hood line. Updated as we ship.
Free forever to analyze. Pro is unlimited renders + API access. Studio is hand-onboarded for multi-engineer studios.
Two analyzed mixes side-by-side. Useful when A/B-ing arrangements or revisiting an old session.
Trust + safety
How we treat your audio. The boring stuff lawyers read.
No training on uploaded audio. Retention 24h on Free / 30d on Pro. Sub-processor list, GDPR / CCPA rights, deletion in 30 days.
Your audio stays yours; our scores aren't guarantees; plain-language IP + acceptable-use + billing.
Measurement-drift policy: if MixLens disagrees with another compliant meter by more than 0.2 LU, we treat it as a bug. Email hello@mixlens.io.
Tell us what's missing.
If you came here looking for something and didn't find it, we consider that a docs bug — email hello@mixlens.io and we'll add it.