PRIVATE B2B MARKETPLACE

Dead Market

A private inventory and deal platform with separate brand, merchant, and operator workflows.

Full stack developmentPrivate project · In development

Discuss a similar project ↗

DEAD MARKETPRIVATE B2B MARKETPLACE

Brand portalMerchant portalAdmin portal

Express API Auth · Listings · KYB · Deals

PostgreSQLWorker boundary

ARCHITECTURE ILLUSTRATION · PRIVATE PROJECT

01 / THE PROBLEM

The challenge

Support business onboarding, private inventory access, deal negotiation, and document review without mixing company and role boundaries.

02 / ENGINEERING APPROACH

How it’s structured

Separate web, Express API, and worker services share TypeScript contracts. PostgreSQL adapters persist core marketplace data. Session-scoped reads distinguish admin operations, brand inventory, and merchant purchasing flows.

Service separation

Next.js web, Express API, background-worker boundary, and shared domain contracts.

Data & access

PostgreSQL/Prisma schema and SQL migrations, session-aware storage adapters, and company/role-scoped reads.

Operations

Docker Compose brings together web, API, worker, PostgreSQL, and Redis; CI validates the codebase.

03 / IMPLEMENTATION

What the project includes

Company onboarding and KYB review for brands and merchants.
Role-scoped listing discovery, moderation, and private inventory rooms.
Draft offers and role-appropriate deal negotiation actions.
Protected document upload/review/download with checksum metadata.
Scoped notifications, audit events, PostgreSQL migrations, and containerized service boundaries.

04 / CURRENT STATE

What’s available

An implemented marketplace foundation with backend contracts for listings, deals, KYB review, protected documents, notifications, and audit events. This is a private project with development workflows, not a claim of a publicly launched marketplace.

Scope & limitations

Payments are intentionally not integrated. Development OTP handling, seeded data, local document storage, and offline frontend fallback remain part of the current setup. Production email delivery, object storage, queue execution, monitoring, and scale readiness require additional infrastructure work.