Sell bots you build

Selling a workflow as a JSON template requires every buyer to own and host the automation platform themselves - a recurring cost and an operational burden on your customer, not you. Selling it embedded in a platform means an embedded/OEM licensing arrangement instead: a negotiated commercial agreement covering distribution rights, branding constraints, term and support, priced per distributor and rarely published. Both routes put someone else's infrastructure between you and your client.

The artifact model avoids both: you compile your workflow once into a standalone desktop artifact, deliver it to your customer, charge your own price, and - on the licence tiers that include them - keep reseller rights. No per-customer platform cost, no negotiated OEM agreement, nothing for you to host - the launcher fetches its configuration from the directory's published endpoint at launch. The embedded licence comparison sets the two models side by side on verifiable dimensions.

A delivered artifact is no longer a black box you cannot recall. A bot published with server-controlled activation stops at its next launch when you update the stored configuration's activation state - within the published cache window - and the launcher shows your message instead of failing silently. You never touch the client's machine.

You can also choose public or password-protected delivery. One qualification, stated plainly: password protection is only meaningful when the delivered configuration is encrypted. A plaintext configuration is readable by anyone who knows the bot's id, so there the password gates execution only, not the workflow definition. The directory's security page documents both strengths in full.

Illustrative numbers, not a promise: check the product pricing page for the current licence tiers and their billing models. You build one inventory-monitoring bot and sell it to three clients at $600 each: $1,800 revenue against your licence cost, with no per-client hosting or platform instance for you or your clients. If one client's contract ends, you disable that copy's activation state remotely and re-sell the bot to the next client without shipping new binaries.

The honest comparison: this is a model comparison, not an absolute saving claim. The embedded-licence alternative is a negotiated annual agreement covering your whole distribution; which model is cheaper depends on your volume and term.

The cost of building and selling is the product licence, tiered by the commercial rights you need; reseller rights are included in the Agency and Enterprise tiers, not every tier. The product pricing page is the authoritative list of tiers, their billing models and their exact terms - this page links to it rather than restating prices. Delivery itself carries no per-client hosting, no per-sale step through us and no metered runtime.

Compare that with the two alternatives: self-hosting a platform per client carries a server bill and an operations burden for every account you create, and an embedded/OEM licence is a negotiated annual agreement covering your whole distribution. The artifact model avoids both, and your licence cost is published in exactly one place - the pricing page - so what you pay is always checkable there rather than restated here.

On lifetime availability: the reseller tiers have been sold as lifetime licences, and the product is moving new sales to subscription billing. The lifetime reseller offer page states current availability and exact terms; if you buy while a lifetime tier is still offered, the terms published at purchase are the ones that apply to it. This page deliberately restates no deadline and no price - the product's own pages are authoritative and current.