Platform · Custom Node.js
Custom commerce platforms in Node.js
Fully custom ecommerce platforms in Node.js and TypeScript for businesses whose model no platform supports: marketplaces, subscriptions, B2B and unusual workflows.
When Custom Node.js fits, and when it doesn't
For businesses whose model no platform supports, built to be maintained for years.
Typical stack: Node.js, TypeScript, PostgreSQL, Redis, Next.js, Queues.
Custom Node.js is a strong fit when
- Your core workflows don't exist in any commerce platform
- Commerce is part of a larger product, not a standalone store
- You need full control of data, performance and roadmap
Choose something else when
- A platform, even with customisation, covers your needs: that's cheaper to run
- You can't commit to a long-term engineering team
What we build on Custom Node.js
The parts of a project where our engineering makes the difference.
01
Domain-driven core
Catalogue, pricing, orders and accounts modelled on how your business actually works.
02
APIs first
One API behind the web store, mobile apps, marketplaces and partners.
03
Integration layer
Events, queues and retries built in from day one, not bolted on.
04
Operations
Monitoring, alerting, backups and an upgrade path, documented and handed over.
How it compares
The trade-offs we walk every client through before recommending a platform.
| Custom Node.js | Medusa.js | |
|---|---|---|
| Starting point | Blank page | Proven commerce modules |
| Fit to unusual models | Exact | Very high, via modules |
| Build cost | Highest | Lower |
| Long-term ownership | Fully yours | Yours, on an open-source core |
Systems we connect it to
Integrations we've built in real projects, each with its own sync design.
- ERPSAP Business One, SAP S/4HANAYour store and SAP agreeing on every price, stock level and order.See the sync design →
- PaymentsStripe, PayPal, Adyen, Checkout.comEvery payment matched to an order, and every refund to a payment.See the sync design →
- CRMHubSpot, SalesforceSales and marketing seeing what every customer actually buys.See the sync design →
- MobileiOS, Android, FlutterOne catalogue, one cart, one account, on web and in the app.See the sync design →
Questions about Custom Node.js
Why not start from Medusa instead?
Often we do: Medusa gives a proven core to extend. Fully custom makes sense when your model is so different that a commerce framework would be fighting you.
Book an architecture review
A 60-minute session with a senior architect. We review your current platform, integrations and growth plans, then send a written summary of risks and options.
- For companies with a real platform decision coming up
- NDA signed before we talk details
- The written summary is yours to keep