Skip to main content

Compute Network and Devices

Worka can run tasks in more than one place. That is useful, but only if you can tell what is running where and why.

Some work belongs on your own machine because it depends on your local tools or subscriptions. Some work can run on broader infrastructure. Some devices can also contribute spare capacity back to the Worka compute network.

Use your own devices​

You can add your own devices so Worka has trusted places to run work.

That is useful when a task depends on:

  • local CLI tools
  • a model subscription already tied to that machine
  • local files or accounts
  • a private environment you control

Examples:

  • a desktop that can run coding work through your existing CLI subscriptions
  • a private server that should handle internal jobs
  • a laptop that already has the tools needed for one specialist workflow

What Worka may use on your device​

Depending on what you allow, Worka may use:

  • local tools
  • local subscriptions
  • device-specific capabilities such as browser control or desktop computer control

Some capabilities are general-purpose enough to help with normal task execution. Others are more sensitive and remain local to your own work even if the device also contributes broader compute.

Join the compute network​

You can also let your device contribute spare capacity to the Worka compute network.

That means idle time on your machine can help power work for others, and you can earn from that participation.

You should expect the product to make this explicit. Contributing compute should be an enrollment decision, not a hidden side effect of adding a device.

What you should be able to control​

You should be able to decide:

  • which devices are available to the workspace
  • which classes of tasks may run on them
  • whether Worka may choose placement automatically
  • whether the device is for your own work only or can also contribute spare capacity
  • which local subscriptions and tools are in scope

That control matters because convenience and trust are different things. A personal setup may prefer convenience. A company setup may care much more about where work runs and what is allowed to execute there.

What to review before you add a device​

Before you add a device, check:

  • what tools are installed there
  • what accounts or subscriptions are already present
  • whether it should handle sensitive work
  • whether it should be available continuously or only when you choose

If the device has powerful local access, treat that as part of the workspace's trust boundary.

What to review before you join the network​

Before you contribute a device to the compute network, check:

  • what kind of work the network may place on it
  • how much of the device should stay reserved for your own use
  • how earnings or credits are handled
  • which capabilities stay local-only even when the device is enrolled

You should never have to guess whether a sensitive local capability is being pooled with network work.

A good device setup​

A sensible setup might be:

  • your desktop handles your own coding and browser tasks
  • a private build machine handles release checks
  • the broader compute network handles lower-risk background work

That kind of split gives Worka flexibility without turning placement into a black box.