Run a node. Watch every job it runs.

A visible window, one job at a time.

The master-node performs typed form-fill jobs in a visible Chromium window on your machine. It is not a remote-control, proxy, or browser-access product — buyer apps submit declared, typed tasks only and never receive access to your browser or your machine. No keystroke capture, no clipboard reads, no screen scraping outside the assigned tab, no background activity. The master-node is the browser; it does not touch the rest of your machine.

You control which buyer apps can dispatch to you. The app ships with a buyer-apps consent screen — until you explicitly approve a buyer app, no jobs from that buyer reach your node. There is no "approve everything" option, and there will not be one. Withdrawing approval is a single click, and dispatch stops within seconds.

At launch, the only approved buyer app is apply.fun, dispatching ATS form-fill jobs. A typical job is sixty to three hundred seconds in the visible window, twenty to sixty fields filled with the applicant's profile, and one submission at the end. Each job runs on behalf of an applicant who consented to having the application submitted for them. Future buyer apps require their own explicit per-operator approval through the same consent screen.

Honest math, stated up front.

Operator share is forty percent of actual credits charged on each completed job. Credits are denominated at half a US cent; longer, more complex jobs pay proportionally more. Earnings are variable, typically small, and not an investment. There is no token, wallet, or stored value — operators are paid in fiat for verified node-resource contribution.

Failures are stated plainly, because only completed jobs pay. A certified failure — the form was unreachable, the ATS blocked the attempt — charges the buyer the start fee but pays your node nothing; operator share is earned on successful submissions only. An uncertified failure — your node crashed mid-job — also pays nothing, refunds the buyer in full, and degrades your node's health score; persistently unhealthy nodes drop out of dispatch.

A desktop you already have.

• A desktop machine. macOS 11+ (Apple Silicon or Intel) or Windows 10+ x64. Linux is not shipped in v1. 4 GB of RAM available to the app and 2 GB of free disk for the browser workspace.
• A residential internet connection. At least 5 Mbit/s steady upstream, and a network that allows long-lived connections — no enterprise proxies or symmetric NAT between you and the dispatcher.
• The master-node app. The operator desktop client. During the beta it is delivered to enrolled operators by the ops team; in-console downloads arrive with the public operator launch.

Enroll in the console today.

Web enrollment is open in the console now. No waitlist mechanics, no invite codes — the sequence below is the whole process.

1. Enroll at console.gofundnode.com. Create an operator account and accept the operator agreement. On acceptance the console issues your node pairing key.
2. Install the master-node app. Install the client the ops team sends you, launch it, and enter your pairing key. The handshake completes automatically — there is no copy-pasting of secrets beyond the key itself.
3. Pass the canary. New nodes are admitted to the live dispatch pool only after a small suite of synthetic form-fills verifies your install. It runs automatically on first connect and typically completes in five to fifteen minutes.
4. Approve apply.fun. Accept the buyer app in the consent screen. Your node flips to available and becomes eligible for real submissions.

During the beta, rewards accrue to your operator ledger as jobs complete — you can see every accrual in the console. Payouts open after the beta through a regulated fiat payout provider (Stripe Connect or equivalent); nothing you accrue during the beta is lost, and nothing about your payout depends on any buyer's approval.

What holds whether or not you're watching.

• Consent is a scheduling filter, not a preference. A buyer app you have not approved cannot be assigned to your node — the dispatcher filters on your consent record before a job is ever scheduled, and your consent decision is recorded on your node and confirmed back to the service.
• No operator profile bleed. Buyers never see who you are. Operator identity, payout state, and node topology never appear in any tenant-facing surface — the only operator handle a buyer ever receives is an anonymized reference, and the boundary is enforced by architecture gates in CI. See the security overview.
• Fiat only. You are paid in fiat through an embedded payout provider for verified node-resource contribution. No token, no wallet, no self-custody, no stored value — as published on the trust page.
• Nothing persists after a job. Applicant data is rendered into the form inside the visible window — visibility is the point — and after the job completes the app clears form state and closes the tab. No third-party telemetry, no analytics SDKs; the app talks only to gofundnode and the site the job targets.
• The agreement is public. The operator agreement you accept at enrollment is published, alongside the rest of /legal/.

Enrollment is open.

Enroll in the console, pair your node, and approve your first buyer app. If you want a human to answer something first, email us — a founder reads that inbox.