Strongest where we have done the work.

Seven areas we work in, with the depth of each. Each page says how deep we go in the Orchestrator and how deep in Webgentic for sites, so you know what to expect before you ask.

Counted from our own delivery records, 29 October 2026.

Seven areas, and how deep we go in each.

The Orchestrator is the agent for teams running many client sites. Webgentic for sites changes one site. The depth differs, so every card gives both.

WordPress

Orchestrator
41 client projects, from Divi to Elementor, plus WooCommerce shops.
Webgentic for sites
Pages, posts, media, custom fields, menus and theme files. Our deepest platform.
See WordPress work

WooCommerce

Orchestrator
Shops inside our WordPress projects: templates, checkout, shipping rules and the cache.
Webgentic for sites
The WordPress side of a shop. Editing products is not built yet.
See WooCommerce work

Shopify

Orchestrator
Store work for client shops. We publish no project count.
Webgentic for sites
Available for Shopify stores. Each store is set up with us.
See Shopify work

Magento and Hyvä

Orchestrator
24 client projects: Page Builder, extensions and big catalogues.
Webgentic for sites
CMS pages, blocks, category text and design settings. Not products.
See Magento work

Drupal

Orchestrator
11 client projects: entities, views, config sync and upgrades.
Webgentic for sites
The files that make up the site. Not content kept in the database.
See Drupal work

Custom PHP

Orchestrator
Hand-built PHP sites, with their own playbook. We publish no project count.
Webgentic for sites
PHP and static files only.
See custom PHP work

Servers and hosting

Orchestrator
Linux, cPanel, PHP upgrades, certificates and patches. We publish no project count.
Webgentic for sites
Not a server tool. It changes one site, not the server under it.
See server work

Craft CMS is not built yet.

Craft CMS is not built in Webgentic for sites, and we have not tried it in the Orchestrator either. We have no date, so we make no promise.

Ask about a Craft CMS job

Questions about platforms

  • Can you work on a platform that is not listed?

    It depends on the platform and the job. Tell us both and we will say whether it is a good fit. The Orchestrator also writes SEO changes, Google Ads fixes, reports and client emails, which are not tied to one platform.

  • Is the Orchestrator deeper than Webgentic for sites on every platform?

    Yes. The Orchestrator works on the whole project, including code, the server and the database, with a plan you approve first. Webgentic for sites changes content and theme files on one site, and each platform page lists exactly what it can and cannot change.

  • Where do the project counts come from?

    From our own delivery records, counted on 29 October 2026: WordPress 41, Magento 24 and Drupal 11. We publish no count for Shopify, custom PHP or servers, so we do not show one.

  • Does Webgentic for sites work on Shopify?

    Yes. It is available for Shopify stores, and each store is set up with us. The Orchestrator also does store work for client shops today. Talk to us about what your store needs.

  • Which platform do you know best?

    WordPress. We counted 41 client projects on 29 October 2026, then Magento with 24 and Drupal with 11. Webgentic for sites also goes deepest on WordPress.

  • What can Webgentic for sites not do on Magento or Drupal?

    On Magento it works on CMS pages, blocks, category text and design settings, not products. On Drupal it works on the files that make up the site, not content kept in the database. Each platform page lists the rest.

  • Does Webgentic for sites work on a server?

    No. It changes one site, not the server under it. PHP upgrades, certificates and patches are Orchestrator jobs, and each one starts as a plan you approve.

  • Something else on your mind?

    Ask us directly and a developer will reply.

    Ask a question

Tell us which platforms you run.

Join the waiting list and name them. We will tell you how deep we go on each one.