Secure install
Buyers receive a package payload, but not private repository URLs, object storage paths, creator secrets, or hidden source metadata. This is protected distribution, not full closed-source execution.
Docs
Monetization
Payments gatedMonetization should match how the capability is delivered.
OlyWork supports free secure install, paid secure install, and protected runtime bridge. The product can prepare pricing and entitlement logic before live Stripe charging is enabled.
Distribution and pricing modes
Mode
How buyer pays
What buyer receives
Best for
Free secure install
Buyer pays nothing
Encrypted install payload through OlyWork
Open/free distribution with safer delivery
Paid secure install
One-time payment
Encrypted install payload after purchase
Commercial packages that can run locally
Protected runtime bridge
Subscription, hourly, per-run, or session pricing
Remote interface/output, not raw source
Premium logic that should stay protected
Protection model
Protected bridge
Buyers call OlyWork through MCP/API/CLI connectors. Creator logic can stay behind an entitlement boundary and return only safe output, status, and logs.
Entitlement per action
Access tokens, purchase status, subscriptions, refunds, disputes, revocation, and suspension should gate install and protected usage.
Recommended pricing rules
Local paid install
Use one-time pricing for packages that can safely run locally after install. Good for templates, skills, workflow configs, and open/commercial MCP packages.
Protected runtime bridge
Use subscription, hourly, per-run, or session pricing when the creator’s premium logic, orchestration, or private resources should not be delivered locally.
Marketplace fee model
Line item
Example
Meaning
Gross sale
$100.00
Buyer payment before fees
OlyWork platform fee
$20.00
20% marketplace commission
Stripe/payment fee
Variable
Charged by payment processor
Creator net
Remainder
Paid out after processor fees and disputes settle
Default commission
OlyWork should use `PLATFORM_FEE_BPS=2000` for a 20% marketplace commission on paid secure installs and protected usage when monetization is live.
Live monetization launch checklist
Keep checkout gated until ready
`MONETIZATION_ENABLED=false` should remain the default until company, tax, Stripe, payout, refund, dispute, and accounting workflows are proven.
Stripe Connect onboarding works for a real creator account.
Checkout creates a purchase and access token.
Platform fee is calculated and recorded correctly.
Refund/dispute events suspend or revoke access as expected.
Creator earnings dashboard is backed by real ledger events.
Payout readiness is shown clearly before accepting paid listings.
Plain-language buyer copy
Free secure install
Get access for free. OlyWork still delivers the package through a protected install token instead of a raw file link.
Paid secure install
Pay once and install locally. You receive an installable package, not the creator’s private repo or storage path.
Protected cloud use
Use the capability remotely through OlyWork. The creator’s private logic stays protected and you receive only the output.