Technologies
-
Home
-
Technologies
Platforms we build on, and when each one fits
A technology page here helps you decide whether a platform fits your project before you choose a supplier. Each one covers where the platform fits and where it does not, the implementation patterns and trade-offs to weigh, how AI features attach to it, and the published Netbase Work records built on it. Start from your workflow, then check the platform against it.
Updated 19 Oct 2026
Google Cloud: fit for applications, data and AI workloads, and the proof behind it
MongoDB: the document model for data that changes shape
PostgreSQL: the relational default for transactional and JSON data
Vue.js: the component framework for widgets, configurators and admin screens
Cloudflare for web applications: fit at the edge, and the proof behind it
React: the interface library for application screens
Strapi: a headless content API behind your own front end
WhatsApp Business Platform: fit for sales, support and order-update workflows
AWS: fit for application and AI workloads, and the proof behind it
Large language models: where they fit, and how to integrate one
WordPress: content, portals and custom plugins, and where it stops
Laravel: a custom application for a workflow no packaged platform models
Magento 2 and Adobe Commerce: where the platform earns its keep
Next.js: a React front end over a headless back end
Odoo: one system for stock, purchasing, sales and accounting
WooCommerce: commerce on WordPress, and the ceiling it has