Skip to main content
Arklow’s goal is to find your infrastructure’s ideal supply and demand curve. Work arrives from your services and queues. Arklow accepts it durably, routes it, and holds excess demand until the destination can absorb it. During a downstream slowdown, excess work remains in Arklow and is released as capacity recovers.
Arklow can also track work that happens externally. Use the SDK when attaching existing pipelines to Arklow is impractical.

Quickstart

Send an action through Arklow and settle its first delivery.

How Arklow works

One action across lanes, admission, shared capacity, and settlement.

​
Core resources

Actions

Define the work your platform performs.

Sources

Bring work in over HTTP or from a queue you already run.

Destinations

Deliver work to webhooks, Pub/Sub, or SDK listeners.

Rules

Route, tag, transform, skip, or terminate work before dispatch.

​
Capacity management

Admission control

Waiting, running and unsettled limits, pacing, and caps.

Metrics

Add the telemetry that already describes your systems.

Capacity pools

Protect destinations that draw from the same underlying resource.

Scale targets

Connect protected work to capacity Arklow can recommend or manage.

​
API reference

OpenAPI

Browse the complete HTTP API.