Skip to main content

System Architecture

This page describes the current working technical structure of LiVi at the present stage.

Current architecture scope​

The actively documented system includes:

  • Scriptwriter frontend
  • Pricing frontend
  • payment creation flow
  • payment confirmation webhook
  • entitlement-based access verification
  • access state sync back to the product UI

Main layers​

Frontend layer​

Current frontend projects include:

  • Scriptwriter
  • Pricing

Scriptwriter is the product interface. Pricing is the billing interface.

API layer​

The current backend layer is based on serverless API routes.

Main active routes:

  • create-payment
  • check-pro
  • wayforpay-webhook

Data layer​

The data layer is currently centered around Supabase.

Main active entities:

  • entitlements
  • payment_orders

Payment layer​

The payment flow is currently built around WayForPay checkout and webhook confirmation.

Access layer​

PRO access is determined by server-side entitlement state and then reflected back into the product interface.

Current system principle​

The current architecture separates product usage from billing logic:

  • Scriptwriter is the product layer
  • Pricing is the billing center
  • access is restored through entitlement checks

This structure is part of the current working system architecture of LiVi.