Skip to main content
Cloud Computer

QoderWake Cloud Computer

Buy, provision, and manage a QoderWake cloud computer and connect Wakers to a persistent online environment.

A QoderWake cloud computer is a persistent cloud runtime for Wakers. It provides a browser, terminal, file system, desktop controls, and common development tools so Wakers can continue tasks while your local computer is offline. Once linked, the Waker runs tasks on that cloud computer by default. Closing the QoderWake page, disconnecting remote desktop, or shutting down your local computer does not actively terminate running cloud tasks.
Purchase options, specifications, prices, available regions, and refund rules may vary by account, site, and promotion. Refer to the current purchase page and order terms.

Cloud computers and local computers

Local computerCloud computer
Runtime locationYour current computerA cloud environment provided by QoderWake
Online requirementThe local computer and QoderWake client must stay onlineYour local computer need not stay online
Files and appsLocal files, apps, and network within the authorized scopeFiles, apps, and network in the cloud computer
Environment stateDepends on the local computerWorkspace and runtime state are stored in the cloud
OperationDirectly on the local deviceView or take control through remote desktop
Local files, apps, sign-in state, VPN, and corporate intranet resources are not automatically available in the cloud. Upload required files explicitly and sign in or authorize external services separately on the cloud computer.

Buy a cloud computer

Path: Settings → Environments & Devices → Cloud Computers.
  1. Choose Buy cloud computer.
  2. Review available specifications, pricing, service period, and order terms.
  3. Choose Buy now and complete payment on the transaction page.
  4. Return to the payment confirmation window in QoderWake:
    • If payment is incomplete, choose Not paid yet and return to the order.
    • If payment is complete, choose Payment completed to query the order and provisioning status.
  5. Wait for provisioning. Do not buy another computer for the same need while it is in progress.
If the browser blocks the transaction page, allow new windows for the site and retry. If the page does not change after payment, refresh the cloud-computer list and check the order before paying again.

Understand cloud computer status

StatusMeaningWhat to do
ProvisioningOrder confirmed; environment is being createdWait and refresh the list
RunningReady for connections and tasksOpen it or link a Waker
StoppingRuntime is stoppingWait; do not repeat the action
StoppedEnvironment retained but not runningStart it when needed
StartingRuntime is resumingWait until it is running
ReleasingEnvironment is being reclaimedStop writing files or starting tasks
ReleasedEnvironment reclaimedConnections are unavailable and data cannot be recovered
Failed or unknownOperation or status synchronization failedRefresh and inspect the error; contact support if it persists
Status names may differ by version and site. Follow the current page. Select a cloud computer when creating a Waker or change its runtime in Waker settings.
  1. Open the Waker's runtime settings.
  2. Select the target cloud computer in the running state.
  3. Save.
  4. Start a new read-only task to verify the expected directories, browser, and tools.
  5. Review tasks that depend on local paths, VPN, local apps, or local Connectors, and migrate or reauthorize them.
Multiple Wakers can share one cloud computer, subject to its resources and platform concurrency policy. One Waker can be linked to only one runtime at a time. Existing tasks do not automatically gain files or signed-in sessions from a changed environment. Validate automation, Groups, @Waker, and WakerFlow separately with a small test.

Open and control

Open the cloud computer from:
  • Open cloud computer under Environments & Devices → Cloud Computers.
  • The current runtime view in task details.
Remote desktop shows the Waker's clicks, typing, navigation, and runtime state. Take control of the keyboard and mouse when sign-in, verification codes, permissions, or interface problems need human handling.
  • Use full screen for more space.
  • Reconnect after a network interruption.
  • Closing remote desktop only disconnects the view; it does not shut down the computer or actively stop Wakers and background tasks.
  • Do not operate the same window simultaneously with the Waker. When finished, explicitly tell it where to continue.

Transfer files

Upload to the cloud computer

  1. Open file transfer.
  2. Select local files and confirm the upload destination.
  3. Wait for completion.
  4. Verify names, sizes, and contents on the cloud computer before asking the Waker to use them.

Download to your computer

  1. Select files or task artifacts to retain.
  2. Choose download to your computer.
  3. Open and verify the downloaded content locally.
File transfer does not synchronize entire local directories, browser sign-in state, or app settings. Do not upload passwords, tokens, or unredacted customer data as ordinary files. Keep durable work in a clearly identified workspace and maintain an external backup.

Runtime and persistence

After a device reconnects or a Waker restarts, the following generally remain available:
  • Project files and task artifacts in the workspace.
  • Installed or configured supported tools.
  • Supported browser sign-in state and cookies.
  • Task logs and recoverable background-task state.
  • Project configuration and caches used by the Waker.
Cloud computers support browser operations, terminals and scripts, file management, desktop app control, long-running commands, background processes, and scheduled or triggered tasks. Device repair, rebuilding, or system maintenance may affect temporary files, unsaved content, and some runtime state. Save durable files in the workspace, return them as task artifacts, or back them up to an approved external location.

Manage the cloud computer

  • Rename: give a running computer a recognizable name, such as Content Operations — Isolated Production Environment. Renaming does not change files.
  • Refresh status: after purchase, starting, stopping, renewal, or network errors, refresh to confirm the actual server state.
  • Check associations: before changes, expiry, or release, inspect linked Wakers, automation, Groups, @Waker, and WakerFlow.
  • Control concurrency: when sharing a computer, avoid modifying the same file, browser session, or external object at once.

Renew, expire, and release

Check expiry in the cloud-computer list or order page and follow the renewal instructions. After expiry, linked Wakers cannot continue using the environment and automation may stop. After the retention period shown on the current page, an expired computer enters release. Release permanently deletes its files, app state, and other data; they cannot be recovered. Do not rely only on a default retention period. Before expiry:
  1. Download or back up required files and artifacts.
  2. Stop or migrate dependent automation.
  3. Switch linked Wakers to an available environment and validate them.
  4. Check whether browsers, Connectors, and external accounts need reauthorization.
Request refunds according to the purchase page or order instructions. Eligibility, amount, and processing time depend on the applicable rules and actual usage at the time of the request.

Troubleshooting

SymptomWhat to check
Purchase page will not openNew-window permission → sign-in state → network → purchase eligibility
Still appears unpurchased after paymentOrder status → payment confirmation → refresh list; do not pay twice
Provisioning or starting takes too longRefresh and record errors; contact support if unchanged
Waker cannot find local filesUpload them or use suitable external storage; files do not sync automatically
Remote view disconnectsNetwork → computer status → reconnect; disconnection does not mean the task stopped
Upload or download failsFile size and permissions → network → target directory → free space
Linked Waker cannot workComputer status → runtime selection → project paths → Skill/Connector authorization
Tasks stop after expiryRenew or migrate Wakers and automation to another available environment
Related: Waker Management · Autonomous Work · Settings