Web Platform Overview

AMADEQ Web Platform is the public face of the product: the marketing landing page, authentication, the user cabinet, the agent catalogue, chat, render/studio, and the free live demo. It is the surface a visitor actually touches — LIS 3 powers the conversations behind it, and Onboarding V4 produces the avatars it sells.

The repository is an npm workspace with two packages:

Workspace	Stack
frontend	React 19 + TypeScript, Vite, React Router 7, Zustand, i18next, Framer Motion, @react-three/fiber + drei for the 3D globe, SCSS modules.
backend	Node + Express 4 (ESM, plain node, no build step), Prisma 5 over Neon Postgres, JWT auth, Stripe, Nodemailer, ws, Zod, Helmet, rate limiting.

Top-level map

Browser
  └─ React 19 + Vite frontend                :5173
       └─ /api proxy in development
            └─ Node/Express backend          :3333
                 ├─ Neon Postgres / Prisma (schema: web)
                 ├─ Stripe
                 ├─ SMTP
                 ├─ LIS gateway
                 ├─ render worker
                 ├─ ws-agent service
                 └─ WebSocket / Unreal live demo

Everything the browser must not see — the LIS API key, the ws-agent service key, Stripe secrets, SMTP credentials — stays behind the backend, which injects them server-side on proxied calls. See Architecture.

Quick start

npm install

Then run the frontend and the backend in two terminals:

npm run dev

npm run dev:backend

The frontend serves on http://localhost:5173, the backend on http://127.0.0.1:3333. Backend environment variables are described in Environment.

warning

Before any database schema change, read Database Migrations. This project runs against a shared Neon database with all tables in a non-default web schema; the standard Prisma migration commands do not work here, and there is no dev branch — every applied migration is production.

Checks

npm run build --workspace=frontend

npm run lint --workspace=frontend

npm run i18n:check --workspace=frontend

Also available in the frontend workspace: tokens:sync, tokens:check, and tokens:audit for design-token parity (see Design System Sync).

What is documented here

Area	Page
Layer map, route groups, and the main request flows	Architecture
Local startup, checks, and recovery from a broken local state	Runbook
Every backend environment variable	Environment
The web-schema Prisma workflow	Database Migrations
Checkout, webhook events, and plan activation	Stripe Checkout
Product scope, screens, and functional requirements	Product Requirements
How a studio scenario becomes an Unreal render job	Render Pipeline
The in-page visual editor specification	Page Tuner
Booking model and phase-1 plan for the free demo	Live Demo
Design-system rules, the pixel-perfect gate, and the Figma passports	Design

What is not documented here

The source repository also keeps a set of living working documents that deliberately stay there rather than on this site, because they change faster than the documentation can be republished:

File in the repository	Contents
docs/HANDOFF.md	The single active state-of-work document: latest check results, open risks, next step. Updated on almost every working session.
BACKLOG.md	Deferred infrastructure, database, and integration tasks.
SITE-AUDIT.md	Running UX, quality, and accessibility backlog.
RESPONSIVE-AUDIT.md, RESPONSIVE-FIX-PLAN.md	Responsive-behaviour findings and the milestone plan for fixing them.
docs/FIGMA-QA-AUDIT-2026-07-21.md, docs/DOCUMENTATION-HANDOFF-AUDIT-2026-07-21.md, docs/PERF-3D-GLOBE-REPORT-2026-07-27.md	Point-in-time audits and reports.
docs/tuner/home.md, docs/tuner/home.json	The generated edit log produced by the page tuner.

note

For the current state of the work — what passes, what is broken, what is next — read docs/HANDOFF.md in the repository. The pages here describe how the system is built and operated, not what state it is in today.

The pages in this section are translated from the Ukrainian source documents in the repository, which remain the originals.