Developer waitlist

Bytewells is in private beta. Public launch is planned for Monday 2 November 2026. Developers on the waitlist are invited first and get hands-on help importing their Actors.

Not yet. We are building supply and demand at the same time: filling the Store with the first developers' Actors and our own, while also collecting a customer waitlist. We do not have paying renter numbers to share yet, and we would rather say so than invent them. Developers on the waitlist are first in line to list when we open the Store.

The docs cover importing, publishing, billing, passes and the API. There are no live third-party rentals to show yet.

Sign up with bw signup, then run bw import apify you/your-actor. Import copies the source, README, input schema, run defaults and rental price, builds the Actor on our builders and creates a draft listing. You then review the price, trial and passes, and publish. You can also use Continue with Apify in the console and pick Actors from a list.

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.

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.

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.

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.

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.

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.

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.

Payouts currently go to developers in the EU, Liechtenstein, Norway, Switzerland and the UK. Developers elsewhere can list free Actors for now, and get traction, but cannot create paid listings yet. More countries are planned to be supported by 1 Jan 2027. Your payout country is fixed once your Stripe account exists.

You set it. You also choose a free trial of 0 to 30 days (the default is 3) and optional Flash (1 hour), Burst (24 hours) and Sprint (7 days) passes. Import carries over your Apify rental price, and --price-discount can undercut it. For reference, the median price across 1,351 listed Apify rental Actors in September 2026 was $19 a month (25th percentile $9.99, 75th $28.50). Trials are whole days, so an Apify trial of a few hours becomes one day.

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.

No. Every developer gets the same terms, with no time-limited founding discount: 10%, and 0% on customers you refer. We do not promise featured placement at launch.

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.

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, 60 seconds minimum), separately from the rental. You do not pay to host or run your Actor.

That does not cost you. Compute is metered and paid by the renter, so heavy use costs them more while your flat rental stays yours. A run also needs a positive credit balance to start.

No. The monthly rental and compute units do not include proxy traffic. 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. Renters who prefer their own proxy URL or password can still configure that instead.

No. Bytewells is not affiliated with Apify, and we do not offer the same pricing model. We are built for a different segment: flat monthly rentals and short passes, not usage-based runs as the default. 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.

You keep ownership of it. Your private key stays in the bw CLI, and source is encrypted before upload, so we store ciphertext rather than a readable repo. Renters run your built image only and never receive your source. The Terms license us to build, store and run it for customers who are entitled to that Actor.

You support your renters, and the Terms make you responsible for the Actor's listing matching what it does. Bytewells runs 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.

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.