Injector Cloud · Install-ready injector coding VMs · 10,165 ready injector profiles across live machine catalogs

Create VMConnect your wallet, choose a machine, and create a virtual machine.Bench workspaceOpen the coding bench tied to your installed virtual machine.DocumentationComprehensive guide to platform purpose, users, and architecture rationale.Live coverage13 ready VM machines. 10,165 ready profiles.Profile directoryOpen brand and profile-level coding route directory.FUEL accessConfigure access and track activity.Installed VMsSee how machine lifecycle and controls work.
Wallet Start Coding

Documentation

Documentation

Last reviewed:

Overview

Console is the control plane for Injector Cloud VM execution. Each job should be tied to an explicit machine install so runtime scope, payment traceability, and operational ownership remain unambiguous.

Session Lifecycle

State Operational Meaning
CreatedSession is provisioned and ready for bench launch.
ActiveOperator workload is executing in an isolated runtime.
ExpiredSession reached TTL and no further operations are allowed.
ClosedOperator or system closed the session with final records preserved.

Controls

  • Wallet-authenticated session creation and refresh.
  • Per-session scope isolation to avoid cross-run data bleed.
  • Trace linkage between machine lifecycle and payment events.
  • Clear session state visibility for operators and reviewers.

Operator Notes

For diagnostics and service audits, record the session context used for each coding action. This improves reproducibility when troubleshooting or validating workshop outcomes.