IsMyGirl Clone Features: The Managed Creator Platform in Full
Most creator platforms hand a creator a dashboard and wish them luck. The managed model works differently - you recruit talent, run the accounts, and take a defined share. Every feature below exists to support that: a roster you control, three-way splits per creator, staff-operated messaging, and approval-gated payouts.
Request a Live Demo →See PricingFeature Set by Role
Both halves ship together: the consumer product fans and creators use, and the operational layer your team runs it from. That second half is the part most creator scripts leave to you.
Fan
Everything a paying member does, across one unified app, the browser and mobile.
- Per-creator subscriptions with free previews or fully gated access
- Pay-per-view unlocks on posts, media and message attachments
- Wallet top-ups and stored balance, so repeat purchases skip checkout
- One-to-one and group messaging, tips and gifts against any creator or post
- Public live sessions with chat, plus private live on request
- Paid audio and video calls, shoutout requests and creator storefront orders
Creator
The roster's own view: publish, price, earn, and see the split in real time.
- Posts, stories, reels, comments, likes and saves across image, video, audio and files
- Per-creator pricing on subscriptions, unlocks, messages, live and calls
- Storefront listings with coupons and time-boxed promotions
- Donation and goal-based campaigns, plus paid shoutout fulfilment
- AI personas answering in the creator's voice, with retained session history
- Earnings, engagement and content performance visible against their own split
Operator and staff
Scoped roles, so a chat operator, talent manager, finance approver and owner each see their remit and nothing more.
- Roster management: add creators, set each split, manage status and restrictions
- Verification review with provider callbacks and a retained decision record
- Managed messaging on a creator's behalf, with templates, saved lists and scheduling
- Moderation queues, report intake and takedown workflow, every decision attributable
- Payment provider configuration, with more than one gateway running at once
- Approval-gated payout runs with reconciliation records
The mechanism that defines this product is the split engine. Every monetized event - subscription, unlock, tip, message, live session, call, storefront order, campaign, paid placement - is calculated against that creator's configured split at the time of the transaction and written to one ledger. A $9 unlock and a $200 call are accounted for identically, which is why month-end is a report rather than a spreadsheet exercise.
Managed Platform vs Generic Creator Script vs Custom Build
What a managed operator actually compares, judged on the tooling a roster business needs rather than on feature counts.
| What a managed operator compares | Generic creator script | Miracuves IsMyGirl Clone | Custom development |
|---|---|---|---|
| Time to launch | Unknown / DIY | 6 days, production-ready | 3-9+ months |
| Source-code ownership | Often limited or encrypted | Full, no per-creator licence | Usually yes |
| Creator roster management | Absent; managed in spreadsheets | Built in - onboarding, status, per-creator settings | Custom build, extra cost |
| Revenue split engine | Flat platform fee at best | Three-way splits, per creator, across every revenue type | Possible, but slow and costly |
| Payout controls | Manual transfers outside the system | Approval-gated runs with an attributable record | Depends on scope |
| Staff permission model | Single admin login shared by the team | Scoped roles - chat, talent, finance, owner | Varies widely |
| Verification and compliance | Minimal or bolt-on | Identity and age checks at onboarding, records retained | Depends on brief |
| Managed messaging at volume | Basic one-to-one chat only | Templates, lists, scheduling, staff-operated inboxes | Custom, usually phase two |
| Audit trail | Rarely present | Moderation, verification and payout decisions attributable | Depends on architecture |
| Ongoing support | Usually none | Defined plans after launch | Contract dependent |
Pricing is deliberately not on this page. The full cost breakdown lives on the development cost page.
The Technology Behind the Features
Laravel 12 on PHP 8.2+ with Sanctum-authenticated REST APIs serving the mobile apps, the web experience, staff tooling and the admin console from one backend. MySQL or MariaDB holds users, creator profiles, subscriptions, posts, media, messages, wallets, transactions, splits and payout records alongside the domain models for commerce, live, calls, AI, ads and analytics. Real-time messaging and live sessions run over WebSockets with Agora or Zego for streaming and calling, and media sits in S3-compatible storage that scales with the roster. The stack is conventional on purpose - it is the one your engineers can hire for, and the one you can extend without our involvement.
How It Works, End to End
A managed roster runs on a sequence a self-serve platform never has to think about: you recruit the talent, you verify them, you set their terms, your staff works their inbox, and you approve what they get paid. Here is that path.
Recruit and onboard the creator
A creator joins the roster rather than signing themselves up. Identity and business verification run at onboarding through third-party age and identity providers, with provider callbacks and a retained decision record attached to the creator before any content goes live.
Configure the split
Each creator gets their own three-way split between creator, manager and platform. This is per creator rather than global, and it is the number every downstream calculation reads. Changing it affects future events only, which is what keeps historical payouts defensible.
Scope your staff
A chat operator is scoped to specific creators and to messaging only. A talent manager sees the roster. A finance approver sees balances and payout runs. The owner sees everything. Nobody sees the slice they are not responsible for.
Your team works the inbox
Staff run one-to-one and group conversations on a creator's behalf, with saved templates, segmented lists, bulk sends and scheduled campaigns. This is the highest-margin surface in the operation and the one that has to be workable at volume.
The fan pays
Subscription, unlock, tip, gift, live session, call, storefront order, campaign or paid placement. Nine surfaces, and every one is calculated against that creator's configured split at the time of the transaction and written to a single ledger.
Settle and pay out
Earnings accrue per creator against their split. Withdrawal requests enter an approval-gated payout run rather than paying automatically, a finance role reviews and approves, and the approval is attributable to a named account with a reconciliation record.
Every Feature Earns Its Place
A feature list tells you what exists. This tells you what each one is worth to a managed operator, and what it costs you not to have it.
| Capability | What it actually does | Why it matters commercially |
|---|---|---|
| Per-creator three-way split | Creator, manager and platform shares configured individually, not globally | You can sign a creator on different terms without a spreadsheet, and every event settles the same way |
| One split engine, nine surfaces | A $9 unlock and a $200 call are accounted for identically | Month-end becomes a report rather than a reconciliation exercise across nine revenue types |
| Defensible split history | Changes affect future events only, against a written ledger | The first time a creator disputes a payout, you can prove which terms applied when |
| Scoped staff permissions | Chat, talent, finance and owner roles each see only their remit | You hire into the platform rather than around it, and a chat operator never sees the payout ledger |
| Managed messaging at volume | Templates, saved lists, bulk sends and scheduling on a creator's behalf | The highest-margin surface in the operation, and the one that decides how many creators one person can service |
| Approval-gated payouts | Runs reviewed and approved by a named finance role, with reconciliation | Money never leaves without a human attached to the decision, which is what an audit actually asks for |
| Verification with retained records | Identity and age checks at onboarding with the decision record kept | In markets with age-verification obligations, that record is what regulators ask to see |
| Attributable moderation | Report intake, review queues and takedown, each decision named | Payment providers in this category ask how you moderate before they approve you, not after |
| Multi-provider payments | Gateways integrated rather than mandated, several running at once | The practical hedge against a single account being closed, which happens in this category |
What Is Not Included in the Base Package
Every module on this page ships and can be switched on, switched off or reshaped. The items below are not part of the base build, and we would rather you know now than discover it mid-rollout.
- Payment provider accountsThe platform integrates gateways rather than mandating one. You bring accounts approved for your content type and region and we wire them in. Provider approval is usually the longest task on the project.
- AI-assisted pre-screeningReport intake, moderation queues, review states and takedown workflow all ship. Automated classification ahead of the human queue is an add-on, for operators moderating at a volume where manual triage stops scaling.
- Tiered agency permissionsChat, talent, finance and owner scopes ship. Deeper agency hierarchies - sub-agencies, regional managers, delegated approval chains - are scoped separately.
- Market-specific payment routingRunning more than one provider is supported. Routing rules that pick a provider by market, card type or content category are custom work.
- Bespoke payout schedulesApproval-gated runs ship. A custom cadence, split-by-milestone payouts or automated advance against future earnings are scoped against your terms.
- Custom moderation rulesYour policy, your standard and your regional rules are configuration. Rule engines that auto-action content against a scored policy are an extension.
- Age-verification provider feesIntegration points for third-party age and identity providers ship. The provider relationship and their per-check fee are yours.
- App store approvalBranded Android and iOS builds ship store-ready and we support submission. Approval in this content category depends on your policies and presentation, and is not something any vendor can guarantee.
See how Miracuves compares to agencies and freelancers
Cost, timeline, source-code ownership and compliance depth compared - plus the verification, moderation and payout controls a regulator will actually ask about.
Frequently Asked Questions
How is this different from your OnlyFans Clone?
How do revenue splits work?
Can my staff message fans on a creator's behalf?
Is there a mobile app?
What is an IsMyGirl Clone app?
What moderation tooling is included?
Explore the IsMyGirl Clone
See exactly what you are getting - before you commit
Sign in as an administrator, not as a fan. Spend your time in the roster, the verification queue, the split configuration and the payout approval screen.
Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by IsMyGirl.
“IsMyGirl Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to IsMyGirl, and how clients search for it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the IsMyGirl website or applications.
IsMyGirl and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
