SUBMIT
Automate carrier portals
Run rate checks, booking confirmations and appointment scheduling across the dozens of carrier portals that never shipped an API.
Logistics
Automate carrier work without losing the audit trail
Turn repetitive freight paperwork into supervised, automated runs — so planners spend their day on exceptions instead of portal logins.
Northbell
Quaystone
Fernlake
Ostrom
EXTRACTING…
Keep facility data accurate
Refresh dock hours, appointment rules, accessorial charges and site contacts from facility portals so planners work from current records.
Streamline document capture
Pull bills of lading, delivery receipts, customs paperwork and invoices out of portals and inboxes, then file them against the right load.
Track regulatory changes
Watch tariff schedules, hazmat notices and customs bulletins across agency sites, so compliance hears about a change on the day it lands.
6.3 hoursof manual entry saved weekly
84%faster carrier onboarding
92%fewer document exceptions
28m+sessions run monthly
“It helps to have someone reliable holding the browser fleet, the proxies and the retries, so our team can stay on the routing model.”
Fernlake“Two engineers, one quarter, forty-one portals. Nothing about the rollout was dramatic, which is the part I appreciated.”
Northbell“Peace of mind is hard to put a number on. The point is that I have stopped thinking about session infrastructure at all.”
OstromFAQs
What does Halyard do?
Halyard is a cloud platform for headless browser automation. We run production-grade browser sessions at scale so you never maintain your own fleet. Teams use Halyard to drive web workflows, extract records from portals, complete forms and work with applications that were never given an API.
What do companies typically build on Halyard?
Document retrieval, portal-based data entry, price and availability monitoring, onboarding flows for regulated suppliers, and agent tooling that needs a real browser rather than a scraped HTML snapshot.
What tools work alongside Halyard?
Anything that speaks the standard remote-debugging protocol: your own orchestrator, a workflow engine, a queue, or the agent framework you already run in production.
Which automation frameworks are supported?
All the mainstream open-source drivers connect over a websocket endpoint with a one-line change, and our SDKs add session replay, structured logs and retries on top.
Can I bring my own proxies?
Yes. Attach your own pool per session, or use the managed residential and datacenter pools with per-run geography rules.
Can sessions run on our own hardware?
Self-hosted deployments are available on annual plans. You run the browser layer inside your own network and keep the control plane with us, or take both.
Which regions are available?
Sessions run in seven regions across North America, Europe and Asia-Pacific, and you can pin a workload to a region for data-residency reasons.
How does Halyard relate to Deckhand?
Deckhand is our open-source authoring layer: you describe a step in plain language and it resolves to deterministic browser actions. Halyard is the runtime it executes on, and either can be used on its own.
Built for workflows where a missed field costs a day.
Let your agents open the portal, pull the record and act on live data, so your team stays on the work that actually moves freight.