Authors keep 70%  ·  Sanitized copies protect your IP

Your workspace, shared.
Your IP, protected.

Once your workspace is built, optionally share a sanitized copy. Subscribers ask questions through their AI. You earn 70% of every paid ask.

One sanitized publish. Paid every time someone asks.

Share Mode keeps raw files local and publishes only the sealed copy you approve.

70%
Author rev share
0
Upfront cost
12-phase
IP-protection pipeline

Before you can Share, you need a workspace.

Most authors who Share also use Leapable for their own writing, research, and editing. Workspace mode is free.

Already using Leapable as a workspace?

Share

New to Leapable?

Start with workspace

From workspace to Share Mode in three steps

Build locally, sanitize deliberately, publish when you are ready.

Step 1

Build your workspace

Install the Leapable MCP server and point it at your PDFs, books, transcripts, or research. OCR, source parsing, and search preparation happen on our cloud GPU — your raw files never leave your drive.

Step 2

Sanitize & publish

One click runs the Creator Publish Sanitizer: 12 phases of PII redaction, filename anonymization, and provenance stripping. A cryptographically sealed copy, not your originals, is what the Library receives. The 12-phase IP-protection pipeline stays between your workspace and every subscriber.

Step 3

Earn on every paid ask

Set a price per ask, a monthly subscription, or both. Keep 70%. Stripe deposits monthly. Watch Workbench light up with the questions readers actually ask.

One split. For everyone.

No volume tiers. No hidden fees. No enterprise carveouts. The rev-share you see today is the one you'll get on ask 10 and ask 10,000,000.

70%
Author share

Per ask. Per subscription. No cap, no tier, no asterisk.

$0
Upfront cost

No monthly platform fee. If you earn zero, you pay zero. We only win when you do.

Monthly
Payouts

Stripe Connect deposits directly to your bank. No invoicing. Tax forms handled.

The infrastructure you'd need to build — and never will

Every author who tries to do this alone ends up running six vendors, two compliance audits, and a Stripe migration. Here's what you skip.

OCR & source processing pipeline
PDFs, Office, images, transcripts — handled on GPU
$25,000 build
HNSW vector index + cross-encoder reranker
The quality layer most RAG products skip
$40,000 build
Creator Publish Sanitizer (12-phase CPS)
PII redaction, filename anonymization, sealed upload
$60,000 build
MCP distribution to every major AI client
Claude, Cursor, ChatGPT, VS Code, and 5 more
not available elsewhere
Credits, subscriptions, Stripe Connect, tax forms
Billing rails for Share Mode
$30,000 build + $15k/yr
Share analytics in Workbench
Asks, revenue, churn, top questions
$10,000 build
Build-it-yourself cost
~12 months, at least two engineering hires
$165,000+
$0 today
Built for authors who protect their IP

Publish the knowledge. Keep the source.

Readers ask; your AI-ready knowledge answers. They never see your PDFs, your filenames, your notes, or your folder structure. That's not a policy — it's how the pipeline is built.

Mandatory PII redaction

Every publish runs Presidio-powered detection plus a zero-residue regex sweep for emails, phone numbers, SSNs, credit cards, and person names. Anything that slips through blocks the publish — there's no opt-out.

Filenames anonymized

Your Q3-draft-FINAL-v7.pdf becomes doc_8a3f…. File paths, hashes, titles, authors, and headings are stripped or nulled before the sealed copy is uploaded.

Sealed & verified

The sanitized copy is hashed (SHA-256), bundled with a manifest, uploaded to private storage, and re-verified server-side. Your raw vault is never transmitted.

No download path

Subscribers receive answers and anonymized excerpt IDs — not files, not pages, not exports. There is no API to retrieve the original source documents.

Identity tables dropped

Audit logs, annotations, saved searches, workflow state, user records, approval chains, and webhook configs are scrubbed from the sealed copy. Subscribers get the knowledge, not the history.

Originals stay local

The Leapable MCP server runs on your machine. The canonical vault — the one with your file paths, provenance, stored excerpts, and source metadata — never moves. Only the sealed, redacted copy goes to market.

Source citations and the source detail metadata are full-fidelity for your own local workflow. They're deliberately stripped from Share Mode vaults — because readers are paying for answers, not your files.

Everything you need to monetize knowledge

The platform, the pipeline, the payout rails. One install.

Share analytics

Live analytics on asks, subscribers, revenue, and churn. See the exact questions your audience asks, then decide what to improve or publish next.

AI-agent distribution

Your knowledge is instantly askable from Claude, Cursor, ChatGPT, VS Code, Windsurf, Zed, Continue, JetBrains, Amazon Q — any MCP-compatible client. Not available anywhere else.

Stripe Connect payouts

Monthly payouts straight to your bank. No invoices, no chasing, no wondering where the money is. Tax-compliant by default.

Pricing you control

Per-ask credits (0-20 credits per question), a monthly subscription cap, a public subscription, or all three. Free tier available if you want reach over revenue.

What can you upload?

Any knowledge source library works. Our pipeline handles the rest.

Books
Transcripts
Research Papers
Course Materials
Legal Documents
Medical Knowledge

Install Leapable to prepare Share Mode vaults

Use the Leapable MCP Server locally to add your document Sources, run OCR, prepare search, and test answer quality. Build many vaults, one per knowledge domain, and share the ones your audience wants. Each Share Mode vault gets its own subscription offer and price.

Local processing — your raw files never leave your machine

Cloud GPU for PDFs — included in your credits

Quality gate — test search before going live

Preview in any AI client — Claude, Cursor, VS Code

Try Share Mode

$0 upfront. Keep 70%. Your files stay yours.