Features

Run on a timer, or the moment data lands.

Start a transport however it suits your workflow — a schedule, an incoming message, a new file, or another transport finishing.

Not every pipeline should run at three in the morning. Some should run when a file lands, some when a message arrives, and some only after another transport has finished successfully. BARRY gives you six ways to start a run and treats them all the same way once they fire. Schedules and cron expressions cover the predictable work. Messaging triggers listen to Kafka, Event Hubs, RabbitMQ or Event Grid. File-arrival and data-sensor triggers watch locations that can sit on-premises, inside your own network. Chaining lets one run start the next, so a multi-step flow is simply transports wired together. Every trigger can pass variables into the run it starts, and those values are frozen for that run.

✓Schedules and cron expressions
✓Messaging triggers (Kafka, Event Hubs, RabbitMQ, Event Grid)
✓File-arrival and data-sensor triggers, on-prem included
✓Chain transports so one run starts the next
✓Variables resolved and frozen per run

⤢ Expand

Time-based

Cron and schedules with per-run variables.

Event-based

React to a message, a file or a sensor.

Chained

Build multi-step flows from simple transports.

Ready to unlock your data?

See how BARRY brings your on-premises data to the cloud — safely, and on your terms.