┌─────────────────────────────────────────────────────────────────────────┐

│ FRONTEND LAYER │

│ │

│ ┌──────────────────────┐ ┌──────────────────────────────┐ │

│ │ Marketing Website │ │ Mobile App (iOS + Android) │ │

│ │ Next.js 15 + Vercel │ │ React Native (Expo SDK 53) │ │

│ │ - 7 pages │ │ - Schedule + Agenda │ │

│ │ - SEO optimized │ │ - QR Scanner (offline) │ │

│ │ - Ticket purchase │ │ - Digital Passport │ │

│ │ - Exhibitor portal │ │ - B2B Networking │ │

│ │ - Sponsor dashboard │ │ - Push Notifications │ │

│ │ - Spanish primary │ │ - Live Streaming │ │

│ └──────────┬───────────┘ └──────────────┬───────────────┘ │

│ │ │ │

└──────────────┼────────────────────────────────────┼─────────────────────┘

│ │

┌──────────────▼────────────────────────────────────▼─────────────────────┐

│ API GATEWAY LAYER │

│ Node.js / FastAPI — REST + WebSocket + GraphQL │

│ Hosted: Railway or Fly.io │

└──────────────────────────┬───────────────────────────────────────────────┘

│

┌──────────────────┼──────────────────────┐

│ │ │

┌───────▼──────┐ ┌────────▼────────┐ ┌──────────▼──────────┐

│ PostgreSQL │ │ Redis │ │ File Storage │

│ (Supabase │ │ (Cache + Queue) │ │ (Cloudflare R2 │

│ self-host) │ │ │ │ or Backblaze B2) │

└──────────────┘ └─────────────────┘ └──────────────────────┘

│

┌───────▼──────────────────────────────────────────────────────────────────┐

│ SPECIALIZED SERVICES │

│ │

│ ┌─────────────────┐ ┌──────────────────┐ ┌────────────────────────┐ │

│ │ Hi.Events │ │ Twenty CRM │ │ Bunny.net Stream │ │

│ │ (Ticketing) │ │ (Lead + Sponsor │ │ (Live + VOD) │ │

│ │ + Pretix for │ │ management) │ │ + Owncast fallback │ │

│ │ on-site QR │ └──────────────────┘ └────────────────────────┘ │

│ └─────────────────┘ │

│ │

│ ┌─────────────────┐ ┌──────────────────┐ ┌────────────────────────┐ │

│ │ NOWPayments │ │ Resend (Email) │ │ PostHog (Analytics) │ │

│ │ (Crypto USDT) │ │ + Brevo fallback │ │ Self-hosted │ │

│ │ + Pago Móvil │ └──────────────────┘ └────────────────────────┘ │

│ │ C2P (local) │ │

│ └─────────────────┘ │

└───────────────────────────────────────────────────────────────────────────┘

• Accepts 300+ cryptocurrencies including USDT (TRC-20, ideal for Venezuela due to low fees), USDC, Bitcoin, ETH
• Non-custodial, funds go directly to your wallet
• REST API with JavaScript SDK
• Sandbox environment for testing
• No geographic restrictions on the merchant side
• Transaction fees: ~0.5-1% per transaction
• Integration effort: 3-5 days

Binance Pay

• Massive adoption in Venezuela (Binance P2P monthly volume exceeds $100M in Venezuela)
• Free transactions between Binance users
• Crixto platform enables USDT-to-bolivar conversion at Venezuelan merchants
• Business API requires Binance merchant account verification
• Integration effort: 5-7 days

Recommended crypto implementation:

• Accept USDT (TRC-20) as primary — lowest fees (~$0.001/tx on TRON network vs ~$2-5 on ETH)
• Show prices in USD, convert at checkout to USDT at real-time rate
• Wallet addresses auto-generated per transaction via NOWPayments API
• Confirmation threshold: 10 confirmations for USDT TRC-20 (~3 minutes)

Layer 2: Zelle (Secondary USD Collection) — Target 20-30% of revenue

Zelle is the dominant informal USD payment method among Venezuelan diaspora and middle-class buyers with US bank access. For transactions under $5,000/day, peer-to-peer Zelle works without API integration.

Manual Zelle flow (viable for early launch):

1. Buyer selects Zelle at checkout

2. System displays Zelle phone number/email, transaction reference code

3. Admin receives Zelle notification, marks order as paid in admin panel

4. System sends ticket via email automatically

Automated Zelle flow (Week 8+ if budget allows):

• Requires a US business bank account with API access (Chase, Bank of America offer limited webhook APIs for enterprise)
• More complex; not recommended for MVP

Layer 3: Pago Móvil C2P (Local Bolivar Collection) — Target 15-20% of revenue

For domestic Pase General tickets priced at $15 equivalent in bolivars.

Options:

Recommended: InstaPago or e4Cash for broader bank coverage (not limited to one bank).

Layer 4: Stripe via US Entity (Optional, Later Phase)

If Morellis or the agency has or can establish a US LLC, open a Stripe account linked to a US bank (Mercury or Relay work well for remote founders). This unlocks credit card processing for international sponsors and exhibitors who need to invoice in USD.

Payment Summary Table

Venezuela Payment Risk Mitigations

• Display all prices in USD. Never in VES — avoid bolivar volatility risk.
• Exchange rate lock: freeze the bolivar-equivalent price at checkout start for 15 minutes.
• Maintain escrow logic: only release access (tickets, exhibitor portal) once payment is confirmed on-chain or validated via bank API.
• Fraud risk: crypto payments are irreversible — build clear cancellation policy.
• Provide WhatsApp support button on checkout for payment help (Venezuelan market expects this).

3. Mobile App Options

Option A: React Native with Expo (RECOMMENDED)

License: MIT

Why recommended:

• Expo SDK abstracts complex native setup (camera, notifications, offline storage, QR scanning)
• OTA (Over-The-Air) updates via Expo Updates — critical for fixing bugs during the 3-day event without App Store review delay
• Expo EAS (Expo Application Services) builds iOS + Android from one codebase
• Largest React Native community = fastest debugging under event pressure
• expo-camera provides offline-capable QR scanning (on-device ML Kit / Vision Kit)
• expo-notifications integrates with FCM/APNs for push notifications
• expo-sqlite enables offline-first local data storage (schedule, exhibitor directory cached locally)

Key packages:

What needs custom build:

• Digital Passport gamification system (stand visit tracking + rewards)
• B2B meeting scheduler (no good open-source option)
• Live streaming viewer (integrate Bunny.net or Mux player SDK)
• Exhibitor directory with search/filter

Estimated integration effort: 10-14 weeks for full feature set; 6 weeks for MVP

Option B: Flutter

Stack: Dart + Flutter 3.x

License: BSD-3

Pros:

• Best raw performance — custom rendering engine, no JS bridge
• Excellent for complex animations and custom UI
• Strong typed language (Dart) catches bugs at compile time

Cons:

• Dart is a smaller talent pool — harder to hire, harder to maintain
• OTA updates are limited (Shorebird exists but adds complexity)
• Fewer ready-made conference app boilerplates than React Native
• Team likely more familiar with JavaScript/TypeScript

• Reuse website codebase — same React components
• Fastest time to launch if web team is strong
• No separate mobile codebase

Cons:

• Performance noticeably worse for camera/QR scanning
• App Store review required for camera permissions anyway
• WebView-based apps feel less native to users
• QR scanning reliability lower than native camera access

Verdict: Only viable as a backup if mobile development timeline collapses. Not recommended for a flagship event app.

Mobile App Recommendation: React Native + Expo

Stack: Laravel (PHP) + React + PostgreSQL

License: AGPL-3.0 (see flag below)

Last active: 2025-2026, actively maintained

Features matching our needs:

• Multi-tier ticket types (free, paid, tiered pricing)
• QR code check-in with mobile scanning tools
• Stripe Connect integration (usable if US entity established)
• Offline payment methods support (manual Zelle/crypto can be configured)
• Embeddable ticket widget for integration into Next.js site
• Multi-language support (add Spanish translations)
• Full REST API
• Event analytics and data export
• Discount codes and promotional pricing

What's missing:

• Native Pago Móvil or crypto payment gateway (must build plugin)
• Sponsor-specific dashboard (must build)
• Exhibitor portal (must build or use separately)

AGPL Warning: AGPL-3.0 means if you modify Hi.Events and expose it as a service, you must open-source your modifications. For a private internal deployment serving one event, this is manageable. Consult the agency's legal position. Alternative: use Hi.Events cloud version at $0 for up to the free tier, or pay for commercial license.

Integration effort: 5-7 days to deploy self-hosted + configure; 10-14 days to add crypto/Pago Móvil payment plugin

Option B: Pretix

Stack: Python (Django) + PostgreSQL

License: Apache 2.0 (core) — more permissive than AGPL

Last active: Actively maintained (German team, production-proven at scale)

Features:

• Plugin architecture — extend with custom payment providers (critical for Venezuela)
• BTCPay Server plugin for Bitcoin/crypto payments (works with our crypto strategy)
• Embeddable widgets
• Hardware integration for on-site check-in scanners
• Multi-event, multi-organizer support
• Custom ticket templates
• Offline check-in capability via pretixSCAN mobile app (separate iOS/Android app)

pretixSCAN: Purpose-built check-in app that works offline — syncs attendee list to device, scans QR codes without internet. This alone is worth serious consideration for a Venezuela event.

What's missing:

• Modern UI (feels dated compared to Hi.Events)
• Pago Móvil integration (must build as plugin in Python/Django)

Integration effort: 7-10 days for base deployment; 12-15 days to build Venezuela payment plugins

Option C: Custom Next.js Website + Integrated Ticketing

Stack: Next.js 15 + Vercel + Stripe (or custom payment backend)

Pros:

• Full design control — critical for premium brand feel ("Domina el Futuro")
• Integrate exactly the payment methods we need from day one
• No AGPL licensing concerns
• Vercel Edge Network CDN globally

Cons:

• Highest development time — building ticketing from scratch
• More surfaces for bugs

Verdict: Build the marketing website in Next.js for brand + SEO. Use Hi.Events or Pretix for ticketing (embedded via iframe/widget). This hybrid gives best-of-both.

Website + Ticketing Recommendation

Marketing Website: Custom Next.js 15 + Tailwind CSS + Strapi CMS (headless) hosted on Vercel

Ticketing Engine: Pretix (self-hosted, Python/Django) — chosen over Hi.Events for its plugin architecture enabling Venezuela payment integration and its battle-tested pretixSCAN offline check-in app

Embed Pretix ticket widget into Next.js pages via iframe or Pretix's JavaScript widget. This keeps the brand experience seamless while leveraging Pretix's battle-tested ticketing logic.

5. Backend + CRM Options

Option A: Twenty CRM (RECOMMENDED)

Stack: Node.js + React + PostgreSQL + GraphQL (Apollo)

License: AGPL-3.0

Last active: Actively maintained, v1.0 released, 300+ contributors

Why it fits:

• Create custom "Event" objects: exhibitor, sponsor, speaker, attendee lead
• GraphQL + REST APIs for integration with our app and website
• Automated workflow engine for email follow-up sequences
• 360° contact view — see every touchpoint per exhibitor/sponsor lead
• Self-hosted on any VPS (DigitalOcean, Hetzner, etc.)
• Pipelines for sponsor deal stages: Prospecting → Pitched → Negotiating → Closed
• Data export (GDPR-compliant, full control)

Limitations:

• No built-in event-specific modules (must configure custom objects)
• AGPL — same licensing note as Hi.Events
• Newer than Salesforce/HubSpot — some features still maturing

Setup: Docker Compose deployment, 1-2 days to configure for event objects

Option B: Erxes

Stack: Node.js + React + MongoDB + TypeScript (Apollo)

License: GNU GPL v3 + Enterprise

Features:

• Unified inbox (email, WhatsApp, social) for sponsor/exhibitor communication
• Sales pipeline (Kanban style)
• Marketing automation — email sequences, campaigns
• Plugin marketplace for extended functionality
• All-in-one HubSpot replacement

Why not primary: MongoDB (NoSQL) is less ideal for the relational data model our event requires (tickets → attendees → exhibitor stands → sponsor tiers). PostgreSQL-based Twenty is cleaner for our use case.

Option C: Custom FastAPI Backend

Stack: Python FastAPI + PostgreSQL + Redis + Celery

Pros:

• Full control over data model
• No AGPL concerns
• Python ecosystem has excellent libraries for QR generation, PDF tickets, email

Cons:

• 4-6 weeks of backend-only development before any frontend can connect
• Effectively building a CRM from scratch

Verdict: Use as the custom API backend (handling app requests, QR passport logic, streaming auth), not as the CRM. Run Twenty CRM alongside it.

Backend + CRM Recommendation

Custom Backend: FastAPI (Python) or Node.js (Express/Fastify) for the core API

Database: PostgreSQL via Supabase (self-hosted on your VPS, or Supabase Cloud — they have no geographic restriction)

CRM: Twenty CRM (self-hosted Docker, same VPS)

Email: Resend (developer-friendly, 3,000/month free tier, clean API, React Email integration)

Analytics: PostHog (self-hosted, MIT license for some features, ~100K events/month free tier)

Queue/Cache: Redis (Upstash managed, or self-hosted)

6. Streaming + VOD Options

Option A: Bunny.net Stream (RECOMMENDED)

Type: Commercial SaaS (not open-source)

Price: $0.005/GB delivered — cheapest professional streaming CDN

Why recommended for Venezuela:

• 119+ PoPs globally including Latin America — content served from nearest node
• Adaptive bitrate streaming (HLS) — automatically reduces quality when bandwidth drops
• Built-in VOD hosting — upload recordings, serve for 90 days post-event
• Sponsor overlay support via custom player theming
• Unlimited video hosting with per-GB delivery billing
• No minimum commitment — pay for what you use
• Transcoding included

Multi-room strategy: Create separate Bunny Stream "Collections" per room. Each room has an RTMP ingest endpoint. OBS Studio at the venue sends RTMP stream → Bunny → viewers worldwide. Three simultaneous rooms = three RTMP streams, each independently managed.

Estimated cost for 3-day event:

• Assume 500 concurrent viewers × 3 rooms × 3 days × 4 hours/day × 3 Mbps = ~6.5 TB delivered
• At $0.005/GB: ~$32.50 for the entire event delivery (extremely affordable)
• VOD storage for 90 days: ~500 GB at $0.01/GB/month = ~$5/month

Option B: Owncast (Self-Hosted, Fallback)

License: MIT

Last commit: November 2025

Features:

• Complete ownership — no third-party CDN dependency
• Built-in chat
• RTMP ingest
• Single-room focused (one stream at a time per instance)

Limitation: Single-room architecture. For 3 simultaneous rooms, you'd need 3 separate Owncast instances on separate servers. Bandwidth entirely on your server — risky in Venezuela if upstream provider throttles.

Use case: Run Owncast as fallback/backup stream on the venue's local network. Attendees on-site access local stream even if internet goes down. This is the offline resilience strategy.

Option C: PeerTube

Stack: Node.js + Vue.js + ActivityPub

License: AGPL-3.0

Best for: VOD archiving post-event. PeerTube runs on 512MB RAM, handles large video libraries well, federation is optional.

Limitation: Live streaming is secondary feature; VOD is its strength.

Use case: Post-event VOD library (90 days). Cheaper than keeping Bunny VOD if storage grows large.

Streaming Recommendation

Live Streaming (Event Days): Bunny.net Stream — multi-room RTMP ingest, global CDN, adaptive bitrate

On-Site Fallback: Owncast on local server — LAN streaming for attendees even without internet

Post-Event VOD: Bunny.net Stream (90-day window), migrate to PeerTube or self-hosted S3 storage after

Encoding at venue: OBS Studio (free) on laptop at each room, connected to Bunny RTMP endpoint via ethernet (NOT WiFi — ethernet only at venue)

7. Build vs Buy Matrix

8. GitHub Repos to Clone / Reference

9. Essential npm Packages

Mobile App (React Native / Expo)

expo # Base SDK

expo-camera # QR scanning (offline-capable)

react-native-vision-camera # Advanced camera if expo-camera insufficient

expo-notifications # Push notifications

expo-sqlite # Offline local database

react-native-mmkv # Fast key-value storage

@tanstack/react-query # Data fetching + cache

react-native-maps # Venue floor map

@gorhom/bottom-sheet # UI component for exhibitor details

stream-chat-react-native # Chat/messaging

lottie-react-native # Animations for gamification

expo-updates # OTA updates (critical for event day fixes)

expo-localization # Spanish/English i18n

react-native-reanimated # Smooth animations

zustand # State management (lighter than Redux)

next # Framework

tailwindcss # Styling

@headlessui/react # Accessible UI components

framer-motion # Animations

next-intl # i18n (Spanish primary)

react-hook-form # Form handling (ticket purchase, exhibitor portal)

zod # Schema validation

@radix-ui/react-* # Primitive UI components

sharp # Image optimization

next-seo # SEO meta tags

stripe # Stripe SDK (if US entity available)

Node.js

fastify # High-performance HTTP server

@fastify/cors # CORS

@fastify/jwt # JWT auth

prisma # ORM for PostgreSQL

ioredis # Redis client

bull / bullmq # Job queue (email sends, webhook processing)

sharp # Image processing (QR generation)

qrcode # QR code generation

nodemailer / @react-email/... # Email templating with Resend

Python (if FastAPI chosen)

fastapi

uvicorn

sqlalchemy

alembic # DB migrations

celery # Task queue

redis

qrcode[pil] # QR generation

python-jose # JWT

Available: ~28 weeks from April 1, 2026

Phase 1 — Foundation (Weeks 1-4, April 1-28)

Phase 2 — Website (Weeks 3-7, April 14 - May 12)

Phase 3 — Mobile App MVP (Weeks 5-16, April 28 - July 7)

Phase 4 — Streaming Setup (Weeks 8-10, May 19 - June 2)

Phase 5 — Marketing + CRM (Weeks 1-20, ongoing)

Phase 6 — Production Hardening (Weeks 20-26, July 14 - August 25)

Phase 7 — Event Operations (Oct 2-4)

Phase 8 — Post-Event (Oct 5+)

11. Venezuela-Specific Risk Mitigations

Internet Reliability

• Risk: Venue internet drops during live event. Streaming fails. App can't sync.
• Mitigation 1: Negotiate with venue for dedicated fiber connection (not shared WiFi). Minimum 100 Mbps symmetric for streaming 3 rooms at 10 Mbps each.
• Mitigation 2: Backup 4G/5G LTE router (Movilnet, CANTV, Digitel) as failover — test all 3 carriers in advance, use the best one as backup.
• Mitigation 3: Owncast instance running on local server at venue — if internet dies, attendees on venue WiFi can still watch streams via local LAN.
• Mitigation 4: All app data (schedule, exhibitor directory, passport stamps) synced to device SQLite on first launch. App works fully offline after initial sync.
• Mitigation 5: Pretix pretixSCAN offline mode — check-in works without internet, syncs when connection restores.

Power Reliability

• Risk: Power outages affect streaming servers and on-site infrastructure.
• Mitigation: Cloud servers (Hetzner Europe or DigitalOcean NYC) are immune to local power issues. Only on-site OBS encoding laptops need UPS. Require venue to provide generator backup for AV area.

Payment Processing Failures

• Risk: NOWPayments API down, Pago Móvil system overloaded (happens regularly in Venezuela).
• Mitigation: Queue all payment webhook events. If primary processor fails, fallback flow shows WhatsApp number for manual Zelle transfer. No sale lost — just manual fulfillment.
• Mitigation 2: Pre-sell 30% of tickets before event through manual channels (exhibitions, social media DMs) to reduce day-of pressure.

App Distribution

• Risk: Google Play / App Store review delay. Venezuelan users may have trouble accessing stores.
• Mitigation 1: Submit apps 4 weeks before event to absorb review delays.
• Mitigation 2: Build PWA (Progressive Web App) version of the app as fallback — installable from website, works offline, covers 80% of features.
• Mitigation 3: Distribute APK directly via website for Android users who can't access Play Store.

Device Fragmentation

• Risk: Venezuela has high penetration of low-end Android devices (budget Tecno, Samsung A-series, etc.)
• Mitigation: Test app on Android 10+ minimum, target API level 29+. Optimize bundle size. Use Hermes JavaScript engine (Expo default). Lazy-load heavy screens.

Currency and Pricing Volatility

• Risk: Bolivar devalues between ticket purchase and event day, causing Pago Móvil pricing confusion.
• Mitigation: All pricing anchored in USD. Bolivar equivalent shown at checkout calculated from official BCV rate at time of purchase. Lock price for 15 minutes only.

CANTV + Hosting Restrictions

• Risk: Venezuelan ISPs (CANTV) block certain IP ranges or throttle traffic to foreign servers.
• Mitigation: Use Cloudflare proxy on all website traffic — Cloudflare IPs are generally not blocked and improve performance. Bunny.net CDN serves content from regional PoPs that avoid blocked upstream routes.

Data Sovereignty

• Risk: CONATEL (Venezuela telecom regulator) can request data about Venezuelan users.
• Mitigation: Store only event-relevant data. No unnecessary personal data collection. Clearly document data retention policy. Server infrastructure outside Venezuela = beyond CONATEL jurisdiction for most practical purposes.

Appendix: Cost Estimates

Monthly Hosting Costs (Pre-Event)

Event Day Streaming Costs (One-Time)

Development Costs (One-Time)

The above is infrastructure only. Development labor is the primary cost — estimate 3-5 developers × 28 weeks for full scope. Priority order for limited budget:

1. Website + Ticketing (revenue-generating, launch first)

2. Mobile App MVP (brand differentiator)

3. Backend + CRM (operational backbone)

4. Streaming (setup is low effort given Bunny.net)

Decision Log Entries