Questions & answers

The base platform without customisation, in one geo-location and one data centre, takes 1–1.5 months. With customisation, add about two months — roughly 3–3.5 months in total. A base deployment across several geo-locations takes about 6 months, and custom development can run in parallel. These are indicative estimates; we refine them once the scope is agreed.

Costs depend on the terms of the contract. They typically include a setup fee, a monthly rental fee (a percentage of customer payments with a monthly minimum) and custom development billed by the hour. We discuss every custom task in detail and give a preliminary estimate in hours before work starts; the hourly rate depends on how many hours per month are reserved for your project. The rental fee is calculated on all customer payments received in the previous month, minus refunds and chargebacks, before performer revenue share and processor fees are deducted.

Yes. We give demo access for the customer, performer and webmaster (traffic partner) roles, and to the operator admin panel — performer management and approvals, customers, token pricing, individual revenue shares, transactions, payouts, affiliates, geo-blocking, account suspensions and business statistics. We can also walk you through it on a screen-share call.

Yes. We can customise any element of the platform, including landing pages and the chat room itself. We can build to your approved mockups or design the pages ourselves in Figma — or you can design on your side together with our designer. The front end is built in ReactJS; landing pages can also be classic HTML/CSS. The standard version of the site is responsive.

Your database content is entirely yours: only you manage customers, performers and other data, and we export a full database dump on request. You own the visual design of custom work and any standalone custom code that doesn’t change the core. The core platform, and code integrated into it, stays our IP and is licensed to you, because it can’t be separated from the platform. With the Enterprise option the platform is installed on your own servers with full root access and a non-exclusive licence with source-code access — you can develop it further yourself or with any team, while support (bug fixes, security updates) is included in the rental fee.

The platform runs on the open-source Janus media server and delivers genuine real-time WebRTC video rather than HLS-based near-live streaming, which keeps the cost of owning a large, high-traffic service down. The Krona.Chat platform itself load-balances WebRTC streams across Janus servers by region. As a guide, one dedicated media server (8+ performance cores, 32 GB+ RAM, NVMe/SSD, a guaranteed 1 Gbit/s port) gives about 700 Mbit/s of usable bandwidth under sustained load (1 Gbit/s minus ~30% headroom). Besides media servers, a deployment needs HTTP capacity, a database cluster (at least three MariaDB Galera servers), a backup/failover server and storage. We size it from your expected number of performers online, viewers per room, traffic growth and target regions.

CCBill is already integrated. We recommend adding at least one more processor, such as Segpay, as a backup — standard practice in the adult industry, because a processor can hold or restrict an account at short notice.

The customer’s balance is kept in tokens (credits); the exchange rate between tokens and real currency is set in the admin panel. Our platform fee and processor fees can be built into the token rate at the moment the customer tops up, so they don’t have to be deducted separately. Promotional credits are supported: they don’t count toward performer payouts, but performers still see them in their statistics.

Revenue sharing is built on a flexible tree-like structure: earnings can be split between the performer, webcam studios, traffic providers and other parties. The payout percentage can be one default rate for everyone or set individually for each performer. We configure the structure to match your business model.

Performers see their total earnings, the transactions behind them and their payout history in their dashboard. Payout currency and the token rate are set in the admin panel, and any payout method and currency can be supported. By default the performer enters their payment details and a manager sends the payout through the chosen payment service — that manual review doubles as a compliance check. The holding period and payout day are configured for your project.

Premium users get access to photo, video and snapshot galleries and can send private messages to the performer inside the public room — other viewers don’t see them, and there is no per-message charge. The platform already supports a lifetime Premium status for users who deposit a set amount, and this logic can be adapted to your model.

Free public rooms — a live video broadcast with a text chat in the room — and four paid formats: group show, classic private, exclusive private (face-to-face) and Watch Private. Other visitors can spy on a classic private; nobody can spy on an exclusive private, where the customer can also turn on their own camera so the model sees and hears them. Classic and exclusive privates can be priced differently. The model turns on Watch Private while doing a private show on another cam site (such as Chaturbate): visitors to your site watch that show but can't message the model.

Tipping is supported, including a preset list of tip amounts. Lovense toys are integrated, so tips can trigger interactive vibration.

Yes. The platform has no technical restrictions on multistreaming. Exclusivity, if you want it, is usually set in the performer agreement rather than enforced by the software.

The platform has its own performer verification, so you don’t pay third-party providers per check at launch. The moderator gets an instant Telegram notification about each upload. A manager reviews the uploaded ID documents and selfie, checks that the selfie matches the document photo, and approves or rejects the application with a reason. Automated liveness checks are not built in, but a third-party verification provider can be integrated if you prefer. Everyone who appears on camera must verify their own account; your Terms & Conditions set the rules and penalties.

Visitor age verification is not built in by default, but adding it is technically straightforward — as a built-in feature or as an integration with an external provider such as Yoti. We recommend planning for the effect an age check at the entry point has on traffic conversion.

Yes. Country blocking can be set for the whole platform and separately for each performer.

The site has a dedicated page for complaints and content removal requests, built to meet legal requirements including DMCA. Requests go to the people responsible via Telegram or email and are handled manually. Moderators also check who is present in live rooms and whether broadcasts comply with the performer agreement.

Yes. It can be set up to attract customers, performers or webmasters, with revenue share, CPA or hybrid payouts.