Stage 01
Queued
Only metadata is stored: platform, scheduled time, job ID. Your content is not in the queue.
Publish is the outbound layer for everything Konstant Studio produces. Unlike most publishing tools, your content does not live here. It passes through.
The insight
When a job is queued, only the metadata is stored: platform, scheduled time, job ID. The actual content is fetched at execution time and purged immediately after posting. Nothing persists in the scheduling layer. Your content lives in your workspace. The scheduler does one job: deliver it at the right time to the right place.
Content never persists
Stage 01
Queued
Only metadata is stored: platform, scheduled time, job ID. Your content is not in the queue.
Stage 02
Execution
At the scheduled moment, the actual content is fetched from your workspace.
Stage 03
Posted
Delivered to the platform. The content is purged from the delivery layer immediately after.
queued → { platform, scheduled_at, job_id } // metadata only
execution → fetch(content_ref) → POST(platform) // content in flight
posted → purge(content_buffer) // delivery layer is emptyHow the scheduler works
Per-account scheduler instances
Your queue is isolated. Other accounts cannot see or affect it.
Metadata-only queue
Content is fetched and purged at post time. Nothing persists in the scheduling layer.
Platform OAuth managed
Connect once. Tokens are maintained automatically.
Admin view
Calendar, queue status, connection health — one surface.
What Publish handles
Social
Instagram, TikTok, LinkedIn, Facebook, and more.
Podcast feed
Distribution to your podcast hosting and feed surfaces.
Email & newsletter
Scheduled delivery through your sending stack.
Scheduled & instant
Send now, or queue for the right moment.
Inbound normalisation
Every platform’s webhook arrives in the same format.
Same locked price. Every tool, as it ships.
Join as a founding member →