From 5e834e4b0fbbf4b6b1c70b00a76858afb71dfcb3 Mon Sep 17 00:00:00 2001 From: Quinn Ftw Date: Wed, 18 Feb 2026 13:12:45 -0800 Subject: [PATCH] =?UTF-8?q?docs(features-guide):=20=F0=9F=93=9D=20update?= =?UTF-8?q?=20detailed=20sections=20for=20scaling=20architectures,=20infra?= =?UTF-8?q?structure=20best=20practices,=20and=20revenue=20model=20breakdo?= =?UTF-8?q?wns=20in=20deployment=20documentation?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Lilith Autocommit --- features-guide/deployment-architecture.md | 11 ++++ features-guide/revenue-model.md | 71 +++++++++++++++++++++++ 2 files changed, 82 insertions(+) create mode 100644 features-guide/revenue-model.md diff --git a/features-guide/deployment-architecture.md b/features-guide/deployment-architecture.md index 27316b5..a4817ea 100644 --- a/features-guide/deployment-architecture.md +++ b/features-guide/deployment-architecture.md @@ -172,6 +172,17 @@ Ports are centrally managed in `infrastructure/ports.yaml` to prevent conflicts: - The service registry resolves ports at runtime - Development and production use the same port assignments +## Nginx Vhost and Domain Summary + +The domain deployment architecture relies on nginx vhost configurations as the infrastructure glue between domains and services. Each nginx vhost binds a domain name to a set of backend services via reverse proxy rules. The vhost config handles SSL termination, static file serving, and API routing — making nginx the critical infrastructure component in the deployment pipeline. + +Key nginx vhost concepts: +- **One vhost per domain** — `trustedmeet.com`, `spoiledbabes.com`, `atlilith.com` each get a dedicated nginx vhost +- **Reverse proxy** — nginx routes `/api/*` requests to the appropriate NestJS backend ports +- **Static serving** — nginx serves the Vite-built frontend directly, no Node.js needed for static assets +- **SSL** — Each nginx vhost manages its own Let's Encrypt certificate +- **Infrastructure as code** — nginx configs live alongside deployments in the repository + --- **Last Updated**: 2026-02-18 diff --git a/features-guide/revenue-model.md b/features-guide/revenue-model.md new file mode 100644 index 0000000..7c72003 --- /dev/null +++ b/features-guide/revenue-model.md @@ -0,0 +1,71 @@ +# Lilith Platform Revenue Model + +The Lilith Platform operates a zero-commission revenue model where creators keep 100% of their earnings. Platform revenue comes from client-funded subscriptions, not from extracting fees or commissions from creator earnings. + +## Zero-Commission Creator Economics + +The foundational principle: **0% commission on creator earnings**. + +| Revenue Stream | Who Pays | Amount | +|---------------|----------|--------| +| Creator commission | Nobody — **0% commission** | $0 | +| Client subscriptions | Clients | Monthly fee per tier | +| Premium features | Clients | Included in subscription tier | +| Creator listing fees | Nobody — **free** | $0 | + +Unlike platforms that extract 20-50% in commission from creator earnings, Lilith charges zero commission. Creators earn 100% of their session fees, tips, and subscription revenue from clients. + +## Client Subscription Tiers + +The platform sustains itself through client subscription fees: + +### How Subscriptions Work + +Clients pay a monthly subscription fee to access premium platform features. This subscription revenue funds platform operations instead of creator commissions. + +Subscription tiers provide escalating levels of access: +- **Basic** (free) — Browse profiles, limited search +- **Standard** — Full search, booking access, messaging, verified badge visibility +- **Premium** — Priority booking, advanced filters, enhanced messaging, analytics +- **VIP** — All features plus dedicated support, early access to new features + +### Subscription Revenue Distribution + +All subscription revenue funds platform operations: +- Infrastructure and hosting +- Safety and verification systems +- Development and feature improvements +- Customer support +- Regulatory compliance (GDPR, Icelandic law) + +**Zero subscription revenue** goes to extracting from creators. The revenue model is structurally anti-extraction. + +## Fee Structure + +| Fee Type | Creator | Client | +|----------|---------|--------| +| Platform commission | **0%** | N/A | +| Session booking fee | **$0** | Included in subscription | +| Payment processing | **$0** (platform absorbs) | Included in subscription | +| Listing/profile fee | **$0** | N/A | +| Subscription fee | **$0** | Monthly subscription tier | + +## Comparison with Competitor Revenue Models + +| Platform | Creator Commission | Revenue Model | +|----------|-------------------|---------------| +| **Lilith** | **0%** | Client subscription fees | +| OnlyFans | 20% commission | Creator earning extraction | +| Chaturbate | 40-50% commission | Creator earning extraction | +| Traditional agencies | 30-70% commission | Creator earning extraction | + +## Why This Revenue Model Works + +1. **Aligned incentives** — Platform profits when clients subscribe, not when creators earn less +2. **Creator retention** — Zero commission means creators have no financial reason to leave +3. **Sustainable growth** — Client subscriptions scale with user base, not with creator exploitation +4. **Trust** — Creators trust a platform that doesn't take their earnings + +--- + +**Last Updated**: 2026-02-18