Public, private, and scheduled releases on SoundCloud

How Rollout handles visibility and timing: public or private tracks, and true scheduling by holding a track and uploading it the moment it’s due — never early.

Here's exactly how Rollout controls who can see a track and when it goes live, and why it works the way it does.

Visibility: public or private

SoundCloud tracks are either public or private — those are the only two states the API exposes (there's no separate "unlisted"). A private track is only reachable by its secret link. You choose the setting per track in Rollout before publishing.

Scheduling: hold-and-upload

SoundCloud has no native "publish later" setting in its API. Rollout handles scheduling a more reliable way: you set a Release date, and Rollout holds the finished track and uploads it the moment the date is due — so it appears as a fresh release, and is never posted early. A background worker does this automatically even if you never open the console. See how to schedule a release.

Good to know

• Dates are interpreted in UTC.
• Rollout keeps an idempotent ledger, so a track is never double-posted.
• Rollout distributes to your own account and never manipulates plays, reposts, or engagement.