Skip to main content

AI that edits like your editors.

Assoc.dev builds Drupal 11 platforms where Canvas, recipes and one design system of single-directory components run dozens of sites from one codebase. AI agents build pages there over MCP with exactly the permissions a human editor has, and every step they take leaves a trace.

core
Drupal 11
page builder
Drupal Canvas
agents
MCP, editor role
hosting
Hetzner, Germany
Fleet matrix · one codebase · 36 sites sample fleet

select a lamp to read it

  • nominal
  • agent working
  • deploying
  • needs attention
  • select a lamp to read it

01 / Services

4 pillars, 1 platform

Four things we build, all on the same platform.

  1. 01

    Platform builds

    Drupal 11 with Canvas for visual page building, recipes for repeatable site setup, and a design system of single-directory components your editors lay out themselves.

    • Drupal 11
    • Canvas
    • recipes
    • SDC library
  2. 02

    AI built in

    Drupal AI integrations, agents that build and edit Canvas pages over MCP as an editor would, content assistants, semantic search over your own content, translation, and accessibility and SEO checks before anything goes live.

    • Drupal AI
    • MCP agents
    • RAG search
    • translation
    • a11y + SEO checks
  3. 03

    Multisite fleets

    Dozens of sites from one codebase and one design system. Each site gets its own database and its own configuration, applied by a recipe rather than copied by hand.

    • one codebase
    • per-site config
    • site recipes
  4. 04

    Platform care

    Hosting on Hetzner provisioned with Ansible, security updates, monitoring, and a remote dashboard that shows every site's version and health in one place.

    • Hetzner
    • Ansible
    • updates
    • fleet dashboard

02 / Agent trace

sample run · clinic-north

Every agent step is a line you can read.

The agent asks Canvas which components exist, drafts the page, places them, and stops where your editors would stop: at the permission to publish.

Run the full sample on the platform page
09:41:02agentcanvas_list_componentsas content_editorok · 62 components
09:41:04agentcanvas_create_page"Spring open day"ok · draft
09:41:06agentcanvas_add_componenthero_bannerok · slot content
09:41:08agentcanvas_add_componentevent_scheduleok · slot content
09:41:11agentcanvas_publish_auto_savesdenied · role lacks "publish content"
09:43:20humanM. Okafor (editor)approved + published

03 / Permissions

The agent never gets an admin account. It gets the editor role, the same review queue, and a revision you can roll back.

Drupal permissions · Canvas auto-save · content moderation · revisions

04 / Fleet

figures from the sample fleet

Thirty-six sites. One codebase. One design system.

sites
36
each with its own database
recipes
7
one per kind of site
components
62
SDCs placeable in Canvas
deploy
6 min
median, all 36 sites

A new site is a recipe, not a copy.

A recipe installs the modules a kind of site needs and imports its configuration. The fortieth clinic site starts from the same tested setup as the first.

web/sites/ · sample excerpt
site recipe state deployed
clinic-north assoc_clinic agent working 09:12
faculty-science assoc_faculty deploying now
research-portal assoc_docs update queued yesterday
summer-school assoc_event nominal 09:12

05 / Care

monthly retainer

After launch, we watch the lamps.

  • Hosting in Germany. Hetzner servers, provisioned and rebuilt with Ansible, so no server is a snowflake.

  • Security updates. Core and contrib advisories applied across the whole fleet in one release window.

  • Monitoring. Uptime, cron, queues, backups and certificate expiry, checked for every site.

  • A remote dashboard. One view of every site's version, pending updates and health.

dashboard.assoc.dev/fleet
  • research-portal 11.2.3 → 11.2.4
  • ethics-board 11.2.3 → 11.2.4
  • concert-hall release 2026.09.30
  • 33 more sites 11.2.4 · backups 02:40

06 / Engagement

3 stages, each one optional

Two weeks to a plan. Twelve weeks at most to a platform.


  • 2 weeks · fixed price

    Discovery sprint

    We audit your sites, editors' workflow and content, and you get an architecture, a recipe plan and a fixed quote for the build.

    you bring
    two editors for two workshops, read access to your sites



  • 8–12 weeks · milestone billing

    Platform build

    Drupal 11, Canvas, your component library, site recipes, the agent wired to your roles, and content migrated into the first sites.

    you bring
    a product owner, two hours a week, sign-off at each milestone



  • monthly · cancel with 60 days' notice

    Platform care

    Hosting, updates, monitoring and the fleet dashboard, plus a set number of hours for new components and sites.

    you bring
    one named contact for releases and incidents


Compare scope and prices of the three engagements

07 / Work

sample case studies

What changed for the people running the sites.

sample case study

Northvale Health: 41 clinic sites onto one codebase in 11 weeks

Forty-one clinic sites had drifted apart over eight years. One clinic recipe, one component library and the Canvas agent let the web team publish landing pages without opening a ticket.

sites
41
build
11 wk
tickets/mo
−63%
sample case study

Ostrander University Press: answers from 18,000 articles

Semantic search with cited sources over the press's own archive. Every answer links the three passages it came from.

search exits to a page, not a dead end: 71%

sample case study

Kettle & Rail: timetable pages in six languages by morning

Automated translation drafts each changed timetable page overnight. A native speaker approves it before 07:00, or the previous version stays up.

6 languages · human approval on every page

08 / Fit

read before you book

Is this a fit?

We say no early, so neither of us spends a month finding out.

  • Rhea Achterberg
    platform lead · sample

  • Tomasz Nowicki
    AI and MCP integration · sample

A good fit

  • You run five or more sites that should share a look and a codebase.
  • Your editors want to build pages without waiting for developers.
  • You want AI help, but only inside the permissions you already trust.
  • You are on Drupal 10 or 11, or ready to move.

Not a fit

  • A single brochure site with no plans to grow.
  • A fixed launch date under eight weeks away.
  • You want AI to publish without a person signing off.
  • Budgets under €40,000 for the build (sample threshold).

Book a platform review.

A 45-minute call with two of our engineers. We look at your sites, how your editors work, and where AI would help and where it would not.

  • reply within one working day
  • written summary within three working days
  • no sales list; your details stay with us

Prefer email? Write to review@assoc.dev.

Your platform

Tell us who to reply to.

Enter an address like name@organization.org.

Optional

Pick the closest range.

We answer within one working day.