Your computer probably sits idle for hours a day. Arclode puts that time to work: it takes on AI jobs for other people in the background, and pays you for what it does.

The simple version

• Install a small app. It runs quietly in the background.
• It only does what you allow. You pick the kind of work, and you can stop it whenever you want.
• You’re paid for real work. The more jobs your computer finishes, the more you earn.

What you need

A normal modern computer, like a gaming PC or a Mac you already own. Nothing special to buy.

How to start

The earning side is still rolling out. Make a free account now, and you’ll be set to install the app and pick what it can run as soon as it opens.

Most computers do nothing for most of the day. Arclode’s provider side puts that idle time to use: install a small app, and your machine picks up AI jobs the network sends it while you’re away, then pays you for the work it finishes.

How it works

• You stay in control. The app only accepts the kinds of work you allow, and you can pause or stop it whenever you want. It steps aside the moment you need your machine back.
• You’re paid for real work. Earnings track the jobs your computer actually completes, counted per job, not promised up front.
• Same account, one balance. What you earn lands in the same Arclode balance you’d spend as a builder. Put it toward your own generations, or keep it separate.

What you need

A gaming PC or a Mac you already own. Nothing to buy, nothing to rack. If it can run today’s games or creative apps, it can take on work.

Getting started

The provider side is still rolling out. Create an account now and you’ll be ready to install the app, set what you’re willing to run, and let it work in the background. You decide how much it does and when.

This post is scheduled ahead of its publish date to show off Arclode’s future-dated posting: it appears in the feed on its date, once the site rebuilds.

The provider side is the supply half of the network. Your machine advertises what it can do, the scheduler routes matching jobs to it, and you earn for the ones it finishes. It’s the same work a developer submits through the builder API, seen from the other end.

Why it’s built this way

• A local client, not a rented rack. The whole premise is reusing hardware that already exists instead of standing up more data centers, so the unit of supply is a consumer machine running a small client, not a server you provision. The client registers the machine, advertises what it can do, takes work while the machine is idle, and yields when you want it back.
• Consent-scoped, because it’s your machine. You decide which kinds of jobs the client will accept. Nothing runs outside that scope, and you can pause or stop at any time. Running someone else’s work on a personal computer only works if the owner sets the boundaries, so that’s the default, not an afterthought.
• Paid per completed job, not per hour online. Earnings attach to work actually finished, not to uptime. It’s harder to game, it lines cost up with value on the builder side, and a fast machine that clears more jobs earns more than one that just sits connected.

What you don’t manage

You don’t hand-place models or babysit infrastructure. The client fetches work, runs it, and returns results; the network handles routing, metering, and payout. Your only real decisions are how much idle capacity to offer and when.

Where it stands

Payout and metering are still coming online, so treat this as the model rather than a live earnings program today. Create an account and you’ll be ready to run the provider client as it rolls out.

This post is scheduled ahead of its publish date to show off Arclode’s future-dated posting: it stays out of the feed until a build runs on or after its date.