No. The cloud logos illustrate the product model. The service reference under each cloud in the sidebar lists declared mappings. Availability and operation coverage must be checked for the specific direction you need.
API-compatible adapters are designed for the origin SDK. You still need to configure the endpoint and appropriate authentication, and verify the operations your application uses. Some capabilities have different behavior or are unavailable on a backend.
The selected backend stores the data for a mapping, such as objects in Cloud Storage. Adapters can also need operational state. Review the service mapping and installation design to identify every store that requires backup, access control and lifecycle management.
Is Cloud Adapter the same product as Tensor9 BYOC?
They share adaptation technology but have different workflows. Cloud Adapter focuses on using origin service APIs with selected backends. Tensor9 BYOC focuses on delivering your software into another organization’s infrastructure.
Do not assume so. A backend change can require a data and identity migration. The upgrade workflow rejects changes without a supported migration. See operations.
It helps test the behavior it implements. It does not establish your production IAM configuration, networking, quotas, latency or failure recovery. Use local testing together with a bounded test against the real target service.
Yes. Use your existing coding agent with the Tensor9 CLI; no separate agent-specific service is required. Read the agent debugging guide for a safe investigation prompt and explain workflow.
It runs in the deployment scope you choose. The target cloud supplies the networking, process supervision and backend primitives described by that deployment. Cloud Adapter does not require the Tensor9 BYOC control plane.
The selected backend stores the data for the mapping. Runtime backend credentials belong to the adapter configuration; origin credentials authenticate application requests. Keep both scoped, rotate them independently and do not place secret values in configuration reviews or agent transcripts.
Only when the selected mapping and configuration workflow support adopting them. A resource identifier is not proof that data, encryption keys, policies or lifecycle behavior are compatible. Verify ownership and migration requirements before pointing an adapter at populated storage.
Scale the adapter processes, coordination store, network path and backend together. A healthy process does not prove that the backend or shared state can handle the workload. Establish a baseline and test failure recovery before increasing replicas.
