Skip to main content

Applications Overview

Last reviewed: 2026-05-20
Maintained by: Engineering

ZGRID is organized around a small set of product surfaces. Each one has a clear role in the day-to-day flow between managers, residents, technicians, and platform administrators.

This page explains what each surface does without exposing internal deployment or operational detail.

API​

  • Path: apps/api
  • Purpose: the platform core for auth, business logic, data access, billing, onboarding, operational workflows, and admin controls
  • Related reference: ../99-reference/environment-contract.md

Landing​

  • Path: apps/landing
  • Purpose: the public-facing product story for ZGRID
  • Public routes:
    • / redirects to /bs
    • /bs is Bosnian
    • /en is English
  • Contact flow:
    • server-backed inquiry delivery
    • recipient and provider configuration stays in environment-managed values
  • Related reference: ../99-reference/environment-contract.md

Back Office​

  • Path: apps/back-office
  • Purpose: the internal workspace for super_admin users who manage platform-level operations
  • Device note:
    • optimized for desktop and larger tablets
    • MobileGuard blocks viewport widths below 960px
  • Language note:
    • app-level language switching
    • do not add /bs and /en URL routing unless explicitly decided later

Manager Desk​

  • Path: apps/manager-desk
  • Purpose: the operational workspace for manager organizations
  • Device note:
    • optimized for desktop and larger tablets
    • MobileGuard blocks viewport widths below 960px
  • Language note:
    • app-level language switching
    • do not add /bs and /en URL routing unless explicitly decided later

Zgrid Mobile​

  • Path: apps/zgrid-mobile
  • Purpose: the mobile experience for residents and technicians
  • Notes:
    • resident payments are not production-live unless a real provider is integrated
    • current resident payment flow is mock / staging-provider oriented where enabled

Docs Site​

  • Path: apps/docs
  • Purpose: the Docusaurus shell for the public-safe technical documentation in docs/

Payment Warnings​

  • Lemon Squeezy is used for ZGRID SaaS subscription billing for manager organizations
  • Monri is planned for one-time resident invoice payments
  • resident payments are not recurring
  • do not claim Monri is live
  • do not claim production tenant card payments are live
  • do not claim split payments are supported