04 / Architecture

System overview

How the main systems connect — Odoo modules, web front ends, APIs, and the database underneath.

HR Ops product stack

Published Odoo module with a Next.js portal on the same workflows.

  1. 01
    Next.js portal (employees / managers)

    Forms, role actions, status timeline, checklist progress, analytics UI.

  2. 02
    Odoo 18 HR Ops Suite

    Transfer, IT hardware, clearance models · multi-step approvals · PDF reports · security groups.

  3. 03
    PostgreSQL

    Transactional records, attachment storage metadata, report data.

  4. 04
    Distribution

    Odoo Apps Store package + GitHub source for install / review.

Enterprise finance & payroll ops

Private client work — batch petty cash, expenses, and payroll on Odoo.

  1. 01
    Users (finance / HR / holders)

    Submit, approve, and close inside Odoo backends.

  2. 02
    Odoo apps (petty cash, expenses, payroll)

    Batch sheets, multi-approver rules, project/city review, payslip / labor costing.

  3. 03
    ORM + PostgreSQL

    Batch writes, constrained states, and reporting queries.

  4. 04
    Outputs

    Approved sheets, payslip runs, cost allocation reports.

Mobile / hub API layer

REST APIs for mobile and hub apps that talk to the ERP.

  1. 01
    Mobile & hub clients

    Field and ops apps that call the API.

  2. 02
    REST controllers (Odoo)

    Auth, projects, HR, requests — consistent JSON responses.

  3. 03
    Domain models + record rules

    Business rules and access stay in Odoo; the API exposes them.

  4. 04
    PostgreSQL

    Source of truth for transactional data returned to clients.

Lann Pya product

Public content site — Odoo backend, Myanmar Next.js front end.

  1. 01
    Next.js (Myanmar UI)

    Guides, news, and community pages.

  2. 02
    Odoo content / auth / feeds

    Editorial workflow, users, REST for front-end consumption.

  3. 03
    PostgreSQL

    Content and user data for the live site.

For project details and links, see work.