Burrow for Craft CMS agencies

Burrow's dedicated Craft CMS plugin captures entry and form events, Craft Commerce order signals, and content publishing activity. Unified with WordPress, Shopify, GitHub, and Stripe signals for agencies running mixed CMS portfolios.

Request early access Read the docs

[ Capabilities ]

First-class Craft plugin

Burrow ships a dedicated Craft CMS integration — not a generic webhook adapter. Entry saves, form submissions, and Commerce order events flow into Burrow through native Craft hooks with history backfill.

Multi-CMS portfolios, one ops layer

Run Craft for enterprise editorial clients, WordPress for marketing sites, and Shopify for stores — Burrow normalizes signals from all three into one timeline per client. No CMS favoritism.

Craft Commerce event capture

Order placed, payment completed, fulfillment updated. Craft Commerce events sit in the same project timeline as GitHub deploys and analytics, giving your retainer reviews real commerce context.

Example

Burrow PHP SDK — emit a Craft CMS event

<?php

use Burrow\BurrowClient;

$burrow = new BurrowClient(['apiKey' => getenv('BURROW_API_KEY')]);

$burrow->events()->create([
    'source'    => 'craftcms',
    'type'      => 'entry.saved',
    'projectId' => 'client_harbor',
    'payload'   => [
        'section'  => 'news',
        'entryId'  => 42,
        'title'    => 'Q1 Product Update',
        'authorId' => 7,
    ],
]);

Craft CMS agencies compete on quality. Burrow helps prove it.

Agencies that choose Craft CMS over WordPress are usually making a deliberate bet on flexibility, content modeling, and long-term maintainability. They build editorial platforms for publishers, membership portals for associations, and product catalogs for manufacturers. The work is complex, thoughtful, and — too often — invisible to the client paying for it.

The problem isn’t Craft. It’s that no WordPress management tool sees Craft. ManageWP, MainWP, and WP Umbrella are excellent for WordPress fleets — but when 30% of your portfolio runs Craft, those tools see 70% of your work. The Craft projects show up as blank spots in your operational view.

Burrow treats Craft CMS as a first-class citizen. The dedicated Craft plugin captures entry events, form submissions, and Commerce order signals through native hooks — not a generic webhook adapter that loses context. Those events join the same client timeline as WordPress activity, GitHub deploys, Stripe billing, and analytics.

When your AM reviews Client Harbor’s month, they see: “12 editorial entries published, 3 GitHub releases deployed, form volume stable at 45/week, 2 Commerce orders totaling $8,400, uptime 99.97%.” One view. One timeline. No Craft Admin screenshots required.

Multi-CMS agencies use case | Compare with ManageWP

Frequently asked questions

Do I need a custom Craft module for Burrow?

No. Install the official Burrow Craft plugin through the Craft plugin store or Composer. It uses native Craft hooks for entry, form, and Commerce events. For highly custom implementations, the Burrow PHP SDK lets you emit events from your own modules.

Does Burrow see Craft's content model?

Burrow captures event metadata — entry type, section, author, timestamp — not the full content body. It's an operational signal layer, not a content mirror. Your editors keep working in Craft's control panel.

What about headless Craft setups?

Burrow captures backend events from Craft regardless of how the front end is rendered. Whether your site uses Twig templates, a GraphQL API, or a headless React/Next.js front end, the operational signals are the same.

Does Burrow support Craft Commerce?

Yes. Order lifecycle events from Craft Commerce — placed, paid, fulfilled, refunded — flow into the same client timeline as editorial events, GitHub deploys, and other signals.

How does this compare to Craft's built-in activity log?

Craft's activity log is per-site and admin-only. Burrow's timeline is per-client-project, cross-tool, and shareable through read-only portals. When the client asks 'what happened this month?', Burrow's answer includes Craft events alongside GitHub, Stripe, and everything else.

Your agency's work deserves to be seen.

We're onboarding agencies in small cohorts to keep the quality high. Request early access and we'll be in touch.

Request early access Read the docs

Self-funded · Independent · Built for the long term