React
Role: Client interface.
Builds reusable customer and administrative interface components.
Why here: Keeps discovery, operations, and review surfaces composed from shared UI parts.
Hypler: SI infrastructure and systems software
Products and infrastructure
Rangoon operating-system targets
In development.
Ubuntu — Server/headless architecture
Debian — Server/headless architecture
Rocky Linux — Server/headless architectureRed Hat Enterprise Linux (RHEL) — Server/headless architecture
Fedora — Server/headless architecture
SUSE Linux Enterprise (SUSE Enterprise) — Server/headless architecture
openSUSE — Server/headless architecture
AlmaLinux — Server/headless architecture
Amazon Linux 2023 — Server/headless architecture
Arch Linux — Server/headless architecture
Windows — x86-64
macOS — Intel x86-64; Apple silicon M-series arm64
LNSAT operating-system targets
In development.
- Ubuntu — Server/headless architecture
- Debian — Server/headless architecture
- Rocky Linux — Server/headless architecture
- AlmaLinux — Server/headless architecture
- Amazon Linux 2023 — Server/headless architecture
- Arch Linux — Server/headless architecture
- Windows — x86-64
- macOS — Intel x86-64; Apple silicon M-series arm64
IZIOS implementation choices
IZIOS processes supplier inputs into normalized records, combines structured filters with vector retrieval, serves product data through APIs, and keeps commerce transactions separate from availability truth.
- Supplier ingestion
- Normalized records
- Structured filters and vector retrieval
- APIs
- Commerce transactions
These are documented implementation choices. Supplier availability remains source-controlled; compile-time contracts and runtime validation serve different checks.
TypeScript
Role: Application contracts.
Adds compile-time types to client and server code.
Why here: Makes data shapes and interface changes easier to inspect before runtime.
Node.js
Role: Server runtime.
Runs the API and supporting application services.
Why here: Keeps server-side processing separate from the browser interface.
Express
Role: HTTP API.
Routes product, account, and operational requests through server middleware.
Why here: Provides a defined API boundary for connected clients and workflows.
PostgreSQL
Role: Relational records.
Stores durable catalog, workflow, and transaction records.
Why here: Supports joins, constraints, and transactional changes where product data must stay reviewable.
pgvector
Role: Vector retrieval.
Stores embeddings with relational records and compares vectors by similarity.
Why here: Supports broader-intent discovery while structured filters keep exact constraints explicit.
Vite
Role: Frontend build.
Builds and serves the web application during development.
Why here: Keeps the client build path fast and explicit.
