KimiShip
Claude-powered social content workspace.
Claude writes. KimiShip stores, reviews, and schedules.
How it works
- Claude writes
You describe your idea in chat. Claude turns it into a multi-platform draft in your voice.
- KimiShip stores
Drafts are saved to your workspace with brand context, not scattered in chat history.
- You review
Open the draft in your browser. Edit, approve, or ask Claude to revise.
- Schedule & publish
Planned module — not yet live
Why KimiShip is different
- Your voice, not a template
Claude learns your brand from your stored brand profile. No viral-content slop.
- Claude is the brain
KimiShip adds no text LLM API of its own. Optional images use your own OpenAI API key.
- Human-reviewed workflow
Every draft needs your eyes before it goes anywhere. No autopilot posting.
- One idea, many formats
LinkedIn long-form, Instagram caption, X thread — from one prompt, in one session.
Platform coverage
Drafts today. Scheduling and publishing are planned modules.
- TikTok
- X (Twitter)
Trust & data ownership
- WorkOS auth
Enterprise-grade authentication. Your account is isolated from other workspaces.
- Owner-scoped data
Your drafts and brand profile are stored under your owner ID. No cross-tenant reads.
- Audit log
Every write action is logged. Draft content is never stored in the audit trail.
- No own text LLM API
KimiShip does not call a text generation model. Claude is the only writer; OpenAI images are BYOK and optional.
KimiShip is an early product. Drafting, brand context, and review are live. Calendar, scheduling, publishing, and optional BYOK images are rolling out module by module.
Try the app