Developer signup

Developers

Make predictable monthly income

Bytewells is an Actor Store where you can earn recurring revenue by offering monthly rentals and short-term passes for your existing Apify Actors. Developer signup is open.

Open now

Publishing and signup are live

Create an account to import your Apify Actors and publish them in the Store.

Keep more of every rental

Platform commission is 10%, against 20% on Apify. Renters you bring yourself carry 0%.

One command to migrate

You already have a product—why sell it in only one marketplace? Import your Actor onto another shelf with a single CLI command; source, README, and input schema come with it.

No exclusivity

Keep your Apify listing and pricing. Bytewells is an extra channel for the same Actor.

Renters don't get your source

You keep ownership. Renters run the built image and never receive the source. We may inspect it for legal, compliance, or security reasons.

FAQ

Questions developers asked us

These come from the developers we have already talked to.

Launch and demand

Is Bytewells open?+
Yes. Developer signup is open. Create an account, import your Actors, and list them in the Store.
Do you have paying renters today?+
We are building supply and demand at the same time: filling the Store with developers' Actors and our own, while growing the renter side. We do not have paying renter numbers to share yet, and we would rather say so than invent them.
How will renters find my Actor?+

Four ways:

  • Customers you bring yourself pay 0% commission.
  • Every Actor gets its own Store page that search engines can read.
  • We publish comparison pages, organic and paid traffic will boost your Store page.
  • AI agents can discover your Actor through the MCP API.

Your own audience matters most in the first months, which is why referred renters carry no commission.

Is there documentation or an example I can look at?+
The docs cover importing, publishing, billing, passes, the API and MCP. There are no live third-party rentals to show yet.

Listing an Actor

How do I get my Actor onto Bytewells?+
Sign up with bw signup, then run bw import apify you/your-actor. Import copies source, README, input schema and run defaults, builds on our builders and creates a free draft listing. Set rent with bw publish --price, then publish. You can also connect Apify in the console and pick Actors from a list.
What does the import access in my Apify account?+
It only reads. It never changes your Apify Actors. The CLI uses your Apify API token, from --apify-token or APIFY_TOKEN. The console uses Apify OAuth, where Apify asks you to authorize profile and full API access; we store that token encrypted and you can disconnect it in Settings or revoke it in Apify. Run it with --dry-run first to see what it would do without writing anything.
Do I have to change my Actor code or add billing code?+
No. Bytewells speaks the Apify API, so the Apify SDK, Crawlee and apify-client work unchanged. The platform sets the API URL and a token that only works for that run. Rentals and passes are handled by the platform, so there is no billing code in the Actor.
Can I publish from a local folder and keep both stores in sync?+
Yes. bw push in any Actor folder builds it on our side, with no Docker needed on your machine. bw import apify --update re-imports an Actor that already exists here. One codebase can ship to both stores.
Do I have to leave Apify?+
No. There is no exclusivity. Keep your Apify listing, pricing and users as they are. Bytewells is an extra sales channel for the same Actor.
Which Apify SDK features work on Bytewells?+
Datasets, key-value stores (named ones too), request queues with deduplication and locking, webhooks, schedules, and proxy password resolution. Saved tasks are not supported yet. Pay-per-event pricing is not available at launch. It is planned as an option from December, and rental stays the default. If your Actor calls Actor.charge(), test it on a draft listing first, because we have not certified that path yet.

Pricing and payouts

What does Bytewells take?+
10% of each rental and pass charge, and 0% on customers you refer. Stripe's card and billing fees on the charge pass through to you at cost, with no markup. A typical $17.50 rental nets about 85%, or about 95% from a referred renter. Compute charges pay for the runtime and are not split with you.
How and when do I get paid?+
Every sale is recorded in an earnings ledger and becomes payable 14 days after the customer pays, which covers the refund window. We pay once a month, in one Stripe transfer, when your payable balance reaches $50. Smaller balances roll over. You can publish a paid listing and start earning before you verify with Stripe, but you must complete Stripe's identity and bank checks to receive a payout.
Which countries can be paid?+
Today, paid listings need a payout country in the EU, Liechtenstein, Norway, Switzerland, the UK, the United States, Canada, Bosnia and Herzegovina, or Pakistan. Payouts run through Stripe Connect on ThoughtPivot, Inc. (US). We are working on expanding developer payouts globally; until your country is supported, you can publish free Actors and build traction. Your payout country is fixed once your Stripe account exists.
How do I decide the monthly rental?+
You set it after import: bw publish <actor> --price 29 --trial-days 3 (trial 1–30 days, default 3 when you publish). Optional Flash (1 hour), Burst (24 hours), and Sprint (7 days) passes are separate. Apify Store pricing is pay-per-event, so import does not copy a monthly rent from Apify.
Is there a minimum commitment or contract?+
Not for developers: no contract and no exclusivity. Renters pay monthly and can cancel at any time. Cancelling stops the next renewal, they keep access until the paid period ends, and unused days are not refunded. A price change applies to new rentals only. Existing rentals keep the price and commission they started with.
Are there special terms for early developers?+
No. Every developer gets the same terms: 10% platform commission, and 0% on customers you refer. We do not promise featured placement at launch.
What happens to my earnings if a sale is refunded or disputed?+
A refund or lost dispute is deducted from your earnings. If the money was already paid out, it is netted from your next payout. A dispute freezes that earning until it closes, and it comes back if we win.

Running Actors

Who pays for compute when someone runs my Actor?+
The renter. Runs are billed to the renter's prepaid credit at $0.15 per compute unit (1 GB of memory for one hour, billed per second, 1 second minimum), separately from the rental. You do not pay to host or run your Actor.
What if one renter uses far more than the rental is worth?+
That does not cost you. Compute is metered and paid by the renter, so heavy use costs them more while your monthly rental stays yours. A run also needs a positive credit balance to start.
Are proxies included?+
No. The monthly rental and compute units do not include proxy traffic. Bytewells datacenter proxy is $1.90 per GB and residential proxy is $5.90 per GB. When an Actor uses Bytewells proxy through the Apify SDK (Actor.createProxyConfiguration(), useApifyProxy, and the usual proxy groups), the renter pays for that usage separately from prepaid credits, the same way they pay for compute. You do not pay for a renter's proxy bill. A renter who wants their own proxy sets it in the Actor's custom proxy option, when the Actor provides one.

Trust, support and risk

Are you a competitor of Apify?+
No. Bytewells is not affiliated with Apify, and we do not offer the same default pricing model. On Bytewells, renters pay a monthly rental for the Actor, plus compute and other usage billed separately from prepaid credit. Optional short passes sit on top. Apify Store Actors default to pay per result. We are not asking you to remove your Apify listing or migrate. Think of Bytewells as another storefront for the same Actor, with a rental-first Store and the same Apify-compatible API so one codebase can live on both.
Who can see my source code?+
You keep ownership of it. Renters run the built image and never receive your source. We may inspect the source when we need to for legal, compliance, or security reasons, for example malware or an Actor that does not match its listing. The Publisher Terms license us to host, build and run it for customers who are entitled to that Actor.
Will you copy my Actor and sell it as your own listing?+
No. The Publisher Terms say we use your source only to operate your listing. We will not publish a first-party Actor substantially derived from your source, or publish your source on another marketplace as our product. Renters never receive your source. We may still inspect it for security and compliance, and we may publish our own Actors that are not derived from your source.
Who supports renters, and how do refunds work?+
The Terms make you responsible for the Actor's listing matching what it does. We run the marketplace, the runtime and billing. If a charge is wrong, the renter contacts us and we correct it. We refund a payment when the charge was our mistake or the law requires it. Used compute and pass charges are otherwise final.
Who is responsible for legal issues around scraping?+
You are. You are responsible for having the right to publish your Actor and for what it does. Renters are responsible for their own runs and targets. Before and while a listing is public, we use automated review of the description, input schema, output shape, and the claims you make in the Store to flag Actors that look abusive or off-policy. If a site owner raises a legitimate concern, we can take a listing down. Our bias is to keep legitimate public-data Actors online when the listing and use case hold up. This is not legal advice; the Terms spell out prohibited uses.

Something missing? Use the contact form, or read the Terms and Publisher Terms.