One suite, start to street date
SoundlotOS is the operating system behind the roster, the release, and the public site. Built from working inside an independent label — not from a generic project board with a music skin.
The problem
Spreadsheets for the catalog. Drive for the masters. A task app for the campaign. Slack for the decisions. A website that lags the actual release. SoundlotOS puts that stack in one operating system so a release has somewhere to live.
SoundlotOS
Dashboard for the label. Sign in required.
Artists, catalog, assets, release tasks, marketing work, team, messages, and publishing controls — the daily software of running a label.
Public catalog
What fans see. Powered by the same records.
Published artists and releases become a public catalog — pages, artwork, and track previews — without rebuilding the site for every street date.
Roster
Not a name in a cell. A page with the bio, the image, the socials, the dates, and every release attached — so A&R, marketing, and the public site are looking at the same act.
Catalog
An album is not a row. It is tracks, artwork, identifiers, pricing notes, comments, and the workflow that gets it out the door. Open a release and the work is already there.
Operations
New releases inherit workflow templates — contract, audio, artwork, metadata, distribution, marketing. Tasks have assignees, dues, status, and assets. The inbox spans the catalog so nothing hides on a buried tab.
Campaigns
Indie campaigns are street-date checklists. SoundlotOS treats them that way: a Marketing phase with press, creative, outreach, launch, and follow-up — visible as a timeline on the release you are actually shipping.
Library
The asset library is the file system the rest of the OS can see. Filter by type, artist, or release. Preview in place. Download the original when you need the master, not a thumbnail.
People
Directory by role. Direct messages. Presence on a release so two people don’t silently overwrite each other. Notifications when a task lands or someone @mentions you in comments.
Publishing
Publishing is a flag, not a rebuild. Mark an artist or release on catalog and the public site updates from the same record. Later, this architecture can grow into per-label domains. Today you can walk the experience in the demo.
And the rest of the desk
Bios, genres, socials, tour dates, galleries, and every release tied to the act.
Albums, EPs, and singles with catalog numbers, SKUs, UPC, ISRCs, and DSP genres.
Templates from contract through launch. Assign people, set dues, attach assets.
Marketing is a phase of the release — press, creative, outreach, launch — not a side app.
Artwork, audio, video, and documents in one library, linked to artists, releases, and tasks.
Roles, DMs, notifications, and who is on a release — so work doesn’t collide.
Toggle what goes live. The public catalog is the same roster and the same catalog.
Admin, Manager, A&R, Marketing, Designer, Legal, Artist, Viewer — each sees what they need.
Also in the OS today: imprint and SKU prefix settings, metadata CSV export for distribution, contract renewal tracking for Legal and Admin, and onboarding that walks a new label from name → first artist → first release. Full contract documents are on the roadmap — the current Contracts area is a renewal register, stated as such.
Why it exists
SoundlotOS is being designed around the actual problems of independent label work: keeping the roster straight, not losing masters, running a release without a scavenger hunt, and shipping a public site that matches what you just announced.
There are no customer logos to line up yet. When labels are on it, they will belong here. Until then, the honest proof is the software — and a catalog demo you can open.
What we will not put on this page
Next on the bench, called correctly: richer marketing timeline UX, recalculating campaign dues when a street date moves, and a proper contract studio beyond renewals.
Straight answers
Short. No brochure gloss.
An operating system for independent labels. It is the internal place to run roster, catalog, assets, workflows, and team work — and it can publish a public catalog from that same data.
No. SoundlotOS is for label operations: organizing the work around a release, not mixing audio or delivering to DSPs. It is built to sit beside the tools you already use for those jobs.
The operating system is the label’s workspace. Only artists and releases you mark as published appear on the public catalog. Internal status, unfinished assets, and unpublished work stay inside the dashboard.
The first account is the label admin. After that, teammates join by invite with a role assigned. There is no open public registration for the OS.
The demo is the public-facing catalog experience — artists, releases, and track previews — the kind of site a label can publish from SoundlotOS. Sign in to use the operating system itself.
The marketing timeline on a release is in place and being refined (street-date-aware labels, recalculating dues when a date moves). Contract tracking today is a renewal register, not a full contract studio. We don’t present unfinished work as shipped.
Walk the public catalog, or sign in to the operating system if you already have an account.