Skip to main content
Planned launcher, October 9, 2026. Tensor9 is implementing the Docker launcher for local development mode. The existing foreground tensor9 adapt svc run command remains the current quickstart path; it does not yet provide this container workflow.
Planned local development mode: one serving container receives origin-cloud API calls and connects to your target-cloud services.Planned local development mode: one serving container receives origin-cloud API calls and connects to your target-cloud services.
The planned local development mode launcher starts one serving image by digest in Docker. The adapter accepts the origin-cloud API and calls your actual target-cloud services. The image is distributed through Tensor9’s private registries, and CLI authentication and a valid license are required.

​
When to use it

Use local development mode to develop and evaluate a directed service mapping against your own cloud resources. It differs from the local emulator, which selects in-memory backends. Use full mode for an installed cloud fabric, whether the environment is for development or production.

​
What you operate

  • Docker on your local machine and the adapter configuration.
  • The local endpoint used by your application.
  • Access to your target-cloud resources.
  • Target-cloud data, billing, backups and recovery.
The planned launcher passes short-lived cloud credentials as files in temporary container storage. It runs the container without root privileges, with a read-only root filesystem and dropped capabilities, without host networking or home-directory credential mounts.

​
Current local workflow

The current quickstarts retain the existing tensor9 adapt svc run command and its verified service-selection options. Follow the quickstart for your mapping, keep its endpoint local, and check the target effect independently. Container acquisition and Docker launch instructions will be added when the launcher is delivered.