The publishing partner for independent software

Your software.
Backed by
Boonwerks.

You’ve built something people should get their hands on. Let’s turn it into a product they can buy, use, and come back to.

Private partnerships. Reviewed project by project.

Small team. Ambitious product.
You don’t have to build the business around it alone.

From working build to paid product

01 / A reason to publish together

Keep building.
We’ll help you ship.

The demo works. Now come the pricing decisions, the checkout, the release, and the customers. Bring in a partner to help turn all that work into a launch.

01

Get it into people’s hands.

From finding a price to preparing a store submission, work with us on the steps between a working build and a paid release. Give your app or game a launch you’ve thought through together.

02

Give the business side a home.

Customers need a way to pay. You need a way to get paid. We help plan the payment setup, billing, refunds, and developer payouts around your product, with clear responsibilities from the start.

03

Have a partner after launch, too.

A launch is the beginning of a product’s life. Agree with us on the billing support and publishing work you need after release, so you have someone to turn to as the product grows.

Independent by design

Keep the thing
that makes it yours.

Your idea brought it this far. Keep your original code, brand, and creative direction. We’ll work out how to support the release, with the publishing terms agreed before launch.

Our approach to publishing
You bring
The original product, code, brand, and creative direction.
We help with
Getting ready to launch, setting up payments, and the publishing work we agree to handle.
We agree together
Who does what, how we share revenue, and what comes next.

02 / Tools behind the partnership

More ways to make
your ideas work.

Give your app a way to work in the browser. Turn a useful workflow into a paid feature. Choose the tools that fit what you’re making.

TabWorker / Developer integration

Your workflows.
Your customer’s browser.

Bring the workflow you know how to build. TabWorker connects it to your customer’s approved Chrome tabs, so your app can help where they already work. The workflow and its code stay yours.

Explore the developer docs and talk to the team about a private integration. Production access is reviewed manually; public SDK packages are still planned.

Build with TabWorker

Boonwerks Credits / Private integrations in development

Turn useful work
into a paid feature.

We’re developing credit billing so customers can buy credits in your app and spend them on the work your product delivers. Give useful work a price that makes sense for your customers.

Your app has its own prices and credit balance. We’re working with private integrations first; talk to us about the billing experience you want to offer.

Discuss credit billing
For workflow developers

Build with TabWorker, then talk to Boonwerks about bringing your workflow to market. Publishing is optional. Apps and games can partner with us too, whether they use these tools or not.

03 / Start with a conversation

Every partnership
starts with a product.

A rough demo. A nearly finished game. A workflow that saves someone’s afternoon. Show us what you’re making and where you’d like a hand.

  1. 01

    Show us the product.

    An app, a game, or an original browser workflow. Tell us who it helps and where you want to ship it.

  2. 02

    Find the fit.

    Talk through where we can help, how the product will be sold, and what the partnership should look like.

  3. 03

    Get ready to ship.

    Put the agreed setup in place, prepare the release, and work through the checks for your product’s launch channel.

A few useful answers

Before we talk.

Why would a developer publish through Boonwerks?

You’ve done the work of building something. Publishing with Boonwerks brings a partner into the work of selling and supporting it: preparing the launch, connecting payments, and handling the operations we agree on. Developers building browser workflows can also explore TabWorker and our credit billing work.

Does publishing mean giving up my product?

Our approach is to preserve developer ownership of their original code, brand, and workflows. The publishing rights we need, revenue share, account arrangements, and exit terms are defined in the partnership agreement.

Do I need TabWorker or credits to publish with you?

No. Apps and games can have a publishing partnership without browser automation or credit billing. TabWorker integration and Boonwerks publishing are separate decisions.

How do payments and app stores fit?

We agree on the seller, publisher, billing, refund, and payout responsibilities for each release. A merchant-of-record arrangement is available only where specifically agreed and supported. Native purchases must follow the store’s applicable billing rules. Payment-provider and store approval remain their decisions.

Is this open to everyone? What does it cost?

We’re starting with private partnerships and reviewing each project with its developer. Services are being introduced project by project. We agree on fees and any revenue share before launch. To get started, tell us what you’re building.

The next thing you ship

Make it yours.
Let’s bring it to market.

Bring your project