Build with TabWorker Relay

Build a feature worth
coming back for.

Your customers have things to do in their browser. You have an idea for making them easier. Bring your original workflow to Relay and give your app a way to help, right in the tabs they approve.

Tell us what you’re building →
Explore the integration docs →

Take it from useful to sellable

Build with TabWorker. Publish with Boonwerks.

You’ve figured out a better way to get something done. A private Boonwerks partnership can help you turn it into a product customers can buy, from preparing the launch to handling the agreed billing and publishing work.

Give useful work a price.

Let customers buy credits in your app and spend them on the work your workflow delivers. Boonwerks is developing this billing path for private integrations, with your app’s own pricing and balance.

Keep what makes it yours.

Your original code, workflows, and product direction stay yours. Decide together where a publishing partner can help, with services and commercial terms agreed before launch.

Discuss publishing and credits ↗

Publishing is optional. The application below is for TabWorker integration access. Publishing and billing are arranged separately with Boonwerks.

Apply for Relay developer access

All fields are required. Do not include passwords, API keys, customer content or private recipe source.

Your application

Tell us who operates the service and where customers can learn about it.

Your name and roleWork emailLegal operator and countryApplication nameApplication website (HTTPS)Privacy policy (HTTPS)Security contact email

The browser work

Describe the integration. Your proprietary recipes stay on your server.

What tasks will customers ask your application to complete?Include the intended users and whether you are requesting testing or production access.What browser access does it need?Service domains, target websites, tabs, actions and observations, including screenshots and file uploads.

Data and safeguards

Name the actual recipients and controls. Identify anything still unverified.

Where does Relay data go?Hosting, storage, model inference, gateways, logging and any other recipients. Say explicitly if there is no model provider.How is data retained and deleted?Page captures, screenshots, task results, logs and backups; include account deletion and provider retention.Who can read customer content?Staff, support, contractors and providers; describe consent, training restrictions and access logging.How do you enforce customer authorization?Tab scope, customer isolation, Stop, expiry, revocation, reconnect and confirmation of consequential actions.

Show us the integration

Use synthetic data. We will arrange private reviewer access after receiving your application.

Demo link, setup steps and known limitationsDescribe a harmless test task and your validation evidence. Do not include credentials or customer data.

Before you submit

Use Relay data only for the disclosed, customer-authorized purpose and comply with Chrome’s Limited Use rules.
No general-purpose model training, advertising, resale or unrelated profiling with Relay data, including through processors.
Disclose recipients and require permitted handling downstream. Obtain consent to read specific support content; restrict and log necessary security or legal access.
Notify TabWorker before expanding access or changing recipients and data practices, and promptly report incidents. Do not share credentials with unapproved developers.

By submitting, you send these answers to Boonwerks for integration review and follow-up. Applications are retained in our review correspondence. See our privacy policy; contact team@tabworker.com for access or deletion requests.