Breyus
AI-assisted commodity trading platform that connects sourcing, partner discovery, negotiation, documents, and admin operations.
What the product covers.
Breyus brings multiple trade workflows into one platform: marketplace discovery, buyer/seller negotiation, deal lifecycle tracking, document handling, AI partner matching, KYC/admin operations, disputes, alerts, taxonomy management, and content publishing. The platform spans a buyer/seller app, admin portal, backend API, and AI service.
The decisions inside the build.
A concise account of the operating problem, the resulting system shape, and the technical decision that kept the work coherent.
Problem
Cross-border trade information arrives with inconsistent company names, categories, and record shapes. The product needed one dependable layer for discovery, analysis, negotiation, documents, and trade operations.
System shape
NestJS owns authenticated product and transactional workflows. FastAPI handles matching, retrieval, and market-analysis work, while PostgreSQL, MongoDB, Redis, and background workers keep relational records, flexible documents, and long-running jobs in the right operating paths.
Decision record
Slow ingestion and market-analysis work runs outside request-response paths so search and product actions stay responsive while pipelines recover independently.
What the contribution actually covered.
The build is complete and pre-launch. The record count describes ingested source data, not production users or completed transactions.
- 01
Role-aware discovery, inventory, purchase request, negotiation, wishlist, trade, notification, and company-profile workflows.
- 02
Administration and content operations for KYC, disputes, taxonomy, alerts, publishing, and platform activity.
- 03
AI-assisted matching, ingestion, normalization, search, analytics, uploads, trade documents, and authenticated real-time messaging.
The working parts, without the theatre.
- 01React
- 02NestJS
- 03FastAPI
This was a private engagement, so the public note is intentionally limited to the verified project scope.
The build is complete and pre-launch. The record count describes ingested source data, not production users or completed transactions.
No public destination published