Beyond gaming
Gamers are an ideal first population because they already own, understand and upgrade high-performance GPUs. Rutli gets much more interesting when other kinds of machines join for completely different reasons.
Different owners. Different idle hours. Different workloads. One network underneath.
A gamer and an office can be almost perfect opposites. A gamer may be busy evenings, nights and weekends. An office is busy in weekday business hours. A home AI machine may be always on, usually lightly loaded, occasionally urgent. A university or professional cluster follows scheduled compute cycles. These patterns overlap in useful ways.
Different idle curves. One more available network.
This is not marketing segmentation. It is network design. No promise of 100% utilisation: the message is diversity.
A business buys infrastructure because it needs that infrastructure during operations. But many business systems do not run at full capacity 24 hours a day, seven days a week. During business hours the machine serves the business. Nights, the office may be quiet. Weekends, quiet. Holidays, the machine still exists. Rutli does not need every off-hour to be monetisable. The structural point is simpler: business infrastructure can have long, predictable windows of spare capacity.
Why a business joins: not because the CFO wakes up wanting to become a GPU provider, but because useful software gives the company a reason to own the machine. Private accounting AI, financial intelligence, internal assistants, document analysis, workflow automation, local models, specialised vertical applications. The local application justifies the node. The network creates a second use for the spare capacity.
Work for the business during the day.
Contribute spare compute at night.
Reach into the network when the business needs more.
A business node can become supply and demand.
It contributes when quiet. It consumes more network power when its own workload spikes. It brings predictable off-hours, stable power, stable networking, professional hardware, recurring local use, recurring business AI demand, and a real willingness to pay for burst capacity. A node that stays online because the owner actually uses it is a different kind of network asset.
Rutli starts with gamers because they already own the hardware. The network expands through other populations whose machines have different reasons to exist and different times when capacity becomes available.
They already own the GPUs.
Why they join: better utility from expensive hardware, local AI, technical curiosity, contribution economics, control. Natural spare windows: daytime work or school hours, overnight, the gaps between demanding sessions.
What they bring: high-performance consumer GPUs, upgrade behaviour, technically capable early adopters, major distribution opportunities. Their message: your GPU should work for you.
PLANNED
Read the doorThe workday ends. The hardware stays.
A business buys infrastructure for working hours and does not run it at full capacity nights, weekends and holidays. It joins for useful local software: private accounting AI, financial intelligence, document analysis, internal assistants. The network is a second use for capacity that would otherwise sit unused.
Work for the business by day. Contribute spare compute at night. Reach into the network when the business needs more. An office node is supply and demand, with stable power, stable networking and a reason to stay online.
LIVE
Your home uses the machine first. Rutli gets what the home does not need.
Home AI systems can be always on, privacy-sensitive, intermittently compute-heavy, lightly used for long periods, and immediately demanding when something important happens. A home-security event beats an external network job every time. That is what local priority means in the real world.
What home nodes bring: persistent edge presence, different idle patterns, a strong local-first philosophy, and hardware that stays online because the home needs it.
LIVE
Your private stack can become part of something larger without ceasing to be yours.
These users already understand local models, private services, APIs, Linux, open systems and infrastructure ownership. They are not a niche afterthought. They can become the cultural and technical nucleus of the early network.
What they bring: testing, edge cases, heterogeneous hardware, early developer energy, infrastructure literacy.
LIVE
Most businesses will never join a GPU marketplace. Good.
They may join because software solves a real problem: a local compliance application, a private industry assistant, a domain-specific workflow. That application can bring a machine into the ecosystem. Later that machine may contribute capacity, or consume it, or both.
Applications recruit nodes from markets that would never care about "decentralised compute". That is strategically powerful.
LIVE
Participant-owned does not mean consumer-only.
A participant can be one person with one GPU, an office with five machines, a company with hundreds, a university lab, a regional provider, an institutional cluster.
The principle does not change: no participant needs to own the whole network to matter inside it.
PLANNED
Read the doorSome participants bring demand, not hardware.
Developers and companies may never run a node. They may simply need capacity. That matters because a network made only of people who want to be paid is not an economy.
Rutli needs both supply and demand. The application ecosystem can help create both.
PLANNED
Read the doorA gamer buys a powerful GPU and joins. Spare capacity enters the network. An office workload consumes it; the office machine contributes overnight; home AI contributes opportunistically; a developer buys inference; node owners receive the compute value; capable hardware becomes more useful; more users and businesses justify nodes; more applications create more supply and demand.
Different reasons to join. One network underneath.
Some nodes bring compute. Some applications need it. Rutli is building both sides. PLANNED
