Where It Started
LiveCamNetwork launched in the early 2000s, when live video over the internet was genuinely difficult. Bandwidth was expensive. Video codecs were primitive. Consumer broadband was still new enough that most users treated it as a luxury. The idea of running a pay-per-minute cam site on residential or small-business internet seemed ambitious by the standards of the time.
2MUCH.NET built the platform during a period when most competitors were working with Flash and proprietary browser plugins. The installations were fragile, the latency was frustrating, and the billing integrations were held together with approaches that couldn't scale. The goal from day one was to build something that could run reliably across multiple operators, on their own domains, with billing that actually worked.
What we built was, by any reasonable description, a white-label SaaS cam platform. That category didn't really have a name yet. We just called it LiveCamNetwork, because that's what it was: a network of live cam sites running on a shared platform. Operators could brand it as their own. The underlying software, billing engine, and infrastructure were ours.
What Made It Work
The platform was purpose-built for cam sites. It wasn't adapted from something else or bolted together from generic components. Pay-per-minute private chat, group shows, and tipping were core from the beginning, not added later. The billing system handled session metering, chargeback tracking, and performer payouts as first-class concerns.
On the payment side, we integrated with the processors operators actually used: CCBill, Segpay, Epoch, NETbilling, and Verotel. Each of those integrations required real engineering, real back-and-forth with the processors, and real testing across different account configurations. Getting billing right in this industry is not straightforward, and a platform that can't hold that together reliably doesn't last. We held it together for over a decade.
Operators got a site that was genuinely their own. Their domain, their branding, their models, their pricing. The platform handled the technology and the billing infrastructure. That division of responsibility worked well and was the reason operators stayed.
Webdreams
In 2005, a production company called Galafilm approached 2MUCH.NET about documenting what we were building. The result was Webdreams, a Canadian documentary series that followed LiveCamNetwork and the people running it across two seasons, from roughly 2005 to 2008. It aired on Showcase and IFC.
The series documented the day-to-day of running an adult cam network in Canada: the technical problems, the performer relationships, the business decisions, and the broader context of building this kind of platform at that particular moment in internet history. It was nominated for a Gemini Award for Best Direction in a Documentary Series in 2006.
Most software products from that era don't have a public record. LiveCamNetwork does. The cameras were in the office during some of the most interesting years of building it. That documentation exists, and it's a reasonably honest account of what the work actually looked like. More on the series at Looking Back on Webdreams.
Over a Decade of Operation
The platform ran continuously for well over ten years across multiple operators. In that time, the underlying technology changed almost completely. Flash gave way to HTML5. Desktop-only design gave way to mobile-first. Standard definition streaming gave way to HD. RTMP, which was the workhorse protocol for real-time video for years, eventually gave way to WebRTC.
None of those transitions happened cleanly or all at once. Each one required real decisions about what to keep, what to rebuild, and how to handle the period where old and new had to coexist. Operators couldn't simply shut down while infrastructure changed. The platform stayed live through all of it.
By the time WebRTC became reliable enough to replace RTMP for real-time video, the team had been through enough platform generations to know the difference between a genuine architectural improvement and a change that created more problems than it solved. That accumulated judgment matters. It doesn't show up in a feature list, but it shows up in how the platform actually behaves under pressure.
The Rebrand to Miricam
LiveCamNetwork was the right name for the first generation of the platform. It described exactly what it was: a network infrastructure for live cam sites. By the 2020s, that description had become too narrow.
The platform had grown to include multi-tenant operator management, integrated streaming servers through MiriStream, AutoSEO analytics integration, automated social posting for performers, age verification support, and a modern WebRTC stack. The codebase had been rebuilt several times. The operator dashboard was unrecognisable compared to the original. The billing engine had been through multiple full rewrites.
Miricam is a better description of what the platform is today. It reflects the product as it exists now, rather than the product as it existed when the name was chosen. The codebase, the billing engine, the operator relationships, and the support team are the same. The name changed because the product outgrew its original description, which is the right reason to change a name.
If you searched for LiveCamNetwork and ended up here, you're in the right place. The platform is now called Miricam. All operator accounts, billing integrations, and support relationships continue under the new name. Nothing was discontinued. Nothing was handed off. The same team that built LiveCamNetwork runs Miricam today.
What Miricam Is Today
Operators who come to Miricam today get a platform that reflects everything learned across more than a decade of running cam sites in production. WebRTC video, tested across a wide range of browsers and devices. Pay-per-minute billing, with all the session metering and chargeback handling that requires. Group chat and tipping as standard features. Performer management that handles scheduling, payouts, and permissions at scale.
Multi-tenant support means that operators can run their own branded platform without managing infrastructure. Managed hosting is included. Payment processor integrations with CCBill, Segpay, Epoch, NETbilling, and Verotel are maintained and current. Technical support comes from the people who built the system, not a third-party help desk reading from a knowledge base.
Full details on what the platform includes and how pricing works are on the Miricam product page.