Overview Installation Workflows Collaboration Job Policies Credits & Monetization

Job Policies

When you submit a generation job, you choose a policy that controls which GPU processes it. Each policy has different cost, speed, and privacy trade-offs.

Overview

Policy	Processed by	Cost	Client required?
`mine`	Your GPU only	Free	Yes — must be online
`all`	Any public provider	Credits	No
`users`	Your trusted users	Free if online	No
`project`	Project team members	Free if online	No
`monetize`	Monetize providers	Real money	No

Policy Details

Private — Mine

mine

Your job runs exclusively on your own GPU. No credits are spent. If your desktop client is not running when you submit, the job is rejected immediately with a clear error — a mine job can never be queued for another provider. Best for privacy, zero cost, and complete control.

Cost

Free

Requires

Desktop client running

Community — All Providers

all

Your job enters the public community queue and is picked up by any online provider. OpenFork uses smart cache-based routing to assign the job to whoever already has your model image downloaded — no wait for an extra download on their end. Jobs queue until a matching provider comes online.

Cost

Credits or free daily slot

Requires

Credit balance or active provider

Trusted Users

users

Only providers whose owners you've added to your trusted users list will process the job. If none are online, the job falls back to standard community credit rules and queues for any available provider. Good for small groups who share compute resources.

Cost

Free if trusted provider online

Requires

At least one trusted provider active

Trusted Project

project

Scoped to a specific project's team. Only providers run by project collaborators or owners will process these jobs. If no team member is online, the job queues until one comes online — same fallback behaviour as Trusted Users. Ideal for production pipelines where a team runs dedicated machines.

Cost

Free if team provider online

Requires

Project collaborator running a client

Monetize — Paid Priority

monetize

Your job goes to monetize providers only — GPU owners who have connected a bank account and opted into paid jobs. Providers are financially incentivized to maintain uptime, so these jobs typically process faster. If community capacity is insufficient, cloud instances on Vast.ai scale up automatically.

Cost

Real money (prepaid balance)

Requires

Prepaid balance at openfork.video/credits

Scheduling Modes (Desktop Client)

The desktop client lets you control when it runs and whose jobs it accepts.

Manual

You start and stop the client yourself.

Always On

Runs whenever the desktop app is open.

Scheduled

Custom time windows — e.g. 22:00–08:00 to use idle overnight hours.

Desktop routing modes

Private

Processes your own jobs, with an optional Trusted group for specific users or projects.

Trusted

Private sub-setting for processing jobs from selected users or selected projects.

Public

Processes any community job (all policy). Earns credits.

Monetize

Processes paid jobs only. Earns real money. Requires Stripe Express.

Security & Abuse Prevention

All public-network job submissions (all policy) pass through a 10-layer protection system: rate limiting, burst detection, duplicate prevention, circuit breakers, and complexity caps.

Trusted policies (mine, project, users) bypass all security checks because the trust relationship is server-verified— it's not enough to claim a policy in the request; the database confirms an actual active trusted provider exists before granting any bypass.

For mine policy: if your desktop client is offline at submission time, the request fails immediately with a MINE_POLICY_NO_PROVIDER error. A mine job is never queued for someone else's GPU.