Leave your email now for launch access and early trial credits.Join waitlist
  • DraPub
DraPub

Turn saved ideas into a publishing rhythm.

Private beta seats open in batches. Leave your email to get early access to the content memory, draft, review, and publishing workflow.

Role
Primary channel

No card required. No spam.

raPub

Grow yourX accountwithDraPub's IP Memory Brainbuilt from yourNotion

Let your content publishing rhythm keep up with what you save and think through.

Role
Primary channel

No card required. No spam.

User pain points

The real blocker is not ideas. It is shipping them.

Sources scatter, topics stall, channels demand rewrites, and handoff still depends on manual cleanup.

Sources scatter

Notes, clips, docs, and transcripts live in separate tools, so reuse starts with hunting.

Topics stay ad hoc

Saved material still needs angles, proof, and a clear reason to become a draft.

Channels need rewrites

One idea has to become WeChat, X, Xiaohongshu, newsletter, and short-video copy.

Assets slow the draft

Covers, scripts, outlines, and edits need prep before the work can ship.

Handoff stays manual

Review, schedule, publish, and performance notes still live across too many places.

Content memory and draft review

Turn scattered inputs into drafts you can trust

Build one loop from source capture to approval. Bring Cubox, Mubu, Feishu, Obsidian, web clips, transcripts, local agents, review gates, and publishing adapters into one traceable workflow.

Source pack

Properties
In review
Ops
R
E
L
D
Docs & links
Topic brief
Source notes
Milestones
Source review 100%
Draft package10/10
Channel staging 13/53

Collect source material once

Keep notes, clips, outlines, documents, and transcripts as reusable source packs without moving your whole workflow into a closed platform.

Move approved drafts forward

Generate platform-specific drafts, check them against source evidence, then hand off only the versions that are ready.

Needs review
New notes from Cubox are ready for topic selection Today
At risk
A draft is missing source evidence before approval Today
Ready
Two approved drafts are ready for channel staging Yesterday

Input adapters

Bring notes, clips, docs, transcripts, and files in.

Cross-source memory

Keep source evidence and reusable context together.

Review queues

Track generated, revised, approved, and staged drafts.

Channel handoff

Send each approved version onward with platform notes.
Agent remote capability

Install DraPub where your agents already work

Install once, then Codex, Claude Code, Cursor, or any MCP-capable agent can call DraPub generation, review, and delivery workflows through the same remote capability.

  • Add it like an Agent Skill without rebuilding your local workspace.
  • Remote draft and review capability is provided through the DraPub API.
  • One key can be reused by Codex, Claude Code, Cursor, and MCP clients.
Install DraPub Agent Skill
$npx skills add drapub-labs/drapub-skills$export DRAPUB_API_KEY="dp_live_..."
Copy for Codex

Install DraPub Agent Skill in this project with `npx skills add drapub-labs/drapub-skills`, then help me set DRAPUB_API_KEY so Codex can call DraPub remote draft, review, and delivery workflows.

Who it is for

Made for people who already collect serious material

DraPub is not for blank-page content farming. It is for creators and teams that already have notes, sources, opinions, and a publishing habit to protect.

Research-heavy creators
Local-first operators
Platform-native publishing
Human-reviewed output
Individual IP operators
Turn saved reading, research, and daily notes into a steady publishing queue.
Technical creators
Use Codex, Claude Code, Cursor, and MCP without losing source evidence or review control.
Small content teams
Share source packs, draft queues, review decisions, and platform handoff in one workflow.

What DraPub is, and what it is not

DraPub is built around a narrow promise: turn saved material into reviewable, platform-ready drafts without losing source evidence or human control.

Read the help docs
Is DraPub another AI writing app?

No. The product starts from existing content assets: clips, notes, docs, outlines, transcripts, and local files. The goal is not a blank-page prompt, but a traceable draft package that can move through review.

Why does it focus on drafts instead of auto-publishing?

The first version is intentionally review-first. DraPub prepares platform-specific copy, source evidence, risk notes, and handoff details, then keeps a human decision before anything leaves the system.

Who should use it first?

It is for individual IP operators, technical creators, and small content teams that already collect serious material and need a repeatable path from source memory to publishable drafts.

How is this different from YouMind, NotebookLM, Postiz, or Buffer?

YouMind and NotebookLM are strong at collecting and understanding material. Postiz and Buffer are strong at scheduling and publishing. DraPub sits in the middle: source assets become multi-platform drafts with review, voice, and handoff intact.

Can local agents still be part of the workflow?

Yes. DraPub keeps CLI, MCP, Codex, Claude Code, Cursor, and local workers as first-class paths. The SaaS layer adds accounts, billing, shared review, and cloud execution when they are useful.

What do credits pay for?

Credits are reserved for metered automation such as agent runs, draft generation, platform rewriting, media work, and future cloud workers. Manual review and local workflow structure remain the product center.