Suggestion to simplify Golem’s Pricing Model.

[cryptobench]

Simplifying Golem’s Pricing Model

Currently, when a user joins the Golem Network, they need to navigate three different pricing components:

1. Start price – A one-time fixed fee for starting a task.
2. CPU/h – Hourly pricing based on CPU time per core.
3. Env/h – Hourly pricing for renting the entire system.

Each of these can be configured independently, in combination with one another, or even all three at once. This complexity makes it difficult for new users to understand pricing and for requestors to estimate the cost of their tasks or how much it would cost to rent a machine for an extended period (e.g., a month).

A major challenge with CPU/h pricing is that CPU usage is highly variable—it depends on workload characteristics, sudden spikes in traffic (e.g., for services), and many other factors. Because of this, there’s no simple way to predict costs accurately, making it difficult for users to confidently commit to the platform. Unlike fixed pricing models, users can’t just use a calculator to estimate their expected costs with certainty.

By simplifying the pricing structure and removing or hiding the start price and CPU/h pricing, leaving only env/h, we can:

• Make the marketplace more transparent and easier to understand.
• Allow both providers and requestors to quickly determine costs without confusion.
• Improve the user experience by reducing the complexity of price configuration.
• Enable accurate cost estimations by adding a simple pricing calculator in the stats page or software, making it easy for users to understand the cost before deploying a task.

[under300]

I support the idea of ​​eliminating the prices for CPU/h and the starting price.
When there are three prices and as different categories, it is really very difficult to make the right choice of price as a provider. For example, I set a price per core per hour, but how many cores are used and what percentage of them - it is not known. For the client who rents my machine, it would also be very difficult to calculate how much money he should give or whether he paid correctly.
The price for the entire rental of the machine per hour, in my opinion, is the right approach to make everything easier for both parties. The client wants to use a given machine for 1 hour and pays the specific amount. Even if the client does not load the machine during that hour for some reason - the provider has not lost.

Really think about simplifying the entire payment and supply scheme, because every provider wants to receive some money, but also to be able to calculate what it would be.

I am currently noticing that my provider, which is set up with only an hourly rate for the entire machine, is not taking any jobs, and the jobs are being taken from providers with extremely low CPU time rates. If I want jobs, I have to set a CPU time rate lower than $0.001 per hour, which is a waste of time and energy. It is better not to participate in the project.

Things should be simple and easy for both parties, not complicated.