Publish
Host the public home, media library, live room, and evergreen feature pages that fans and agents can understand.
fanful.net/features
Fanful features for an owned creator business.
Fanful brings the creator site, media library, shop, memberships, lessons, live moments, email, fan CRM, and analytics into one product surface. The overview below links to feature guides while staying clear about what is available now and what is still being hardened.
Earn
Connect shop, memberships, lessons, and paid access to the same listener account and admin record.
Operate
Give creators practical email, CRM, analytics, moderation, and admin tools without scattering data across vendors.
Availability
Working in the current Laurel/Fanful stack, with platform polish still expected as more artists come on board.
The first useful slice exists, but the reusable Fanful version still needs product hardening before broad selling.
Designed as part of the Fanful product direction, but not something to promise without checking the roadmap or detail page.
Feature guides
The product map fans experience as one creator home.
Broadcast rooms
Live stream
Schedule an owned room for a premiere, recital, rehearsal, replay, or subscriber-first event without sending fans to a disconnected platform.
Fan value
Fans get one clear place to show up, see the room status, and return when a replay or follow-up is ready.
Creator value
Creators can manage event state, provider metadata, visibility, and moderation from the same admin surface as the rest of the site.
Current proof
- D1-backed /live room schedule and state
- admin live controls
- Cloudflare Stream metadata path
Production event playbooks and reusable pricing boundaries are still being shaped.
Community conversation
Live chat
First-party live-room and community chat keep event conversation attached to the creator site instead of splitting it across Discord, YouTube, and comments.
Fan value
Fans can read, post, and return to the same creator-owned thread around a live moment.
Creator value
Creators can connect room chat to sign-in, moderation, community channels, and future member access.
Current proof
- signed-in live notes
- community channels on /live
- admin moderation and realtime socket foundations
The next layer is packaging reusable channel controls for more artists and agent-safe operations.
Creator commerce
Shop
Sell physical items, digital downloads, support items, and creator offers from a shop that shares fan identity with the rest of the site.
Fan value
Fans can buy from the creator without losing the thread between purchases, memberships, media, and account history.
Creator value
Creators get D1-backed inventory, download metadata, checkout records, and admin commerce visibility.
Current proof
- public /shop with feature flags
- Stripe Checkout and Venmo fallback path
- admin inventory and purchase rows
Refunds, fulfillment exports, and multi-artist Stripe Connect remain future platform work.
Media library
Upload music and video
Publish owned audio, artwork, short video, and release material into the same place fans already use for listening, buying, and joining.
Fan value
Fans can listen, browse, and return to media without jumping between file hosts and social posts.
Creator value
Creators can upload authenticated media into R2, store metadata in D1, and keep provenance review visible.
Current proof
- authenticated admin uploads
- R2-backed media serving with byte ranges
- media provenance fields and review queue
Large-file direct-to-R2 multipart upload, processing, and richer video handling are still future work.
Paid fan access
Memberships
Create recurring supporter tiers and use membership state as the backbone for protected media, live access, and account benefits.
Fan value
Fans can understand what their support unlocks and see the account state attached to that support.
Creator value
Creators can connect Stripe subscription records, D1 membership rows, and centralized entitlement checks.
Current proof
- recurring supporter tiers
- Stripe subscription checkout and webhook recording
- account membership state and media entitlements
Plan packaging and creator-facing entitlement controls still need clearer reusable UI.
Teaching offers
Lessons and bookings
Let fans move from discovery to lesson interest, booking requests, class packs, and paid teaching offers inside the creator site.
Fan value
Students can request learning time without treating lessons as a separate business from the artist relationship.
Creator value
Creators can keep teaching demand, checkout intent, fan context, and admin follow-up near the rest of their operations.
Current proof
- public lessons surface
- lesson admin data
- checkout integration path for teaching offers
Calendar automation, class-pack fulfillment, and polished booking operations remain follow-ups.
Audience relationship
Email and fan CRM
Capture confirmed subscribers, send careful campaigns, receive inbound replies, and measure email usage without handing the fan relationship to a generic newsletter tool.
Fan value
Fans can hear from the creator through consented email instead of depending on social-feed luck.
Creator value
Creators can draft, preview, broadcast, review replies, and track usage from the admin surface.
Current proof
- double opt-in newsletter flow
- campaign drafts, previews, and broadcasts
- inbound message rows, reply state, and usage ledger
Segmentation, deliverability provider choices, and full CRM workflows are still being hardened.
First-party insight
Analytics
Show creators useful source, playback, listener, conversion, email, and activity signals without making Google Analytics the system of record.
Fan value
Fans get a site that can remember progress and improve experiences without unnecessary ad-tech assumptions.
Creator value
Creators can see what is working across listening, subscribers, purchases, memberships, lessons, replies, and recent activity.
Current proof
- /admin/analytics
- first-party analytics event stream
- listener playback state and domain-table summaries
The dashboard should stay directional and privacy-aware while native-player event detail continues to improve.
Overview table
Feature paths for humans and agents.
| Feature | Status | Detail URL | Creator job |
|---|---|---|---|
| Live stream | In progress | /features/live-stream | Creators can manage event state, provider metadata, visibility, and moderation from the same admin surface as the rest of the site. |
| Live chat | Available now | /features/live-chat | Creators can connect room chat to sign-in, moderation, community channels, and future member access. |
| Shop | Available now | /features/shop | Creators get D1-backed inventory, download metadata, checkout records, and admin commerce visibility. |
| Upload music and video | In progress | /features/upload-music-and-video | Creators can upload authenticated media into R2, store metadata in D1, and keep provenance review visible. |
| Memberships | Available now | /features/memberships | Creators can connect Stripe subscription records, D1 membership rows, and centralized entitlement checks. |
| Lessons and bookings | In progress | /features/lessons-and-bookings | Creators can keep teaching demand, checkout intent, fan context, and admin follow-up near the rest of their operations. |
| Email and fan CRM | In progress | /features/email-and-fan-crm | Creators can draft, preview, broadcast, review replies, and track usage from the admin surface. |
| Analytics | Available now | /features/analytics | Creators can see what is working across listening, subscribers, purchases, memberships, lessons, replies, and recent activity. |
Product discipline
One fan relationship, not a pile of point tools.
Fanful should be useful because the modules share account state, admin context, and honest availability boundaries.
- Each feature should strengthen the same owned fan relationship instead of creating another detached tool.
- Fanful copy should separate working product from platform hardening and roadmap intent.
- Fan data should map to real creator jobs: listening, buying, joining, learning, replying, and returning.
- Human pages and markdown mirrors should tell the same story so agents can reason about Fanful without scraping fragile layouts.