Skip to content

One suite, start to street date

Run your labelin one place.Your catalog. Your rules.

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 morning view — releases, tasks, and what changed.

The problem

Labels already have the work.They don't have a system.

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

The operating system

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.

  • Role-aware workspace
  • Release as the unit of work
  • Assets linked to people and tasks
  • Invite-only after the first admin
Sign in to the OS

Public catalog

The storefront

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.

  • Artists and albums from the live catalog
  • Publish flags, not a second CMS
  • Track previews when you attach audio
  • A working demo you can click through now
Open the catalog demo

Roster

Artists as first-class records.

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.

  • Profile imagery and galleries from the asset library
  • Structured genres, website, and social links
  • Tour dates with upcoming and past split
  • Create a release from the artist without leaving the page
Roster, bios, imagery, and every linked release.

Catalog

The release is the workspace.

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.

  • Type, format, catalog number, SKU, UPC, ISRCs
  • Tracklists you can order, copy, and attach audio to
  • Cover art and storefront gallery from the library
  • Lifecycle stays internal — the public site never sees Draft
Tracks, assets, workflow, and campaign work on one record.

Operations

A task command center, not a forgotten checklist.

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.

  • Org-wide task inbox plus work on each release
  • Due dates and notifications when work is assigned
  • Asset ↔ task links so files live next to the job
  • Dashboard widgets for what is due and what moved
Checklists from contract through launch, assigned and due.

Campaigns

Marketing stays on the release.

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.

  • Default campaign pack from timeline through post-release
  • Due offsets from street date, assigned by role when you can
  • Promo files attach to the task that needs them
  • Timeline polish and date-recalc are in active development — not pretended as finished
Campaign work lives on the release, not in a side tool.

Library

Masters, crops, one-sheets — findable.

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.

  • Artwork, photo, audio, video, and documents
  • Drag-and-drop upload on library and release
  • Display derivatives for speed; originals stay intact
  • Linked from artists, releases, and workflow tasks
Artwork, audio, video, and documents — linked where they’re used.

People

The label is a team, not a shared login.

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.

  • Role-based navigation and permissions
  • Messaging in the same system as the rest of the OS
  • Release presence with a clear editor when two people are in
  • Help guide in the sidebar for the first weeks
Roles, presence, and conversations in the same OS.

Publishing

The catalog you manageis the catalog they see.

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.

What you publish is what fans see — same artists, same releases.

And the rest of the desk

Built for how a label actually runs.

  • Artist records

    Bios, genres, socials, tour dates, galleries, and every release tied to the act.

  • Catalog & metadata

    Albums, EPs, and singles with catalog numbers, SKUs, UPC, ISRCs, and DSP genres.

  • Release tasks

    Templates from contract through launch. Assign people, set dues, attach assets.

  • Campaign on the release

    Marketing is a phase of the release — press, creative, outreach, launch — not a side app.

  • Asset library

    Artwork, audio, video, and documents in one library, linked to artists, releases, and tasks.

  • Team, chat, presence

    Roles, DMs, notifications, and who is on a release — so work doesn’t collide.

  • Publishing

    Toggle what goes live. The public catalog is the same roster and the same catalog.

  • Roles that match a label

    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

Built from inside the label, not outside it.

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

  • Fake testimonials
  • Invented usage numbers
  • Awards we have not won
  • Features that are still on the bench, sold as live

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

The questions everyone asks first.

Short. No brochure gloss.

What is SoundlotOS?

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.

Does it replace a DAW, DistroKid, or a distributor?

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.

Is my catalog uploaded to a public cloud by default?

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.

Who can sign in?

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.

What does the demo show?

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.

What is still being built?

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.

Open the system.

Walk the public catalog, or sign in to the operating system if you already have an account.