Tell it.Drohp it.
Drohp gives Claude and ChatGPT the power to ship real links for creators. Drop pages, presales, fan gates, QR codes, ticketed events, whole sites. You type a sentence. Your assistant types the rest. The link is live before the post goes up.
Switch assistants tomorrow. Your workspace, your data, and your live URLs come with you.
14 seconds. No browser opened. No template chosen.
Tasha drops merch.
She asked Claude for a presale page with a wallet pass for the first 100 buyers. Approved it from her phone in the Uber. The link hit her stories before she got home.
Kai runs a music newsletter.
He drohped a personalised link-in-bio that shows the closest tour date by city. One link. Sixteen tour stops. Zero spreadsheets.
Maya is a fashion creator.
Her last collab needed an RSVP gate, a $1 pre-auth, and a private gallery for buyers. She typed it. Claude shipped it. She posted it.
None of them opened a tab.
You change assistants. Your work doesn't.
Connect any MCP-capable assistant. Move when you want.
Your workspace stays put. Your live links keep resolving. Your Stripe stays connected. Your tables keep collecting rows.
The assistant is a renter. Drohp is the lease.
Everything your assistant needs to ship a real link.
Claude writes the HTML.
No block library. The agent writes the page source directly.
Many pages, one publish.
Atomic publishing. Shared chrome. Site-scoped sessions.
QR for any URL.
URL, vCard, WiFi, wallet pass, deep links. Print-ready.
Tables that outlive chats.
Auto-provisioned schemas. Public IDs. No enumeration.
Your Stripe, your money.
Stripe and Razorpay on your own account. Drohp orchestrates.
Products, discounts, wallet passes.
Shopify sync, abandoned cart recovery, digital delivery.
Slots, calendars, confirmations.
Time-slot reservations the assistant can offer in chat.
Email, SMS, WhatsApp, fired.
Rule-based and ad-hoc, two-way comms supported.
Scans, conversions, attribution.
Read-only telemetry. Pipe it into your own warehouse.
Ten thousand codes at once.
Bulk generation, folders, scheduling, routing, pixels.
Storage built for assistants.
Signed URLs, image transforms, PDFs, wallet assets.
Custom domains, white label.
Wallet certs, sender identities, social accounts.
One brand, many outlets.
Per-venue overrides for messaging and payments.
Workspaces, teams, billing.
Role-scoped access, audit log, config rollback.
Claude writes integrations too.
Sandboxed JS extensions for whatever isn't supported yet.
Built for the way creators actually ship.
Brief in chat. Ship in chat.
No tabs, no logins, no drag-and-drop builders. The assistant is the editor.
Your stack stays yours.
Stripe, Shopify, Notion, Sheets, Mailchimp, Klaviyo connect to your own accounts. You own the receipts.
Your name on every link.
Custom domains, white-label sender identities, Apple and Google wallet certificates. drohp.link is the default, not the limit.
Roll back anything.
Every page, code, product, and rule keeps its last 10 versions. One call rewinds the link without breaking the QR codes already in the wild.
Drohp speaks creator.
A week in real links.
RSVP page for the streetwear drop.
Tour-stop landing pages, one per city.
Fan gate for the unreleased EP.
Behind-the-chair booking link for the beauty drop.
Made in chat. Not a single tab opened.
Credentials never touch your assistant. When Drohp connects your Stripe, your Shopify, or your Mailchimp, the tokens land on our servers over TLS, encrypted at rest, and stay there. Your assistant only ever sees a connection ID.
Pages run sandboxed under a strict manifest. Tables can't be enumerated. Sessions are server-signed. Rate limits are server-enforced. The assistant gets to be creative; the platform stays in charge.
Real questions. Honest answers.
01What does "drohp a link" actually mean?
You ask Claude or ChatGPT to make something. A presale page, a fan gate, a QR for the merch table, a whole site. Drohp gives your assistant the tools to actually publish it. The output is a real, shareable URL. That's the drohp.
02Do I need to know how to code?
No. You don't even open a browser. You type to your assistant the way you'd brief a friend, and Drohp handles the rest: the page, the form, the database row, the payment link, the notifications.
03Which assistant does this work with?
Anything that speaks MCP. Today that's Claude and ChatGPT. Tomorrow it's whatever you switch to. Drohp is the workspace; your assistant is the keyboard.
04What if I switch from Claude to ChatGPT mid-campaign?
Your live links keep resolving. Your fan list keeps collecting. Your Stripe stays connected. You point the new assistant at your Drohp workspace and it picks up where the last one left off.
05Where do my pages live? Can I use my own domain?
Pages live at drohp.link/... by default, which is fine for a quick drop. When you want your own URL (shop.tasha.fm, kai.tour, mayadrops.co), you connect the domain inside Drohp and your assistant points pages at it. White label is supported from day one.
06Can I plug in my own Stripe, Shopify, Mailchimp?
Yes, and you should. Money lands in your Stripe account, products sync from your Shopify, fans subscribe to your Mailchimp. Drohp orchestrates; you own everything that matters.
07What if I drohp something I regret?
Every page, code, product, and rule keeps its last 10 versions. You ask your assistant to roll back, and the link points at the older version without breaking any QR codes already in the wild.
08Is fan data actually safe?
Credentials never touch your assistant's chat history. Connections live on Drohp's servers, encrypted. Pages are sandboxed with strict rules so one fan can't see another's row. Your assistant gets to be creative; the platform stays in charge.
09How do I get in?
Drohp is invite-only right now while we onboard a small first wave of creators. Email hello@drohp.link and tell us what you'd drop on day one. The more specific the brief, the faster the invite.
That's it. Go drohp something.