Build your own browser workflows

Give your app a browser. Build an original workflow and bring it to the Chrome tabs your customers approve. Keep your workflow logic and code on your own server.

Availability: Relay is available on the Chrome Web Store. Each integration’s availability depends on its own release and end-to-end validation. Production developer access requires manual approval. Public SDK packages are not yet released.

One connection, clear responsibilities

Your application owns its workflows, selectors, customer experience, pricing, and action policy. TabWorker Core coordinates registered services, pairing, leases, and lifecycle records. Relay executes the authorized browser work and returns observations to the paired service. Your step loop stays on your server.

Start with Relay

Understand the browser connection: capabilities, authorization, data sharing, and Stop.
Apply for developer access: the application, manual admission, server credentials, pairing prefixes, and lifecycle webhooks.
Contact TabWorker for invited integration testing.
Review data handling before requesting customer access.

SDK access is not browser access

The integration contracts are public. Official production access is admitted by TabWorker; each customer must still authorize the application’s browser access. An application key cannot authorize unrelated customers or tabs. Developer testing uses explicitly registered test connections.

Our initial partner review covers publisher identity, the demonstrated integration, requested capabilities, data recipients, and stop/revocation behavior. This is an admission policy, not a claim that every future action has been audited or is safe. Partner admission and application-wide suspension must be validated before broader onboarding.

Multiple tasks, separate grants

Up to eight authorized tabs can execute in the background. Each grant binds the service, requester, purpose, tab, sites, actions, and expiry. A customer may allow later jobs within the same scope; expanded access requires a fresh review.

Implementation and ownership

Relay and the coordination backend remain proprietary initially. We plan to publish the stable SDK and examples after the initial integrations are validated. Public documentation grants no rights to private implementation source. Application recipes remain owned and hosted by their developers.

Optional publishing and credit billing

TabWorker is operated by Boonwerks, which is opening private publishing partnerships for independent apps, games, and original browser workflows. A partnership can cover launch preparation, payment integration, and agreed commercial operations while preserving developer ownership of original code and workflows.

Boonwerks is developing credit billing for private integrations, so customers can buy credits in your app and spend them on the work your workflows deliver. Each application has its own prices and balance. Payment channels and subscription needs are agreed during onboarding.

Publishing is a separate agreement from technical integration access. It does not grant customer browser access or change Relay’s data-use requirements. There is no public self-service billing integration yet. Discuss publishing and credits with Boonwerks.

The documentation index for tools follows the current Relay launch scope.