All features

Scheduling & reliability

Scheduled means published.

Timezone-aware schedules, quiet hours and daily limits on top of durable queues that survive restarts, respect rate limits and never lose a paid job.

Get startedSee all 20 features
MTWTFSSQUIET HOURS
01

Timezones done right

Schedules are stored with their timezone and survive daylight-saving changes. Your 9am stays 9am.

02

Quiet hours and blackout dates

Set them once per account. Nothing publishes while your audience sleeps or on days you choose.

03

Capacity you can count on

Kairo Post only promises slots it can actually deliver within X's limits.

04

Durable by design

A database outbox, worker heartbeats and dead-letter review mean restarts don't lose work.

Capabilities

Everything in scheduling & reliability.

StagesFoundationCore platformLaunchFirst releaseAutopilotAI autopilotGrowthTeams & growthExploringUnder evaluationNeeds X approvalEnabled only once X grants accessStages show the order we're building in, not release dates.

Calendar & scheduling

Publish at chosen times while respecting capacity.

  • Schedule a post

    Foundation

    Choose when a draft should publish.

  • Timezone-aware schedules

    Foundation

    Respect the customer's local publishing time.

  • Reschedule safely

    Foundation

    Move a post without leaving a ghost job.

  • Cancel queued posts

    Foundation

    Stop a scheduled post before publishing begins.

  • Recurring content slots

    Autopilot

    Define slots such as weekday mornings.

  • Per-account daily limits

    Launch

    Control how frequently each account posts.

  • Quiet hours and blackout dates

    Autopilot

    Avoid publishing at unsuitable times.

  • Missed-slot policy

    Launch

    Handle downtime without flooding an account afterward.

  • Capacity-aware admission

    Launch

    Avoid promising more publishing capacity than is available.

  • Evergreen rotation

    Growth

    Reuse approved ideas after a suitable cooldown.

Redis, jobs & reliability

Make background work survive failure and scale fairly.

  • Live Redis connectivity

    Foundation

    Prove that API and worker can reach the real Redis service.

  • Durable database outbox

    Foundation

    Avoid losing jobs between saving data and queueing work.

  • Separate job queues

    Launch

    Keep slow images from delaying payments or publishing.

  • Safe retry rules

    Foundation

    Retry transient failures without repeating public side effects.

  • Dead-letter handling

    Foundation

    Keep exhausted jobs visible and recoverable.

  • Worker leases and heartbeats

    Foundation

    Detect stalled jobs and crashed processes.

  • Global and account rate limits

    Foundation

    Respect X limits across every worker replica.

  • Fair scheduling

    Growth

    Stop one heavy customer monopolizing workers.

  • Recovery and graceful shutdown

    Foundation

    Resume safely after deploys and service outages.

  • Queue observability

    Foundation

    Know which queue is slow, stuck or expensive.

Previous

Composer & publishing

Write posts, threads and polls. Publish exactly once.

Next

Campaigns

Coordinate launches across accounts.

Your next post has a moment.

Connect an account, describe your voice and let Kairo Post find it.

Get startedHow pricing works