Call Us Free: 1-888-334-1276
Miricam 8.3: Feature Reference

What Miricam does, and why it matters.

A plain-language technical reference for operators evaluating Miricam. Click any feature in the grid below to jump to a full description. If you want pricing and a summary, that’s here.

Streaming

WebRTC delivery

Miricam uses WebRTC as its broadcast protocol, which means performers stream directly from their browser camera without installing anything. WebRTC is built into every modern browser (Chrome, Firefox, Safari, Edge), so there is no plugin to download, no desktop app to install, and no third-party account to create. Latency is sub-second, which matters for real-time interaction: when a member types a message and a performer responds, both parties experience the exchange as a live conversation rather than a delayed replay.

The media server layer runs on AntMedia Server, which handles signalling, WebSocket connections, and stream distribution to multiple viewers simultaneously. A single performer stream can serve hundreds of concurrent viewers without the performer's connection being multiplied; the server handles the fan-out.

720p HD

720p HD streaming is included with every Miricam platform. It is the baseline that works reliably across the broadest range of performer hardware and viewer connections. A performer with a decent webcam and a standard broadband connection can broadcast in 720p without issues.

1080p Full HD

1080p Full HD streaming is included. It requires a performer connection capable of sustaining the required bitrate without dropping frames. For platforms where performers have good equipment, 1080p is the standard viewers increasingly expect.

2K / 4K with GPU transcoding

2K and 4K streaming are included and require GPU transcoding on the media server. The server takes the performer's high-resolution stream and re-encodes it into multiple quality levels simultaneously. Viewers with capable connections and screens receive the full resolution; viewers on weaker connections automatically receive a lower-quality variant. This is called adaptive bitrate delivery, and it means the operator does not have to choose between serving high-end viewers and not alienating everyone else.

GPU transcoding is computationally intensive, which is why this feature requires managed hosting with GPU acceleration or a server with a discrete GPU. Without GPU acceleration, the CPU overhead of transcoding at 4K is prohibitive.

Adaptive bitrate

Adaptive bitrate streaming means the player automatically adjusts the stream quality based on each viewer's available bandwidth in real time. If a viewer's connection degrades mid-session, the player steps down to a lower bitrate without interrupting the stream. When the connection recovers, it steps back up. This happens without any action from the viewer or the performer.

The alternative, a single fixed bitrate stream, forces an operator to choose: too high, and viewers on slower connections buffer constantly; too low, and viewers on fast connections see an unnecessarily degraded picture. Adaptive bitrate solves this by serving each viewer the best quality their connection can sustain.

Mobile broadcast

Performers can broadcast from a smartphone or tablet using the same browser-based WebRTC approach as desktop. There is no separate app. The performer opens their broadcast dashboard in a mobile browser and goes live. This removes a meaningful barrier for performers who do not have or do not want a dedicated desktop setup, and it enables broadcasting from locations where a laptop is not practical.

OBS Studio compatibility

Performers who use OBS Studio for their broadcast (for scene switching, overlays, green screen, hardware encoding, or a complex multi-camera setup) can push an RTMP stream from OBS directly into Miricam. This requires additional media server configuration to accept RTMP input alongside the standard WebRTC streams.

For the performer, the workflow is: configure OBS with the Miricam stream key, go live in OBS, and their stream appears on the platform exactly as a WebRTC stream would. OBS is standard software among professional streamers across every live streaming category, and supporting it means Miricam can accommodate performers who have already invested in production setups.

Session recording

Private sessions can be recorded server-side. The recording is stored and can be made available as VOD content, either automatically or with the performer's approval, turning a live session into a passive revenue asset. Performers control whether session recording is enabled on their profile.

Recording private sessions requires explicit consent mechanisms and careful handling to comply with relevant laws, which is why it is an opt-in feature at the performer level rather than a site-wide default.

Replay mode

Replay mode allows a performer to broadcast a pre-recorded video file as if it were a live stream. From the viewer's perspective, the stream appears in the directory as an active room. This is useful for performers who want to maintain presence on the platform during times they cannot stream live: scheduled content, promotional broadcasts, or maintaining directory visibility during off-hours.

Replay mode is included. It is a practical tool for solo operators who cannot staff live performers around the clock.

RTSP voyeur cameras

Miricam can ingest streams directly from RTSP-compatible IP cameras, the same type used in security and surveillance applications. This enables a distinct content category: voyeur-mode rooms, where a fixed camera broadcasts a space passively. Viewers subscribe for monthly access rather than paying per minute, because there is no performer on duty whose time is being purchased.

This feature requires additional media server configuration. The voyeur subscription model pairs naturally with it. See the Voyeur mode subscriptions entry under Revenue & Billing.

Stream reliability layer

Two mechanisms keep the streaming layer accurate. First, AntMedia webhooks send real-time status events to Miricam when a stream starts, stops, or drops unexpectedly. When a performer's connection cuts out, the platform knows within seconds and updates their status accordingly; they stop appearing as online in the directory.

Second, a 5-minute cron job cross-checks all active session records against the actual stream status from the media server. This catches edge cases where a webhook was missed or a database record was not updated correctly. The result is that ghost-streamer entries (performers who appear online but are not actually broadcasting) are automatically cleared. Without this, a directory fills up with stale entries that frustrate members and waste their time.

↑ Back to top

Revenue & Billing

Free public chat rooms

Free chat rooms are open to any visitor, including those who have not registered. They are the top of the acquisition funnel: visitors browse the directory, click a room, watch the stream, and interact in chat. The goal of a free chat room is to convert a browser into a registered, funded member.

Performers earn a configurable hourly rate for time spent in free chat, separate from tips or private sessions. This ensures performers are incentivised to maintain free chat presence rather than going straight to private: a full, active directory converts better than an empty one.

Private pay-per-minute sessions

Private 1-on-1 sessions are the core revenue model. A member starts a private session with a performer, and their wallet is debited per second (at 5-second intervals) at the configured per-minute rate. Only that member and the performer are in the room; it disappears from the public directory.

The platform's take is calculated server-side at transaction time using the configured commission split. Neither the member nor the performer can affect the rate. The session ends when the member ends it, when the performer ends it, or when the member's wallet balance reaches zero.

Group paid sessions

In a group session, the per-minute cost is divided equally among all members in the room. The performer earns at their full configured rate; the cost to each member is that rate split by the number of participants. Site owners set their own per-minute rates for every session type, so the economics scale to whatever pricing model the operator has configured.

Group sessions work well for performers who have built an audience and can reliably fill a room. They generate meaningful revenue while offering members a lower-cost route to an interactive experience than going private alone.

Per-second billing

Miricam bills in 5-second intervals rather than whole minutes. A member who spends 35 seconds in a private session is charged for 35 seconds, not a full minute. This is fairer to members and reduces a specific category of dispute: the complaint that a session was billed for time not used.

The practical difference on a typical session is small, but the perception matters. Members who feel they are being billed fairly are less likely to dispute charges, more likely to return, and more likely to trust the platform with additional top-ups.

Tipping

Tipping is available in both free chat and paid rooms. Preset tip amounts ($1, $5, $10, $20) are shown as quick-tap buttons, with a custom amount field available. Tips are processed immediately from the member's wallet and credited to the performer's earnings at the configured split rate.

Tipping in free chat is a significant revenue source for performers who run high-traffic rooms. It also functions as a conversion mechanism: a member who tips in free chat has made a financial commitment to the platform and is more likely to go private than one who has not.

Free chat passive earnings

Performers can be configured to earn a flat hourly rate (between $5 and $100 per hour) simply for being online in free chat. This rate is paid by the platform, not deducted from member wallets. It functions as an incentive for performers to stay online and maintain directory presence.

An active directory with real performers online at all hours converts better than one that is only populated during peak times. The free chat earnings rate is a tool for shaping performer behaviour to serve platform health.

Cam-to-cam

Cam-to-cam allows a member to enable their own camera during a private session. The performer can see the member; the member can see the performer. Cam-to-cam sessions carry a configurable surcharge on top of the standard private rate.

Cam-to-cam is consistently one of the most requested features among members who engage regularly with a specific performer. It changes the dynamic from watching to participating.

Fan Club subscriptions

Fan Club subscriptions add monthly recurring revenue alongside the per-minute model. Performers create up to three membership tiers (typically bronze, silver, and gold), each with different perks: exclusive content, discount rates on private sessions, direct messaging access, or priority in group shows.

From the operator's perspective, fan clubs add a revenue stream that does not depend on members actively deciding to go private on any given visit. A member who subscribes to a fan club is billing automatically each month. From the performer's perspective, it creates a relationship with their most engaged viewers that extends beyond individual sessions.

Voyeur mode subscriptions

Voyeur mode subscriptions are tied to RTSP camera streaming. Members pay a monthly recurring subscription for access to a passive camera feed: a fixed location stream with no performer actively engaging. Revenue is recurring and entirely passive once the camera is configured.

This is a niche product, but it is a genuine one. Certain content categories have an established audience for voyeur-style content, and the subscription model is better suited to it than per-minute billing.

Content feed subscriptions

Content feed subscriptions give members recurring monthly access to a performer's full content library. Rather than purchasing individual clips or photo sets, a subscriber pays once per month and can access everything the performer has published.

This is a Netflix-style model applied at the performer level. It suits performers who produce content consistently and want a predictable monthly income from their library, separate from live session revenue.

Prepaid wallet system

Miricam uses a prepaid wallet system. Members add funds to their wallet balance and spend from it during sessions. They do not enter their payment details at the start of each session. They fund their wallet in advance and the platform debits it in real time.

The key operational benefit is chargeback reduction. When a member disputes a session charge on a traditional per-transaction billing system, the dispute is about a specific charge they can point to. With a prepaid wallet, the member authorised the top-up, so the session charges are internal debits from a balance they chose to create. This does not eliminate chargebacks, but it changes the nature of the transaction in a way that reduces their frequency.

Real-time balance warnings

During a live session, the member's wallet balance is displayed in real time and updates every few seconds. When the balance approaches zero, a low-balance warning appears prominently, giving the member time to top up before the session ends. The top-up flow is accessible without leaving the session page.

Interrupting a session because a member ran out of credits is a conversion failure. The warning system turns that moment into an upsell opportunity instead.

Automatic session termination

When a member's wallet reaches zero, the session ends automatically and cleanly. The member is presented with a top-up prompt. There is no debt accumulation and no awkward negotiation about time owed. Both the member and the performer know exactly where they stand.

Full transaction history

Every wallet top-up, session charge, tip, and subscription billing event is logged per member with a timestamp, amount, and payment method. Members can review their own transaction history in their account area. Admins can access the full log for any member.

A complete transaction log is essential for handling member disputes accurately. When a member questions a charge, the admin can pull the exact record: what time the session started, how many seconds it ran, and what rate was applied, rather than relying on estimates.

Customer referral program

Members can refer new members using a personal referral link. When a referred member registers and funds their wallet, the referring member earns a credit to their own wallet or a cash commission, depending on configuration. Referral fraud detection using IP and device fingerprints prevents members from creating multiple accounts to claim their own referral.

Model referral program

Performers earn a percentage of platform revenue from members they personally referred, for the lifetime of that member's activity on the platform. A performer who sends traffic from their other platforms (social media, other cam sites, fan communities) is rewarded proportionally to the value that traffic generates.

Lifetime commission structures align performer incentives with platform growth. A performer who can earn ongoing passive income from members they brought to the platform has a reason to promote it consistently.

Webmaster affiliate program

The built-in affiliate system allows external webmasters and promoters to register as affiliates, receive tracking links, and earn commission on member registrations and first deposits they generate. Affiliate commissions are paid from the platform's share of revenue, not from the performer's share. Click fraud and referral fraud detection is built into the tracking layer.

↑ Back to top

Payments

NETbilling

NETbilling is Miricam's primary billing partner. It is a specialist adult billing processor with strong chargeback management tools, an established relationship with card networks for adult content, and a direct merchant account option available through 2MUCH.NET. For operators who do not yet have a billing relationship, NETbilling is typically the fastest path to a working payment integration.

CCBill

CCBill is one of the largest and most recognisable adult billing processors. Members across the adult internet have seen the CCBill name on their bank statements for decades. It is trusted in a way that newer processors are not. CCBill supports both subscription billing and the pay-per-minute model natively, and its fraud screening is mature.

Epoch

Epoch is a long-established adult billing processor with particularly strong reach in European markets. It handles multiple currencies and has existing relationships with European banks that make it suitable for platforms targeting non-US traffic. Epoch and CCBill together cover the majority of global adult billing volume.

Segpay

Segpay is an EU-based adult billing processor with GDPR-compliant infrastructure. For operators whose primary market is Europe, Segpay is often the stronger choice: EU-based processing reduces latency on card authorisations and can improve approval rates for European-issued cards.

Verotel

Verotel is a European adult billing processor that handles EUR and GBP transactions well. It is used by platforms with significant UK and continental European audiences and offers an additional option for operators who want redundancy across processors.

Payze

Payze is a newer adult billing processor with competitive rates. It has been growing its approval rate in the adult space and is included as an option for operators who are evaluating rates and terms across multiple processors.

Stripe

Stripe is included for operators who have received explicit approval to process adult content. Stripe's standard terms do not permit adult content, but it is possible to obtain approval for specific use cases. Where an operator has that approval, Stripe offers excellent developer tooling, fast payouts, and a familiar checkout experience.

If you are starting a new adult platform and do not yet have billing relationships, Stripe is not the place to start; NETbilling, CCBill, or Epoch are more appropriate first steps.

NATS integration

NATS (Network of Adult Trade Systems) is affiliate management software widely used across the adult industry. Where an operator already runs NATS, Miricam can integrate with it to handle both affiliate tracking and the payment processing flow in a single system. New member registrations that arrive via affiliate links are tracked through NATS, and commissions are calculated and recorded there.

Token Plus rebilling

Token Plus is a rebilling mechanism for returning members. On a member's first top-up, they go through the complete billing processor checkout flow. For subsequent top-ups, Token Plus allows the processor to authorise the transaction using the stored token from the original transaction: fewer clicks, fewer form fields, lower abandonment.

Wallet abandonment at top-up is a real problem. The friction of re-entering payment details on a third-party checkout page, on every top-up, costs operators money. Token Plus reduces that friction for the members most likely to spend: those who have already funded their wallet at least once.

Commission split configuration

The commission split between the platform and performers is configured site-wide during setup. The default is 70% to the performer and 30% to the platform, but this is fully adjustable. The split applies to all revenue types: private sessions, tips, group sessions, VOD sales, and fan club subscriptions, and is enforced server-side at transaction time.

The split is not a rounding exercise. Every transaction is calculated precisely and logged. Payout calculations are derived from the transaction ledger, not from estimates or manual tracking.

Per-performer rate overrides

Individual performers can be assigned a different commission rate than the site default. A high-earning performer might negotiate a better split as a retention incentive. A newer performer on a provisional arrangement might start on a lower rate. These overrides are applied per-performer and do not affect any other performer's rate.

Automated payout calculations

Every transaction on the platform is logged with the calculated performer portion and the platform portion at the time of the transaction. When a payout is due, the system totals the performer's logged earnings across the period and presents the figure to the admin for review and approval.

There is no manual calculation. The payout queue shows each performer's total owed, broken down by revenue type, with an approve-and-mark-as-paid workflow. Historical payout records are retained for each performer.

↑ Back to top

Performers

Multi-step registration

Performer onboarding is a multi-step process: account creation, identity verification, payment setup, and profile completion. Each step is a separate screen with clear instructions. Incomplete applications are held at whatever step the performer stopped; they can return and continue without starting over.

Splitting registration into steps serves two purposes. First, it prevents incomplete profiles from entering the approval queue; the admin only sees applications that have passed through identity verification. Second, it collects information progressively, which reduces abandonment compared to presenting a long form on a single page.

Government ID verification

Every performer must upload a government-issued photo ID before their application is reviewed. The accepted document types are configured at installation and typically include passports, national ID cards, and driver's licences. The document is stored securely and linked to the performer's account as the primary identity record for USC 2257 compliance.

AI face recognition

When a performer uploads their government ID, they are also asked to take a selfie. Miricam's AI face recognition system compares the selfie to the photo on the ID document using EasyOCR and NVIDIA CUDA. The comparison runs in approximately 0.23 seconds and produces a confidence score that is presented to the admin reviewer alongside the raw documents.

This is an efficiency tool for the admin, not a replacement for human review. The AI result flags obvious mismatches, such as a selfie that does not resemble the ID photo, so the reviewer can prioritise their attention. Every application still requires manual approval.

Admin approval workflow

No performer goes live without explicit admin approval. The approval queue presents each pending application with the AI verification result, the uploaded ID documents, the selfie, and the completed profile. The admin approves or rejects each one individually. There is no automatic approval path.

This is by design. An automated approval system would reduce the admin burden but would also allow unverified or fraudulent performers onto the platform. The compliance and legal exposure that creates is not worth the convenience.

AI profile autofill

During profile setup, a performer selects their content categories and interests. Miricam's AI uses these selections to generate a bio and suggest relevant tags. The generated content is shown to the performer as a starting point. They can edit, replace, or accept it.

The practical value is for performers who are not writers. A blank bio field stops many performers at this step. An AI-generated starting point that captures their category correctly removes that barrier and produces more complete, indexable profile text than a performer might write themselves.

Tax information collection

US-based performers are required to provide tax information (SSN, EIN, or ITIN) for 1099-NEC reporting. This information is collected during the registration flow, stored securely, and made accessible for year-end reporting. Operators who pay US-based contractors above the reporting threshold are legally required to file 1099s; this system supports that requirement.

Room status switching

Performers switch between four status states from their broadcast dashboard: Free Chat (publicly visible, earning per-hour rate), Group Session (group billing active), Private (1-on-1, room removed from directory), and Offline. Status changes update the directory in real time; a performer who switches to Offline disappears from the active listings within seconds.

Broadcast schedule

Performers can publish a broadcast schedule showing the specific days and times when they plan to be online. The schedule is displayed on their profile with timezone conversion: a viewer in London and a viewer in Los Angeles both see the scheduled time in their own timezone. This reduces the "when are you online?" question that takes up significant time in performer-viewer communication.

Lovense toy integration

Lovense makes Bluetooth-connected adult toys that can be controlled remotely over the internet. Performers can connect their compatible Lovense device to their Miricam stream. Tip events from viewers trigger vibration patterns in the toy; the strength and duration of the response can be configured to match different tip levels.

This is consistently among the most requested features in the cam platform market. It transforms tipping from a financial gesture into a physical interaction, which changes the dynamic of a free chat room significantly. Rooms with Lovense-enabled performers regularly outperform equivalent rooms without it in tips per session.

Earnings dashboard

Performers have an earnings dashboard that shows revenue broken down by type: free chat hours, private session minutes, group sessions, tips, content sales, and fan club subscriptions. They can view earnings by day, week, or month. The breakdown tells a performer not just how much they earned but where it came from.

A performer who earns mostly from free chat tips is running a different business from one who earns mostly from private sessions, even if the total is the same. Understanding the breakdown is the starting point for managing which activities to prioritise.

Private customer notes

Performers can add private notes to individual member profiles, visible only to that performer and not to the member or other performers. Notes can capture anything useful: a member's preferred name, a recurring interest, a previous session they mentioned, a particular content request.

Performers who remember details about their regulars provide a meaningfully different experience than those who treat every session as the first. Customer notes make that memory systematic rather than reliant on the performer's recall across potentially hundreds of different viewers.

Top fans leaderboard

Each performer's profile displays a leaderboard of their top-spending members. The leaderboard is public; members can see where they rank among a performer's supporters. Some members actively compete for leaderboard position, which drives additional spending. The leaderboard also signals to browsing visitors that a performer has an active, engaged audience.

Self-service payout requests

Performers submit payout requests through their own dashboard. They see their available balance, enter the amount they want to withdraw, and submit. The request appears in the admin's payout queue for review and approval. No email, no support ticket, no back-and-forth required.

This is an operational convenience for both parties. Performers get a clear, predictable process. Admins get requests in a structured queue rather than scattered across messages.

Content library

Performers upload images and videos through their dashboard. Each piece of content has a visibility setting: free/public, paid (purchase required), or fan-club-only. The content library is displayed on the performer's profile and is fully searchable.

Content that sits in a library earns passively. A performer who uploads consistently over time builds a catalogue that generates revenue from their profile page even while they are offline.

AI performance coach

The AI performance coach analyses each performer's earnings data and generates specific, data-driven recommendations. Not generic advice about streaming more often, but observations tied to their actual numbers: "Your Tuesday streams produce 40% more per-hour earnings than your Monday streams. Consider shifting your schedule," or "Members who tip in your free chat convert to private at twice the platform average. Consider spending more time building your free chat audience before going private."

The coach runs against each performer's individual data rather than platform averages, which means its recommendations are specific to that performer's patterns and audience.

↑ Back to top

Users

Streamer directory with filters

The performer directory is the primary navigation surface for members and visitors. It shows online performers with live thumbnails, viewer counts, category tags, and an indication of current room status. Visitors can filter by category, search by name or tag, and sort by various criteria.

An effective directory converts browsers. A directory that is hard to navigate, slow to load, or full of offline performers does not. The directory is updated in real time as performers go online, go offline, or switch between statuses.

Public profiles without login

Performer profiles are publicly accessible without registration or login. A visitor can browse the directory, click through to a performer's profile, read their bio, view their schedule, watch any free content they have made public, and understand what the platform offers, all before creating an account.

This reduces the barrier to initial engagement significantly. Requiring registration before showing anything about the platform creates friction at the point where visitors have the least commitment. Public profiles let visitors invest time and interest before asking them to invest an account.

Secure member registration

Member registration is email-verified with secure session handling throughout. Password storage uses bcrypt hashing. Session tokens carry HTTPOnly, Secure, and SameSite flags: they are not accessible to JavaScript, are only transmitted over HTTPS, and are restricted to same-site requests. These are standard security practices, consistently applied.

30-day remember-me tokens

Members who opt in to "remember me" at login receive a 30-day persistent session token. They stay logged in across browser sessions and device restarts for the duration of that period. Returning visits require no re-authentication.

Reducing friction for returning visits matters. A member who has to log in every time they visit has a lower return rate than one who lands on the homepage already authenticated.

Device fingerprinting

Miricam uses device fingerprinting to detect suspicious patterns: multiple accounts registered from the same device, members who have previously charged back, or referral attribution that looks like fraud. Flagged accounts are surfaced in the admin panel for review rather than being acted on automatically.

Device fingerprinting does not replace session authentication. It is a signal layer that helps admins identify risk without requiring every member to prove their identity beyond their password.

Like and follow system

The like and follow system allows members to follow specific performers. Following a performer affects several things: the followed performer appears at the top of that member's directory view, the member receives a notification when the performer goes live, and the performer's community wall posts appear in the member's feed.

Follow mechanics create platform stickiness. A member who follows three or four performers and gets notifications when they go live has a reason to return to the platform that is not tied to any individual session decision.

Live notifications

When a performer goes live, members who follow them receive a notification, in-browser if they are on the platform or via email if configured. The notification links directly to the performer's room. This is opt-in engagement: the member chose to follow, so the notification is something they asked for.

Community wall feed

The community wall feed aggregates posts from all performers a member follows and displays them on the member's home screen after login. It functions like a lightweight social feed: updates, announcements, teasers, and schedule reminders from performers the member has expressed interest in.

A feed that shows content even when a member's favourite performers are offline gives the platform a reason for a member to visit when they are not actively intending to spend. That casual visit can turn into a session.

VOD browsing with previews

The VOD library allows members to browse recorded content from performers. Each video has a configurable free preview: long enough to establish what the content is, short enough that the full clip retains clear additional value. Purchase happens from the same page; the full clip unlocks immediately from the member's wallet.

Fan club membership

From the member side, fan club membership is a subscription to a specific performer's club at a chosen tier. The subscription is billed monthly from the member's wallet or payment method. Different tiers unlock different benefits, configured by the performer. A fan club subscription is a recurring relationship between a member and a performer, managed on the platform.

Mobile-optimised experience

The member-facing interface is built responsive from the ground up. Chat rooms, the performer directory, wallet top-up, performer profiles, and content browsing all function correctly on mobile browsers without a separate app. This is not a scaled-down mobile view; it is a full-featured interface designed to work on a phone screen.

A significant portion of adult content browsing happens on mobile devices. A platform that does not work well on mobile is not competing for that audience.

↑ Back to top

Admin & Operations

KPI overview dashboard

The admin dashboard opens with a KPI panel: total revenue for the period, number of active performers, number of funded member wallets, and traffic trend. These are the four numbers an operator needs to answer the question "is the site healthy right now?" without navigating into detailed reports.

Real-time session stats

The live stats view shows current active sessions, concurrent viewer counts by room, and the live revenue rate: how much the platform is earning per minute at that moment. This is useful during peak periods to monitor load, and useful during off-peak periods to understand baseline performance.

Application review queue

The application review queue presents pending performer applications one at a time. For each application, the admin sees the AI face recognition result (confidence score and comparison image), the uploaded government ID, the selfie, and the completed profile information. The admin approves or rejects with a single action. Rejected applications can include a reason that is communicated to the applicant.

Full performer roster

The full performer roster is searchable and filterable by status (active, suspended, pending), earnings tier, join date, and custom criteria. Bulk actions are available, such as sending a notification to all active performers or exporting a filtered list for reporting.

Suspend / unsuspend accounts

A performer can be suspended from the admin panel with immediate effect. A suspended performer cannot broadcast, cannot be found in the directory, and cannot log in. The action is reversible with a single click: the account is not deleted, just locked. This is the appropriate tool for situations that require immediate action while a decision is being made.

Payout management

The payout queue shows all pending payout requests, each with the performer's name, the amount requested, the period it covers, and a breakdown by revenue type. The admin reviews each request, confirms the amount, and marks it as paid. The system records the payment date and method. Historical payout records are retained and searchable.

Chargeback management

The chargeback management view shows all received chargebacks with detail: which member, which transaction, which processor, how much, and when. The admin can flag the member account for additional scrutiny, apply a spending limit, or suspend the account. The log is retained for processor reporting.

User cohort analytics

The user analytics section includes cohort retention curves, tracking what percentage of members who registered in a given week are still active (making transactions) at 1 week, 2 weeks, 1 month, and 3 months. This is the metric that tells an operator whether the platform is retaining the members it acquires, or whether it has a leaky bucket.

Churn visibility at the individual member level allows admins to identify members who are lapsing before they are gone. A member who visited weekly and has not been back in two weeks is a candidate for a retention effort; a member who visited once and never returned is a different problem.

8 themes + custom CSS

Miricam includes 8 built-in themes (4 light and 4 dark) applied from the admin panel without any technical knowledge required. For operators who want to go further, custom CSS can be injected site-wide. Custom CSS is applied on top of the active theme and persists through software updates.

Operating mode selection

The operating mode determines what kind of platform Miricam is running: Chat Only (no streaming, just text chat and content), Streaming Only (video rooms without a text chat layer), or Hybrid (both). This allows operators to launch a simpler platform initially, such as a content site without live streaming, and add streaming capability later.

Email system configuration

Transactional emails (registration confirmation, application approval, payout notification, low balance alert) are sent through a configurable email provider. SendGrid, Mailgun, and standard SMTP are all supported. Email templates are editable from the admin panel. A platform that sends well-designed transactional emails from its own domain projects professionalism; one that sends from a generic server does not.

Performer broadcast messaging

Administrators can send messages to all active performers or a filtered subset, such as only performers who have not streamed in the past two weeks. Messages appear in the performer's dashboard notification area. This is the appropriate channel for policy announcements, rate changes, platform events, or operational reminders.

Banner advertising system

The banner advertising system allows admins to place promotional banners across the site: home page, directory, performer profiles, or specific page types. Banners can promote platform events, bonus credit offers, featured performers, or third-party partner products. Click-through is tracked. Banners are managed entirely from the admin panel.

MBASE syndication

MBASE is a cooperative performer sharing network across Miricam-licensed platforms. When MBASE syndication is enabled, performers from partner platforms appear in your directory alongside your own. They broadcast from their home platform; viewers on your platform see and can interact with them. Revenue from interactions on your platform is split between your platform and the performer's home platform according to the MBASE agreement.

The practical value of MBASE is that a new platform does not start with an empty directory. An empty directory does not convert. A directory with active performers, even if many of them are MBASE syndicated, gives visitors a reason to register and fund a wallet.

Chat with your data

Administrators can query platform data in plain English. "Which performers earned more than $500 last month?", "How many members funded their wallet but never started a private session?", "What is the average session length on Tuesday evenings?" The system interprets these questions and returns results without requiring SQL knowledge.

This is not a replacement for structured reporting, but it is a useful tool for operators who have specific questions that do not fit neatly into a preset report view.

↑ Back to top

SEO & Traffic

AI meta tag generation

Every performer profile and community wall post gets an AI-generated title tag and meta description. The AI (2Much Colossus, a model trained specifically for adult platform SEO) produces tags that describe the actual content of the profile: the performer's category, their specific attributes, and the type of content they offer.

Generic meta tag templates produce generic search results. A performer directory where every profile has a unique, accurate, and search-intent-matched meta tag is a different SEO proposition from one where every profile shares a variation of "Join [Performer Name] on [Platform Name] for live cam shows."

A/B testing for meta variants

With Google Search Console integration, meta tag A/B testing runs automatically. Two variants of a title tag or description are generated; GSC data is monitored to determine which variant produces better click-through rates from search results. The winning variant is retained. This runs at scale across the entire performer directory without manual intervention.

Auto re-optimisation

When a page's GSC data shows declining impressions or click-through rate below a configurable threshold, the re-optimisation system triggers automatically. It generates new meta tag variants for the affected page and applies them. The system then monitors whether the new tags improve performance. This is a closed-loop SEO optimisation process that runs without the operator having to monitor individual page performance.

Google Search Console integration

The Google Search Console integration pulls real search performance data (impressions, clicks, average position, and click-through rate) for every indexed page on the platform. This data is used by the AI meta optimisation system and by the automatic re-optimisation trigger. It is also available in the admin reporting area for operators who want to monitor search performance directly.

Dynamic XML sitemap

Miricam generates an XML sitemap dynamically. When a new performer is added and their profile is published, it appears in the sitemap on the next generation. When a performer is suspended, their profile is removed from the sitemap. The sitemap is submitted to Google Search Console automatically. New profiles are crawled and indexed faster as a result.

GA4 integration

GA4 integration tracks the full member journey as events: page views, performer profile views, video plays, registration, wallet top-up, session start, and session end. These events can be used to build conversion funnels in GA4 to understand where in the journey visitors drop off, which performer profiles convert best from view to session, and which traffic sources produce members who actually spend.

Twitter/X auto-posting

When a performer who has connected their Twitter/X account goes live, an automatic tweet is sent. The tweet announces the performer is live with a link to their room. Performers with existing Twitter followings become a traffic source for the platform without needing to remember to post every time they stream.

Across a platform with many performers, this creates a persistent presence in the social media feeds of audiences that are already interested in the category. The aggregate effect is significant for platforms where performers have meaningful followings.

Community wall posting

Community wall posting allows performers to publish updates, announcements, and teasers to a feed. Members who follow a performer see these posts in their community feed. The wall functions as a lightweight social layer; performers can maintain a presence and communicate with their audience between live sessions.

Public pages indexed without login

Performer profiles, the streamer directory, and the community wall are all publicly accessible without requiring visitors to register or log in. This matters for SEO: search engines can crawl and index every performer profile, every bio, every tag, and every community post. A platform that walls off all content behind a login form is effectively invisible to search engines.

Public profiles generate long-tail keyword coverage organically. Every performer bio with specific category terms, every schedule entry, every community wall post is an indexed page that can rank for queries no campaign manager would think to target. At scale, across dozens or hundreds of performers, this produces a substantial and compounding organic footprint that paid traffic cannot replicate.

Custom tour pages

Custom tour pages are configurable landing pages designed for specific acquisition campaigns. An operator running paid traffic to a specific content category can create a tour page with custom copy, images, and calls to action that speaks directly to that audience, without modifying the main site. Affiliates can be given dedicated tour page URLs with their tracking code embedded.

Streamer recruitment page

A separate performer recruitment landing page is built into Miricam and deployed as part of the installation. It has its own URL, its own copy, and its own calls to action aimed at people looking for cam modelling opportunities rather than people looking to watch cam shows. The two audiences have different search behaviours and different conversion paths; serving them from the same page is a mistake.

↑ Back to top

AI & Automation

ViewerIQ CRM

ViewerIQ is Miricam's customer intelligence layer. It analyses each member's spending behaviour and engagement patterns and classifies them into segments: Browser (registered but not spent), New (first purchase made), Regular (recurring spending, predictable pattern), VIP (high spend, strong engagement), and Whale (top-tier spenders).

Segmentation matters because different segments respond to different approaches. A VIP member who has not been on the platform in two weeks is a churn risk worth acting on: a bonus credit offer or a notification that their favourite performer is online. A Browser who has never spent is a different problem entirely. Treating all members identically wastes retention spend on members who were never going to convert and under-invests in members who are genuinely valuable.

Churn prediction

ViewerIQ's churn prediction model monitors each member's engagement patterns and flags members who show early signs of disengagement: reducing session frequency, shorter sessions, longer gaps between visits. These flags appear in the admin panel before the member has actually churned.

The window between "starting to disengage" and "gone" is the only window available for retention. A bonus credit, a notification that a followed performer is online, or a personalised message can extend a valuable member relationship significantly if applied at the right moment. Applied after the member has already left, it cannot.

Lifetime value tracking

Lifetime value tracking calculates per-member LTV from the complete transaction history. This data is useful for understanding acquisition efficiency: if a traffic source produces members with a 90-day LTV of $15, and another produces members with a 90-day LTV of $80, that difference should inform where acquisition spend goes.

LTV tracking also surfaces which performer-member relationships drive the highest long-term value, identifying which performers attract and retain the most valuable members, with direct implications for who to feature, incentivise, and retain.

Virtual Users

Every new cam platform faces the same cold-start problem: empty rooms do not convert, but rooms only fill with real members once the platform has traction. Virtual Users are AI-driven participants that maintain realistic activity in performer rooms during the platform's early stages. They appear in the viewer count, participate in chat, and tip at configurable rates.

Virtual Users are a temporary scaffolding tool, not a permanent feature. Their activity is configured to taper as real member numbers grow. The goal is to bridge the gap between launch and the point where genuine social proof exists in the rooms.

AI Vision for Virtual Users

AI Vision gives Virtual Users the ability to analyse the active stream in real time using GPU-accelerated image recognition. A Virtual User that can see what is happening on screen and generate contextually relevant chat messages in response is more convincing than one working from a script. This requires significant GPU compute on the media server.

Trend and anomaly detection

The anomaly detection layer monitors platform metrics and flags unusual patterns as admin notifications. A sudden drop in revenue from a specific processor might indicate a billing integration issue. An unusual spike in chargebacks from a specific performer might indicate a compliance problem. A traffic pattern that does not match historical norms might indicate a bot traffic injection.

These are the kinds of signals that get missed in manual monitoring. The anomaly system brings them to the operator's attention without requiring constant dashboard observation.

Revenue predictions

Revenue prediction uses historical platform data (seasonal patterns, day-of-week trends, performer activity cycles) to project future revenue. The projections are not precise, but they are useful for capacity planning and for identifying when actual performance is diverging significantly from what the historical pattern would suggest.

AI identity verification

The AI identity verification system (EasyOCR running on NVIDIA CUDA) compares a performer's selfie to their government ID photo and produces a confidence score in approximately 0.23 seconds. The score and a side-by-side comparison image are presented to the admin reviewer. An obvious mismatch is flagged clearly; a high-confidence match gives the reviewer a starting point.

This is not a replacement for the admin's judgment. It is a tool that makes the review faster and flags the cases that most need human attention.

AI profile autofill

AI profile autofill generates a performer bio and tag suggestions from their selected categories during registration. The generated text is editable; it is a starting point, not a final product. The practical value is removing the blank-page problem: performers who would otherwise write nothing, or write very little, produce a complete profile because the AI gave them something to work from.

AI streamer performance coach

The AI performance coach analyses each performer's individual data (stream times, room type usage, session lengths, tip patterns, content upload frequency) and produces specific recommendations. It does not offer generic advice. If a performer earns consistently more on Tuesday evenings than any other time, the coach notes it. If their free-to-private conversion rate is below the platform average, the coach identifies it and suggests approaches.

The coach runs on real data from that specific performer's history, not platform-wide averages. Its recommendations are relevant to the individual, which is what makes them actionable.

↑ Back to top

Compliance & Security

USC 2257 records management

USC 18 §2257 requires US-based adult content producers and platforms to maintain records of performer age verification and make those records available for inspection. Miricam stores identity verification records (government ID scans, selfies, AI verification results) against each performer's account in a format that satisfies the record-keeping requirement.

The installation includes the required Custodian of Records designation and the USC 2257 statement page, pre-configured for the operator. These are legal requirements, not optional features.

DMCA takedown tools

The DMCA takedown workflow gives admins the tools to respond to copyright complaints: locate the content, remove it, and log the action with a timestamp, description of the removed content, and the basis for removal. The log is retained for the operator's records.

A documented, repeatable DMCA response process is a practical necessity for any platform that hosts user-uploaded content. The alternative, ad hoc responses with no record, creates legal exposure if a complaint escalates.

Cloudflare + Turnstile

Miricam integrates with Cloudflare for DDoS mitigation at the network layer and with Cloudflare Turnstile for bot-resistant CAPTCHA on registration and payment forms. Turnstile is Cloudflare's privacy-respecting CAPTCHA alternative. It does not present visual puzzles to legitimate users in most cases, but it is effective at blocking automated registration and form submission attacks.

Secure session management

Session tokens on all user types (members, performers, affiliates, and admins) are issued with HTTPOnly (not accessible to JavaScript), Secure (only transmitted over HTTPS), and SameSite (restricted to same-site requests) flags. These three attributes together defend against the most common session token attack vectors: XSS-based token theft, protocol downgrade attacks, and cross-site request forgery.

Separated authentication

Members, performers, affiliates, and administrators each have separate authentication systems, separate session stores, and separate permission models. A member session token cannot be used to authenticate as a performer. A performer session cannot access admin functions. A compromised member account cannot escalate to any other role.

This is a design principle rather than a feature, but it has practical security implications. Many platforms run a single user system with role flags, which means a vulnerability in the member registration flow is also a vulnerability in the admin authentication flow.

Referral fraud detection

Referral fraud (creating multiple accounts to claim referral bonuses, or sending fraudulent traffic to generate affiliate commissions) is detected using IP address and device fingerprint matching. When a new registration matches the fingerprint of an existing account, or when referral patterns match known fraud signatures, the attributed commission is voided pending admin review rather than being paid and then reversed.

DSA moderation infrastructure

The Digital Services Act applies to platforms operating in EU member states and requires content reporting mechanisms, moderation workflows, and transparency about content policies. Miricam's moderation infrastructure (content reporting, review queues, and policy documentation pages) aligns with these requirements. Operators targeting EU audiences should review DSA applicability with legal counsel, but the technical infrastructure is in place.

2Much AI Age Verify

2Much AI Age Verify uses the visitor's webcam or phone camera combined with on-device AI to estimate age in real time. The analysis runs locally: no image is transmitted to a server, no biometric data is stored, and no personal information leaves the visitor's device. The result is a pass or fail determination that allows or blocks access — nothing more.

This approach addresses a core tension in age verification: robust checks typically require collecting and storing personal data, which creates its own compliance and security exposure. 2Much AI Age Verify eliminates that exposure by design. The check is performed, the result is used, and nothing persists. Operators can deploy age gating with a strong compliance argument and no data retention liability.

Yoti third-party certification (optional)

Yoti is a certified third-party identity verification service. Operators can add Yoti verification as an additional step in the registration flow. Yoti performs its own identity check and issues a certified result. For operators who need defensible compliance documentation — those in regulated markets or with high-value performers — Yoti adds a layer of third-party certification that an internal check alone cannot provide.

Yoti integration is optional. Operators who do not need third-party certification do not need to enable it. Miricam's built-in government ID verification and AI face recognition provide the baseline compliance layer on every platform.

↑ Back to top
Ready to go further?

Talk to us about your platform.

Tell us your domain and your expected traffic. We will give you a straight answer on whether Miricam is the right fit.

Get in Touch View Pricing