IsMyGirl Clone Features: The Managed Creator Platform in Full
A managed creator model puts recruitment, account operations and an agreed revenue share together. The recorded specification covers a roster you control, three-way splits per creator, staff-operated messaging and approval-gated payouts. These are proposed software capabilities to verify against your requirements and signed terms, not evidence of an operating deployment.
The original also advertised an uptime SLA and a fixed launch window. Neither is presented here as an established service commitment. Ask for availability, delivery, support and acceptance terms in your written quote.
Feature Set by Role
The recorded scope combines the consumer product fans and creators use with the operational layer your team runs. Validate both halves rather than assuming a consumer interface includes the management controls.
01 ยท Fan
The proposed consumer surface spans browser and mobile. Per-creator subscriptions can have free previews or fully gated access; pay-per-view unlocks apply to posts, media and message attachments. Wallet top-ups and stored balance support repeat purchases without a separate checkout each time. One-to-one and group messaging include tips and gifts against a creator or post. Public live sessions include chat, with private live on request. Paid audio and video calls, shoutout requests and creator storefront orders are also specified.
02 ยท Creator
The roster view covers publishing, pricing, earnings and the configured split. Posts, stories, reels, comments, likes and saves span image, video, audio and files. Per-creator pricing covers subscriptions, unlocks, messages, live and calls. Storefront listings support coupons and time-boxed promotions. Donation and goal-based campaigns sit alongside paid shoutout fulfilment. AI personas are specified to answer in the creator's voice with retained session history; suitability, consent and disclosure need review. Earnings, engagement and content performance are shown against the creator's own split.
03 ยท Operator and staff
The proposed permissions separate chat operators, talent managers, finance approvers and owners. Roster management adds creators, sets each split, and manages status and restrictions. Verification review includes provider callbacks and a retained decision record. Managed messaging on a creator's behalf includes templates, saved lists and scheduling. Moderation includes report intake, review queues and takedown with attributable decisions. Payment configuration supports more than one gateway at once, and payout runs are approval-gated with reconciliation records. Verify the access boundaries through role-based testing.
The split engine is the defining mechanism in this specification. Each monetized event - subscription, unlock, tip, message, live session, call, storefront order, campaign and paid placement - reads that creator's configured split at transaction time and writes to one ledger. A small unlock and a larger call should use the same accounting path. Test that path and the month-end reports rather than treating the architecture description as proof of reconciliation.
Managed Platform, Generic Creator Script and Custom Build
Compare the tooling a managed roster needs, not a headline feature count. The Omnistu column records proposed scope. The other columns are questions to ask each bidder, not claims about what a provider category lacks.
| Criterion | Generic creator script - what to ask | Omnistu - proposed scope | Custom build - what to ask |
|---|---|---|---|
| Delivery | How will you estimate configuration, integrations and acceptance? | A delivery window and acceptance criteria agreed in writing | What scope, dependencies and acceptance criteria drive the schedule? |
| Source-code ownership | What source access and per-creator licence restrictions apply? | Full source and no per-creator licence are proposed; confirm against signed software terms | What ownership and third-party licence terms apply? |
| Creator roster management | How are roster records managed, including any external spreadsheets? | Onboarding, status and per-creator settings - specified | Is roster management inside the quoted scope? |
| Revenue split engine | Does the split support creator, manager and platform, or only a flat platform fee? | Three-way splits per creator across every revenue type - specified | How will per-creator splits be implemented and tested? |
| Payout controls | Do transfers happen in-system or manually outside it? | Approval-gated runs with an attributable record - specified | What approval and reconciliation controls are included? |
| Staff permission model | Are there separate scoped accounts rather than a shared admin login? | Scoped chat, talent, finance and owner roles - specified | Which staff roles and access boundaries are in scope? |
| Verification and compliance | Which checks, provider integrations and records are available? | Identity and age-check integration at onboarding with retained records - specified; review suitability with qualified counsel | Which verification controls does the brief include, and what needs counsel review? |
| Managed messaging at volume | Does messaging include these operating tools beyond one-to-one chat? | Templates, lists, scheduling and staff-operated inboxes - specified | Are managed messaging workflows included at launch or a later phase? |
| Audit trail | Which decisions are logged, and can records be retrieved? | Attributable moderation, verification and payout decisions - specified | How are audit records designed, retained and tested? |
| Ongoing support | What support, if any, is included and under which terms? | Support plans to be defined in writing after launch | What support and maintenance obligations does the contract include? |
Pricing is deliberately not on this page. The Development Cost page covers the scope behind a written quote.
The Technology Behind the Features
The recorded stack is Laravel 12 on PHP 8.2+, with Sanctum-authenticated REST APIs serving mobile apps, web, 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 domain models for commerce, live, calls, AI, ads and analytics.
Real-time messaging and live sessions use WebSockets, with Agora or Zego for streaming and calling. Media uses S3-compatible storage. Ask how capacity, storage costs and performance will be tested as the roster grows. The stated reason for this stack is maintainability: ask whether your engineers can hire for it, extend it and operate it without dependence on one vendor. A conventional stack alone does not establish that outcome.
How It Works, End to End
The managed-roster journey connects recruitment, verification, terms, staff-operated inboxes and payout approval. These six steps preserve the recorded operating sequence; each control remains subject to implementation and acceptance testing.
Step 1 ยท Recruit and onboard the creator
A creator joins the managed roster rather than simply signing up to a self-serve operation. The proposed onboarding flow integrates third-party age and identity providers for identity and business verification, with provider callbacks and a retained decision record attached before content goes live. Confirm the actual checks, provider eligibility and approval gates; ask qualified counsel which checks and records your market requires.
Step 2 ยท Configure the split
Each creator has a three-way split between creator, manager and platform. It is per creator rather than global, and downstream calculations read it. The specified mechanism applies changes only to future events. Test that historical payouts retain the terms in effect when the transaction happened.
Step 3 ยท Scope your staff
A chat operator is scoped to specific creators and messaging only. A talent manager sees the roster; a finance approver sees balances and payout runs; the owner sees everything. The intended boundary is that nobody sees a slice outside their remit. Verify it in both interface and API permission tests.
Step 4 ยท Your team works the inbox
Staff run one-to-one and group conversations on a creator's behalf using saved templates, segmented lists, bulk sends and scheduled campaigns. Test the number of creators and conversations a staff member can handle, along with consent, disclosure and message-policy requirements. The source's claim that this is the highest-margin surface is not established here.
Step 5 ยท The fan pays
Subscription, unlock, tip, gift, live session, call, storefront order, campaign or paid placement: nine surfaces are enumerated in this flow. Each reads the creator's configured split at transaction time and writes to one ledger. Validate each event type separately, including refunds and failure paths, before relying on the shared mechanism.
Step 6 ยท Settle and pay out
Earnings accrue per creator against the configured split. Withdrawal requests enter an approval-gated payout run rather than paying automatically. A finance role reviews and approves, with the decision attributable to a named account and linked to a reconciliation record. Test the authorization and reconciliation paths with your own controls.
Every Feature Earns Its Place
The source links each capability to a commercial reason. The final column turns that reasoning into diligence questions, preserving each topic without promising margin, compliance or operating outcomes.
| Capability | What it does - specified | Commercial question to test |
|---|---|---|
| Per-creator three-way split | Creator, manager and platform shares configured individually rather than globally | Can the operator agree different creator terms without a separate spreadsheet, while settling each event consistently? |
| One split engine, nine surfaces | Unlocks and calls use the same accounting mechanism regardless of amount | Can month-end reports reconcile all nine revenue types without separate manual accounting paths? |
| Split history | Changes apply to future events only, with historical ledger records | Can you retrieve and substantiate which terms applied when a disputed payout was earned? |
| Scoped staff permissions | Chat, talent, finance and owner roles see their assigned remit | Can you add staff without exposing payout records to chat operators? Verify access rather than assuming it. |
| Managed messaging at volume | Templates, saved lists, bulk sends and scheduling on a creator's behalf | What workload and staffing economics does testing show? The source's highest-margin claim is not a forecast. |
| Approval-gated payouts | Named finance-role review and approval, with reconciliation | Can you verify that funds cannot leave through an unapproved path, and ask your auditor which evidence is needed? |
| Verification with retained records | Identity and age-check integration at onboarding, retaining the decision record | Ask qualified counsel which age-verification obligations and records apply in your markets, and whether this workflow meets them. |
| Attributable moderation | Report intake, review queues and takedown with named decisions | Ask prospective payment providers which moderation controls they require and whether these records meet their review needs. |
| Multi-provider payments | Integrated rather than mandated gateways, with more than one running at once | What happens if an account is suspended or closed? Test continuity and routing rather than assuming another provider can take over. |
What Is Not Included in the Base Package
The original describes the listed modules as switchable and configurable. Confirm the exact enabled, disabled or reshaped scope in writing. The following exclusions and dependencies remain separate from the base build.
01 ยท Payment provider accounts
Gateways are integrated rather than mandated. You bring accounts approved by the provider for your content type and region; connecting them is scoped work. Provider approval is a project dependency. Ask each provider for its process and timing rather than assuming it will be the longest task.
02 ยท AI-assisted pre-screening
Report intake, moderation queues, review states and takedown are in the recorded base scope. Automated classification ahead of the human queue is an add-on. Decide whether it is appropriate from moderation volume and testing, rather than assuming it replaces human review.
03 ยท Tiered agency permissions
Chat, talent, finance and owner scopes are specified. Deeper agency hierarchies, including sub-agencies, regional managers and delegated approval chains, are scoped separately.
04 ยท Market-specific payment routing
More than one provider is supported in the recorded scope. Routing rules that select by market, card type or content category are custom work.
05 ยท Bespoke payout schedules
Approval-gated runs are specified. A custom cadence, split-by-milestone payouts or automated advances against future earnings must be scoped against your terms.
06 ยท Custom moderation rules
Your policy, standard and regional rules are configuration inputs. Rule engines that automatically act on content against a scored policy are an extension; confirm which rules and review paths are required.
07 ยท Age-verification provider fees
Integration points for third-party age and identity providers are specified. The provider relationship and per-check fees are yours; confirm coverage, approval and commercial terms directly.
08 ยท App store approval
Branded Android builds and submission support are recorded scope. iOS is proposed scoped work subject to validation, not an established shipped build. Ask how your content policies and presentation fit the current store rules. Approval is a store decision and cannot be guaranteed.
Compare Delivery Options
The Development Company page examines cost, delivery, source-code terms and verification, moderation and payout controls. Ask qualified counsel and relevant providers which compliance controls matter for your operation rather than assuming any software is regulator-approved.
Read the provider comparisonFrequently Asked Questions
How is this different from your OnlyFans Clone?
The recorded distinction is the operating model and buyer, not a claim about the named third-party businesses. The OnlyFans Clone page is framed for self-serve platforms where creators run their own accounts. This managed-roster scope puts recruitment, onboarding, per-creator splits, staff-operated messaging and payout approval at the centre. If you represent creators commercially, assess those workflows first.
How do revenue splits work?
Splits are per creator, not global, and divide between creator, manager and platform. Every monetized event, including subscriptions, unlocks, tips, calls and orders, reads the configured split at transaction time and writes to a ledger. Changes are specified to affect future events only, not historical ones. Verify historical terms and payouts through acceptance tests.
Can my staff message fans on a creator's behalf?
The proposed permission model scopes a chat operator to specific creators and messaging only, without payouts, splits or platform settings. Saved templates, bulk sends, custom lists and scheduling are included in the recorded scope. Test these boundaries, and review consent, disclosure and messaging policies before use.
Is there a mobile app?
Branded Android builds sharing one codebase with the web experience and submission support are recorded scope. iOS is proposed scoped work subject to validation. The original described both as store-ready; that is not treated here as verified delivery or store approval. Check real-device behaviour and current store rules against your policies and presentation.
What is an IsMyGirl Clone app?
A proposed white-label platform for a managed creator business: fans subscribe, unlock content, message, tip and join live sessions, while your team recruits and verifies creators, sets their splits, operates inboxes and approves payouts. Full source ownership and control of branding and commercial terms are proposed, subject to the signed software and third-party licence terms.
What moderation tooling is included?
Fan and staff reporting, review-state moderation queues, takedown workflow and per-creator content controls are specified, with decisions attributable to the staff member who made them. AI-assisted pre-screening is an add-on. Confirm your moderation rules, staffing and review requirements before launch.
Evaluate the Management Controls Before You Commit
The original evaluation path focuses on an administrator's work: roster management, the verification queue, split configuration and payout approval, rather than only the fan interface. Ask us to work through that path against your specification in writing, and ask each bidder the same. No live demo or client deployment is claimed here. The sibling pages cover the scope behind cost, delivery options and the revenue model. Email is answered in writing, with no calls required and no phone numbers collected.
