Policy downloads by list
The broker loads a list of policy numbers and gets each policy's documents with its outcome: pass, return, reject or escalate.
The broker's team logs into each portal, searches policy by policy and downloads PDFs by hand. orbit gateway works those portals with the broker's legitimate credentials and written authorization, looks up and downloads policies, premium receipts and payment notices, and stops to call a person whenever a captcha or verification appears. It is still in development: the control plane is live and the first insurer connectors are being validated with authorized access.
Every insurer has its own intermediary portal, with its own menus, its own search and its own way of serving the PDF. To get a policy, a premium receipt or a payment notice, someone at the broker logs in, searches, opens the history and downloads, one policy and one portal at a time. That work leaves no record of who downloaded what. And when someone tries to automate it with a generic bot, the portal blocks it or the bot quietly breaks on the next screen change.
A multi-tenant connectivity layer where the broker registers its encrypted credentials and launches runs for a list of policies or a single one, while a real browser works each insurer's portal with deterministic code to look up and download documents into a common model of policy, receipt and payment notice, logging every step and escalating to a person at any challenge.
From the broker's credential to a validated PDF, with every step on record.
With written authorization, the admin registers the username and password for each portal. They're stored encrypted and are never displayed or sent to the user's browser.
For a list of policies or a single one. The organization sets the pace, pauses and working hours, and a credential is never used in two sessions at once.
Chrome with a consistent identity, without hiding that it's automated, and with a network allowlist that blocks any request that would change something in the portal. Every PDF is validated before it's stored.
On a captcha, a verification code, new terms, a block or an unknown screen, the run stops and escalates. Once resolved, only the pending policies resume.
orbit gateway does not bypass security controls. It doesn't hide that it's an automated browser, doesn't use plugins to disguise itself and doesn't solve captchas through outside services: if the portal asks for verification, the run stops and a person handles it. It works only with the broker's credentials and authorization, and aims for each insurer to recognize it and add it to its access allowlist. It changes nothing in the portal. Today the first insurer connectors are written but still need to be validated in complete automated runs, and resolving a challenge inside the same session doesn't exist yet.
What the platform does today and what is still being validated.
The broker loads a list of policy numbers and gets each policy's documents with its outcome: pass, return, reject or escalate.
Receipts from each policy's history are identified and downloaded with their type. Anything that can't be classified with certainty is filed as other, with no guessing.
A captcha, a verification code or an expired password reaches the designated contact with the run's context.
Each insurer with its connector, status and capabilities. A connector is maintained once and serves every broker in its own space.
What changes when portal access stops depending on manual clicks and opaque bots.
Request demoThe operation is designed for the insurer to recognize and register it, not to slip by unnoticed.
Every run, step, document and escalation goes into an immutable audit log per organization.
The network allowlist blocks any request that isn't a lookup or a download.
On a challenge the system doesn't guess: it stops, escalates and later picks up only what's pending, without duplicating documents.
Credentials are stored encrypted, never shown or downloaded, and every use is logged.
An honest comparison between working portals by hand and doing it through a traceable layer.
Built for intermediaries who work with several insurers and need their documents outside the portal.
Policies and receipts across the whole book, downloaded with the broker's credential and with every download on record.
Each policy's receipt ready for the team that follows up on payment, without anyone having to log in and look for it.
In 30 minutes we'll tell you whether orbit gateway fits your process, what it integrates with and what it doesn't, and what a pilot looks like. If it doesn't fit, we'll tell you that too.
Run the discovery with rocky