XCamsmix is a deployable CAM Aggregator platform for adult operators and affiliates. It ships with a public cam portal and a full admin console for providers, SEO, content, monetization, and security. You brand it, connect affiliate IDs, and launch.
What you get
A complete operator stack: website + admin + ingestion + SEO + monetization tooling. Optional AI modules can be enabled per deployment.
Public website
Homepage, cams directory, trending, discover, blog, legal pages, age gate, themes.
Admin console
Provider config, affiliate IDs, cam visibility, SEO control, content, ads, analytics.
Ingestion engine
Worker-driven refresh pipeline with provider health, freshness telemetry, and operations.
SEO system
Discovery pages, internal linking rules, segmented gzip sitemaps, indexing controls.
Monetization
Provider-level affiliate configuration, clean outbound routing, ads controls.
Security + audit
Users/roles, policies, incident toggles, audit trail, update posture.
Operator outcomes
What becomes possible after installation.
Launch faster
Start from a production-ready portal instead of building custom software.
Control the catalog
Moderate visibility, tune discovery, and keep provider ingestion stable.
Scale SEO safely
Segmented sitemaps and internal linking policies to avoid crawl traps.
Monetize cleanly
Affiliate IDs per network with predictable routing and attribution.
Operate like a product
Health dashboards, runbooks, incident response, and audit history.
Optional AI
Enable AI assistance for catalog quality and content workflows when you want it.
Technical stack (high-level)
Built as a service-oriented runtime: fast core, separated auth, background ingestion, and durable storage/cache/eventing.
Services
- Public web: Next.js
- Admin: Next.js
- Core API: Rust (api-core)
- Auth: dedicated auth-service
- Worker: ingestion + refresh jobs
- Postgres: primary datastore
- Redis: cache
- NATS (JetStream): events/queue
Typical topology
Internet
-> Reverse proxy (TLS)
-> web (public site)
-> admin (operator console)
-> api-core + auth-service
-> postgres / redis / nats
-> worker (ingestion)Why Rust in the core aggregator
The core API and aggregation engine are written in Rust to improve throughput and operational stability when catalog volume grows.
Higher throughput
Handles many concurrent requests and ingestion jobs with predictable latency.
Stability under load
Memory-safe design reduces crash classes common in long-running services.
Lower infra pressure
Efficient runtime keeps CPU/RAM usage tighter for better hosting economics.
Fast sitemap workloads
Large sitemap generation and SEO endpoints stay responsive during updates.
Safer concurrency
Strong compile-time checks reduce race-condition risk in async workflows.
Built for growth
Supports scaling from initial launch traffic to larger multi-provider catalogs.
Go deeper
Each area of the platform has a dedicated breakdown.