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.
By Netbase Editorial Team · Reviewed by Huy Nguyen (David), CEO · Updated 4 Nov 2026
MySQL and MariaDB: fit for business applications, and how Netbase runs them
DigitalOcean: fit for applications and their data, and where the limits are
Vue.js: the component framework for widgets, configurators and admin screens
PostgreSQL: the relational default for transactional and JSON data
MongoDB: the document model for data that changes shape
Google Cloud: fit for applications, data and AI workloads, and the proof behind it
React: the interface library for application screens
WhatsApp Business Platform: fit for sales, support and order-update workflows
Strapi: a headless content API behind your own front end
Cloudflare for web applications: fit at the edge, and the proof behind it
WordPress: content, portals and custom plugins, and where it stops
Large language models: where they fit, and how to integrate one
AWS: fit for application and AI workloads, and the proof behind it
Laravel: a custom application for a workflow no packaged platform models
WooCommerce: commerce on WordPress, and the ceiling it has
Odoo: one system for stock, purchasing, sales and accounting
Next.js: a React front end over a headless back end
Magento 2 and Adobe Commerce: where the platform earns its keep