Skip to main content

Byeego

AI sales CRM and reseller platform with customer dashboard, reseller portal, admin console, docs, and hidden backend origin.

Split platform across backend API, public web, docs, customer dashboard, reseller portal, admin console, domain gateway surfaces, CI gates, smoke tests, staging workflows, and production-readiness validation.

LoopxoAI CRM PlatformVisit live product
AI CRMReseller PortalAdmin ConsoleCustomer DashboardDocsBilling
Byeego

Byeego

Byeego is a split AI sales CRM and reseller platform. The platform is organized across a backend API service, public web app, public docs site, customer dashboard, reseller portal, admin console, and public developer gateway.

The build is not a single landing page or dashboard. It separates customer, reseller, admin, docs, and backend surfaces so each role can move through the product without exposing the private backend origin.

Product Surfaces

  • Backend API service.
  • Public web app at byeego.com.
  • Public docs site at docs.byeego.com.
  • Customer dashboard at dashboard.byeego.com.
  • Reseller portal at reseller.byeego.com.
  • Internal admin console at admin.byeego.com.
  • Public developer gateway at connect.byeego.com.

The admin repo is intentionally treated as private/staff-only before production deployment.

Complexity Handled

  • Six local repos exist and build independently.
  • Customer, reseller, and admin apps use separate repos, ports, domains, and gateway surfaces.
  • Backend origin protection and auth surface isolation are implemented behind gateway headers.
  • Customer, reseller, and admin smoke suites enforce gateway/provider browser-call safety.
  • Customer, reseller, and admin routes use route-level splitting with lazy page chunks.
  • Each repo has ci:verify, local secret scanning, GitHub CI for typecheck/build/secret scan/audit gates, and CI artifacts.
  • Manual staging-smoke workflows run Playwright against deployed staging URLs.
  • Backend DB package has Drizzle migration generation/migration scripts and a tracked migrations directory.
  • Backend integration harness can boot the built app against TEST_DATABASE_URL.
  • Backend seed creates repeatable customer, reseller, admin, org, bot, context, leads, credits, billing state, client, CRM, booking, setup, QA, and ROI report fixtures.
  • GET /api/launch-checklist returns readiness for bot, knowledge, widget, CRM, booking, voice, billing, and reporting.

Production Readiness

Production backend boot validation requires managed Postgres, managed Redis, gateway secrets, HTTPS origins, Sentry-style error tracking, and an uptime check URL.

A 10/10 ticket gate exists for coding maturity, E2E, production, frontend, and competitive moat work. A release checklist also exists for launch execution.

What This Demonstrates

Byeego demonstrates platform decomposition and production-thinking across multiple role-specific apps. The strongest proof is the split between public web, docs, customer dashboard, reseller portal, admin console, protected backend, and gateway surfaces.

The project shows that Loopxo can move beyond a feature demo into launch-grade architecture: repo separation, auth-surface isolation, seed data, CI gates, smoke workflows, staging checks, and production boot requirements.

Short Version

Byeego is an AI sales CRM and reseller platform spanning backend API, customer dashboard, reseller portal, admin console, docs site, public web app, developer gateway, CI gates, staging smoke workflows, Drizzle/Postgres migrations, gateway isolation, readiness checks, and launch documentation.

Gallery

Byeego — Gallery 1