Supported Platforms

Three production stacks, three pages. Most visitors land here to figure out which of the pages below describes the site in their head, not to read another pitch. Pick the stack. Each child page goes into capability detail, the failure modes that turn up in audits, and the work pattern that fits that platform.

Primary expertise. PHP-FPM tuning and MySQL or MariaDB query work where the slow log actually gets read, Redis and Memcached wired correctly for real object caching, and Docker stacks built on Caddy, PHP-FPM, MariaDB, and Redis for teams that want the price-to-performance of a bare VPS. Hetzner, DigitalOcean, and Cloudways for teams that prefer a managed surface.

WooCommerce work includes checkout performance, subscription handling, payment gateway integration, and order volume scaling. Custom plugin maintenance keeps bespoke code current with WordPress, PHP, and MySQL or MariaDB versions. Headless front-ends in Next.js or React talking to WordPress via the REST API or GraphQL are built and maintained under the same agreement. Full WooCommerce and custom plugin scope.

Theme performance tuning, structured sections, and Liquid organisation that stays maintainable over time. App permission audits before anything gets installed store-wide, checkout hardening, and carding and bot-abuse mitigation on the sensitive endpoints that attackers actually target.

Custom app maintenance for private and custom public apps built on Remix or Node, with their own webhook handlers and scope requirements. Store-to-store migrations where theme, apps, metafields, and DNS cutover have to land together, plus Shopify SEO across collection templates, canonical handling, and product JSON-LD. Theme audits, app permission reviews, and checkout work.

Apps running on Vercel, on Cloudflare (Workers, Pages), or self-hosted on Node. ISR and edge runtime work, SSR behaviour tuned against real traffic, and env hygiene that keeps secrets out of commits and client bundles. CSP and middleware rate limits are configured intentionally rather than left at framework defaults.

Headless CMS integrations and the database or content API behind the app are treated as part of the platform, not someone else’s problem. Deployment targets, caching strategy, and revalidation are reviewed as one system rather than three. ISR, edge runtime, and dependency hygiene specifics.

One agreement shape covers all three stacks; the tier breakdown, hour allocations, and ZAR pricing live on a single page.