PulseGrid

Overview

The workflow runs from local track analysis through set planning to transition review. A natural-language brief can shape track order, transition points and mixing automation; users can preview planned transitions before Auto Play, edit cues or take manual control. That makes PulseGrid useful for rehearsal as well as automated playback, while leaving room for the DJ to correct the plan.

The project releases its original source code under the MIT License unless a file states otherwise. Its documented setup requires a local Node.js API, Python and audio tools, so simply hosting static files is not enough. Docker is documented for Mac, Windows and Linux, with a native installation option for macOS.

Key features

Track analysis and set planning

PulseGrid analyzes uploaded tracks for BPM, key, beatgrid, waveform, energy, drops and musical structure. The set planner turns a natural-language brief into an order, transition-specific Cue 8 to Cue 5 handoffs, and EQ, Filter, FX and Crossfader automation. Set duration is a soft goal: if the available tracks do not support the requested length, PulseGrid prioritizes safer structures and transitions instead of forcing the duration.

Structure detection is heuristic and can misread half-time BPM, complex live intros, weak downbeats or ambiguous drops. DJs should review transition plans rather than treating analysis as authoritative, particularly when those musical details matter.

Mixing and transition review

Two decks, waveforms, Sync, up to eight Hot Cues per track, loops, EQ and FX support manual adjustment alongside automation. Users can audit planned transitions before Auto Play, then edit cues or take control themselves. Browser master-output recording is also included. That combination suits DJs who want to rehearse and refine a set, but the project cautions that browser key shifting and DSP do not match dedicated DJ hardware or audio engines.

Local library and privacy

Supported formats include WAV, MP3, AIFF, M4A, AAC, FLAC, OGG and Opus, with a 600 MB limit per local upload. Music, uploads, analysis jobs and results run locally, and tracks are not sent to an external PulseGrid server. Some interface state, cues, ratings and tags may be kept in the current browser's local storage; libraries do not sync automatically across devices or browser profiles. That favors privacy and local control over a library that follows the user between machines. The project describes local data handling but does not state security certifications or compliance attestations.

Pricing

PulseGrid is free, with a free plan. There are no paid tiers or seat terms to weigh in the stated pricing model. The practical trade-off is the setup and local-resource burden: users need the documented API, Python and audio tools, while each uploaded file is capped at 600 MB.

Platforms

PulseGrid is listed for Linux, macOS, Windows, self-hosted use and the web. Docker is documented for Mac, Windows and Linux, while native installation is documented for macOS. Chrome or Edge is recommended for first use because those browsers provide the most complete Web Audio and AudioWorklet support. A browser interface therefore does not mean a static web-page deployment will suffice.

Who it's for

PulseGrid fits DJs who want to analyze their own tracks, draft sets from a natural-language brief, and rehearse or perform transitions with automation they can edit. It is also a reasonable fit for people who prioritize local processing and are comfortable setting up software dependencies. Look elsewhere if you need automatic library sync, third-party music-service integration, or processing equivalent to dedicated DJ hardware.

Pros and cons

• Pro: Analysis, set planning, transition review and dual-deck mixing sit in one workflow, reducing the need to move between separate planning and rehearsal tools.
• Pro: Local processing keeps tracks off an external PulseGrid server, a meaningful advantage for DJs who do not want to upload their libraries.
• Pro: Transition previews, editable cues and manual control let users inspect or override automation before relying on it.
• Con: Heuristic structure detection can misread several challenging musical patterns, so transition plans need human review.
• Con: Libraries do not sync automatically across devices or browser profiles, limiting continuity for DJs who move between setups.
• Con: Setup requires local services and audio tools, and the 600 MB per-file cap may constrain large recordings.
• Con: Browser key shifting and DSP are not equivalent to dedicated DJ hardware or audio engines.

Alternatives

For a broader comparison, see AI DJ Software. Choose CortexDJ instead if you want a free home-use plan for up to two computers with analysis, AI auto-mix, mashups, live decks, mix rendering and export to rekordbox and Serato. djay is the alternative to consider if you want apps across Android, iOS, macOS and Windows, with a free download and an optional PRO subscription for advanced features. Offtrack offers a free plan across Android, iOS and macOS; its listed facts do not establish a closer fit for PulseGrid's planning workflow.

SetPrep may suit DJs focused on preparing mixes on macOS or Windows: its free plan allows three mixes per month, while Pro Monthly costs 5.99 GBP per month for unlimited mixes. AuraJam is a web option with a free plan that allows five exports a day, marks exports, and leaves on-device tools unmetered; its Pro plan costs 9.99 USD per month for unlimited exports. automixer.ai may be a better fit for project-based mixing in a web app: its free plan allows three projects, six tracks per project and five exports per month, with 1 GB storage and MP3 320kbps exports.

CRATELAB is a freemium alternative for web, Windows and macOS. Mixbridge is a free alternative for iOS and web.

Verdict

Choose PulseGrid if you want a free, local-first workstation for analyzing your tracks, building a set and reviewing editable transitions without sending music to an external PulseGrid server. Its strongest reason to choose it is the joined-up path from analysis to rehearsal and mixing; its strongest reason to look elsewhere is the combination of setup demands, unsynced local libraries and browser-processing limits. DJs who need dependable hardware-equivalent processing or a library that travels automatically between devices should choose another approach.