What we build with it
Public storefronts that have to be fast on a phone, and the application behind them: back offices, dealer portals, admin tools and dashboards. Shopflooring serves a catalogue of 118,651 rows with a pricing engine behind it, and Norpex reused that storefront architecture for a multi-vendor marketplace.
One application, several audiences
Oryx, a distribution platform we are building, serves four portals — a storefront, a dealer portal, an operations back office and a sales CRM — from one Next.js application over one schema, so trade pricing, inventory and customer records cannot diverge between surfaces.
The application stays the source of truth
On our own Growth Engine, the Next.js app is the source of truth and the workflow engine is a stateless task runner called by webhook, so the state lives where it is owned. Contractor OS keeps its books in one schema where every financial document posts a balanced journal entry.
When it is not the answer
A brochure site does not need an application framework, and a product that lives on a phone may need a native client first. The free audit says which.