Shipped systems
Six builds running in production, described by what actually went wrong and what was done about it. The connection leak. The privilege escalation path. The race that dropped cart updates. That is the part worth reading.
What has The Cubas built?
The Cubas has shipped multi-vendor marketplaces, ecommerce platforms, booking applications and developer tools using Next.js, React, TypeScript, Node.js, PostgreSQL and MongoDB. Each build is documented with the engineering decisions and production incidents behind it rather than a feature list.
Projects live
11
Shipping since
2021
Published
IEEE, 2023
Stack
Next.js, Node.js, TypeScript
6 builds · 4 categories
Marketplaces, stores, booking systems and developer tools. Each one links to a full write up of the architecture and the problems that shaped it.
ProductionEcommerce · 2025
Multi-vendor marketplace running in production
A bilingual storefront, vendor dashboards and an admin back office in one marketplace, running in production on its own domain.
ProductionEcommerce · 2025
Home and decor store, hardened after launch
A home and decor storefront with customer and admin dashboards, Chart.js reporting and PDF invoices, maintained in production across more than 200 commits.
ProductionMarketplace · 2025
Farm to table marketplace with a split client and API
A marketplace connecting local farmers listing produce with customers who browse, order and pay, built as a Next.js 15 client against a separate Express API.
LiveBooking · 2024
Hotel booking from search to payment
A booking application covering listing discovery, reservations, property management and payment, with seeded demo accounts so anyone can walk the full flow.
Open sourceDeveloper tools · 2025
SQL to entity relationship diagram, with no server
Paste SQL from any dialect and get an entity relationship diagram. No account, no upload, no server, and 247 tests covering four dialects.
Open sourceDeveloper tools · 2025
JavaScript playground with a real console
Write JavaScript and watch console output and a live DOM preview beside the editor, with a sandbox that an infinite loop cannot wedge.
Who builds this
Ashraful works across backend decisions and frontend detail. He designs typed REST APIs and data models, builds background jobs and authentication flows, then brings those pieces into Next.js and React interfaces that stay usable under real conditions.
The experience that shaped how he works came after launch rather than before it. Investigating a connection leak that only appeared under load. Closing a privilege escalation path found in his own audit. Fixing a race condition that dropped cart updates during rapid clicks. Those taught him to verify how a system behaves, not how it reads in code.
Tests, lint, typecheck and build before a pull request is called ready, then an end to end check against production. Some checks passing is not the checks passing.
Audit findings get reproduced first. Some turn out to be false positives, and some implied fixes would break features that already work.
A checkout that refetches price and stock before charging a card was flagged as wasteful. In a payment flow that is the correct behaviour, so it stayed, with the reason written down.
When a fix needs an architecture change with more regression risk than it removes, it is listed as deferred with the reason rather than quietly dropped.
A rule that applies to a whole class of routes is mounted where that class is mounted, so a new route cannot forget it.
Engineering services
The same practices these projects were built on, applied to your product.
Send us the brief or the broken thing. We will tell you what it takes and whether it needs building at all.
Prefer to skip the form? Message us on WhatsApp or email yousuf@thecubas.com