Publishing for independent apps and games

You build it.
We bring it
to market.

Bring a release-ready build. We take on the work around it: listings, screenshots, store submissions, and release management. Add credit billing and fraud checks as our developer tools roll out.

Private partnerships are opening now. Credit billing and fraud tools are in development.

You keep improving the product.
We keep the publishing work moving.

From release-ready build to next version

01 / Why developers publish with Boonwerks

Your build is ready.
Let’s get it into people’s hands.

The app works. The listing, screenshots, submission, and billing still need doing. That’s the work a Boonwerks partnership is here to take on, so you can put your attention back into the product.

01

A storefront worthy of the app.

Listing copy, screenshots, release assets, and store pages that explain what you’ve built. We prepare the agreed launch materials with you, so the first impression gets the attention it deserves.

02

One partner for the next release, too.

Submit the build, follow up on review, coordinate the launch, and keep the listing current. You deliver the next version; we handle the publishing work agreed for each release.

03

Billing you can build on.

We’re developing credit billing boilerplates for checkout, credit balances, and usage charges. Set a price for the work your app delivers, with a starter integration that takes the routine billing work off your plate.

04

Less time chasing bad purchases.

Payment-fraud screening and credit-abuse checks are part of the billing tools we’re developing. The aim is to flag suspicious purchases and repeated abuse before they become another thing on your to-do list.

02 / The whole release cycle

Apple. Google. Steam.
One publishing partner.

Plan your release across the Apple App Store, Google Play, Steam, and the web. From the first listing to the next update, we agree on the platforms and publishing work your product needs.

  1. 01 / Prepare

    Make the storefront.

    Copy, screenshots, store assets, pricing, and release pages.

  2. 02 / Submit

    Work through review.

    Submission preparation, review notes, and follow-up.

  3. 03 / Launch

    Bring it to market.

    Release coordination and listings ready for your customers.

  4. 04 / Maintain

    Keep it moving.

    Store-page updates and publishing the next version.

Platform coverage and publisher-account arrangements are agreed per product. Store review and payment-provider approval remain their decisions.

Independent by design

Your product.
Your name. Your direction.

Publishing through Boonwerks gives the release a commercial home. You keep your original code, brand, and workflows. We agree on the rights and responsibilities needed to bring it to market.

Our approach to publishing
You focus on
The app, the code, and what your customers want next.
We take on
The agreed storefront, submissions, release management, and billing setup.
We agree together
The platforms, publishing rights, covered revenue, and commission terms.

03 / Less infrastructure to build

Make getting paid
the easy part.

RevenueCat-style simplicity for credit billing, with a publishing partner alongside. We’re building the starter integrations and fraud tools around the work your product sells.

Boonwerks Credits / Private integrations in development

Turn useful work
into paid credits.

Let customers buy credits in your app and spend them on useful work. Billing boilerplates are being developed for checkout, credit balances, usage charges, and refund handling, with fraud screening alongside.

Your app has its own prices and credit balance. We’ll work through the integration and the payment channels your release can use.

Talk about credit billing

TabWorker / The browser bonus

Need a browser extension?
There’s a connection for that.

Build your own browser workflows and connect them to your customer’s approved Chrome tabs through TabWorker Relay. Keep your workflow code and give your app a way to help where customers already work.

Production integrations are reviewed privately. Public SDK packages are still planned.

Build with TabWorker
Built around your product

Publish an app or game, sell a useful workflow, or add a browser feature. Choose the tools and partnership services that fit what you’re making.

04 / Your next release

Bring the build.
Let’s take it from there.

Show us what you’re making and where you want it to go. We’ll work out the publishing handoff together.

  1. 01

    Show us the product.

    An app, a game, or an original browser workflow. A demo and a release plan are a good place to start.

  2. 02

    Agree on the handoff.

    Choose the stores, launch materials, billing needs, and ongoing release work. Confirm the commission terms before launch.

  3. 03

    Get back to building.

    Deliver the release-ready build. We take on the publishing work agreed for your product, and plan how the next version reaches customers.

For developers and curious customers

Why Boonwerks?

Why is this app published through Boonwerks?

Its developer chose a partner for the work around the release: listings, screenshots, store submissions, release management, and the agreed billing setup. They can focus on making the product better while Boonwerks handles the publishing work. Apps with paid workflows can also explore our credit billing and fraud tools as they roll out.

How does the 1% commission work?

Boonwerks’ commission is 1% of sales handled through Boonwerks. Store and payment-processing fees are separate. A $100 sale means a $1 Boonwerks commission, plus applicable store and processing fees. We agree on the publishing work, refund handling, and payout terms with you before launch.

What does “RevenueCat-style credit billing” mean?

It describes the integration experience we’re aiming for: boilerplates and managed billing infrastructure for credit purchases, balances, and paid usage. RevenueCat is a product analogy; Boonwerks is independent. Our credit billing and fraud tools are in development for private integrations.

What does fraud prevention cover?

We’re developing payment-risk screening and checks for suspicious credit purchases and usage. The goal is to help you spot payment fraud and credit abuse while keeping the billing experience straightforward. The controls and review process are agreed for each integration.

Can you handle Apple, Google, and Steam releases?

We plan publishing partnerships around the Apple App Store, Google Play, Steam, and web releases. The platforms, account access, store materials, submission work, and ongoing management are agreed for each product. Store approval and availability depend on their requirements and review.

Do I keep my app? Do I need TabWorker?

Our approach preserves your ownership of original code, brand, and workflows. Publishing rights and exit terms are set out in the agreement. TabWorker is optional: apps and games can publish through Boonwerks without a browser extension or credit billing.

Can native apps use Boonwerks credit billing?

The billing integration must fit the release channel. Native purchases follow the store’s applicable billing rules. A merchant-of-record arrangement is available only where specifically agreed and supported. We confirm the seller, publisher, refunds, and payout responsibilities for your release.

How do I get started?

We’re opening through private partnerships, reviewed project by project. Tell us what you’re building, where you want to release it, and what you’d like us to take off your plate. We’ll discuss the fit and available services with you.

Your next release

More time making it.
Less time getting it out.

Bring your project