Documentation
Comprehensive documentation is on the way. In the meantime, our SDKs and plugins are open source — explore the repos below or check the product overview for the full picture.
[ Open Source ]
Burrow SDK
PHP and TypeScript SDK monorepo — transport client, event envelope builders, contract models, durable outbox primitives, and backfill processing with retries.
More SDK languages are planned as we expand platform coverage.
WordPress Plugin
Production plugin for WordPress — WooCommerce order/item/funnel events, Gravity Forms, Fluent Forms, Ninja Forms, Contact Form 7 ingestion, system heartbeats, and durable outbox delivery.
Extensible by design: we can continue adding coverage through additional plugin and core WordPress hooks.
Craft CMS Plugin
First-class Craft CMS integration — auto-detects your stack, ingests entry and form events, captures Craft Commerce order/item/funnel events, and backfills history via the Burrow SDK.
Hook-first architecture means we can keep expanding event capture across Craft plugins and core hooks.
[ Coming Soon ]
Statamic
Coming Soon
ExpressionEngine
Coming Soon[ Event API ]
Unified event ingestion.
Every event flows through a single endpoint. Plugins, SDKs, and custom integrations all use the same envelope format — scoped by organization, client, and project.
$ curl -X POST app.useburrow.com/api/v1/events \
-H "Authorization: Bearer brw_live_xxxx_your_key" \
-H "Content-Type: application/json" \
-d '{
"clientId": "cli_xyz",
"projectId": "prj_123",
"channel": "forms",
"event": "forms.submission.received",
"timestamp": "2026-03-17T08:30:00.000Z",
"properties": {
"submissionId": "sub_456",
"formName": "Contact"
},
"tags": {
"formId": "contact"
}
}'Idempotent
Deterministic event keys ensure safe retries and deduplication across outbox workers.
Multi-tenant
Organization, client, and project scoping baked into every envelope.
Durable
Local outbox with enqueue-first delivery, exponential backoff, and terminal failure handling.
[ FAQ ]
Technical FAQ
How fast can I start sending events?
For plugin installs, setup is near-zero: install, paste your API key, and events begin flowing after link/sync. For custom integrations, you can post immediately to `POST /api/v1/events` with the standard Burrow envelope.
Can I send custom events to Burrow?
Yes. Burrow exposes a single event ingestion API endpoint (`POST /api/v1/events`) that accepts a standard JSON event envelope, including custom operational events.
What sources does Burrow support today?
Today, Burrow supports the SDK, the WordPress plugin, and the Craft CMS plugin, plus direct API ingestion for custom sources. Additional integrations can publish through the same event endpoint and envelope format.
How is data scoped and isolated?
Events are scoped by organization, client, and project. Ingestion keys are tied to the linked project so event routing and access boundaries stay isolated by tenant.
Is there an SLA for Burrow?
As an early access product, we do not currently offer a formal enterprise SLA, though our infrastructure is built on highly available serverless primitives.
Ready to connect your first source?
Get started with early access. We'll walk you through setup and have you ingesting events in minutes.
Self-funded · Independent · Built for the long term