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

Documentation

Documentation

Last reviewed:

Overview

Injector Cloud documentation is organized as a route-based technical manual. Each route targets one topic and includes clear boundaries, operational context, and implementation-level guidance.

Platform Scope

  • Operator-facing diesel injector coding workflows for common rail systems.
  • Secure VM execution for deterministic algorithm runs and reduced environment drift.
  • Blockchain settlement and event traceability for cross-team trust and auditability.
  • Coverage-first rollout strategy with transparent ready machine families and install paths.

Documentation Map

Route Coverage
/docs/getting-startedOnboarding, prerequisites, operator first-run flow.
/docs/console-and-vm-sessionsWallet auth, VM lifecycle, machine controls, and trace signals.
/docs/troubleshooting-and-runbooksFailure signatures, triage order, and production-safe recovery runbooks.
/docs/diesel-injector-codingCoding standards, correction families, service triggers.
/docs/coverage-and-profilesReady machine families, profile directory, and install flow logic.
/coding-profilesOperator-facing directory for brand, family, part, and OEM profile lookup.
/docs/blockchain-vm-architectureInfrastructure model, trust boundaries, deterministic execution.
/docs/access-and-usage-feesAccess model, payment tokens, usage economics.
/docs/security-and-complianceIdentity, isolation, auditing, and operational controls.
/docs/token-and-accessFUEL role, access-window scope, and utility boundaries.
/termsPlatform usage terms and workflow responsibility boundaries.
/privacyData collection, usage, and retention overview.
/docs/operations-and-rolloutDelivery phases, governance, and team enablement.
/docs/release-and-change-managementRelease channels, change windows, rollback posture, and communications.
/docs/faqCommon technical and operational questions.

Recommended Reading Paths

All App Aspects Covered

These docs cover the complete platform surface: business context, operator workflow, technical architecture, security boundaries, payment model, token model, runbook operations, and release governance. New docs routes can be added under `/docs/*`, while profile lookup stays centralized under `/coding-profiles`.