Verda: what to verify before choosing

Verda Cloud provides GPU and CPU instances, virtualized Instant Clusters, and serverless containers for inference/batch jobs; public materials also describe custom bare-metal clusters by request. An instance is customer-managed compute; an Instant Cluster is a virtualized multi-node cluster with host/network operation by Verda and guest VM updates/configuration by the customer; Serverless Containers handle container replicas, scaling and serving operations. Confirm exact service terms and configuration.

Updated

Computraq is preparing for launch. These guides explain readiness and the proposed framework; they do not establish a live service, integration or partnership.

Delivery modes and operating boundary

Verda Cloud provides GPU and CPU instances, virtualized Instant Clusters, and serverless containers for inference/batch jobs; public materials also describe custom bare-metal clusters by request.

An instance is customer-managed compute; an Instant Cluster is a virtualized multi-node cluster with host/network operation by Verda and guest VM updates/configuration by the customer; Serverless Containers handle container replicas, scaling and serving operations. Confirm exact service terms and configuration.

Computraq is prelaunch. Naming this provider here does not mean that Computraq hosts workloads on it, has tested its integration, or has a commercial relationship with it.

Buyer and procurement preparation

Use these questions to prepare a comparable, workload-specific evaluation. Product names describe the provider’s published offering; they do not establish availability for a particular account.

  • Verify the current product and contracting identity: Verda is the successor brand to DataCrunch, while some API/SDK and older console references may retain DataCrunch naming.
  • Choose an instance, Instant Cluster or Serverless Container from workload duration, topology and operations needs; request current capacity, location, security, support and reservation terms.
  • Review the shared-responsibility boundary, instance/volume deletion behavior, logs and inference input/output retention for the selected service.

Developer and operator evidence

Before selecting capacity, create a small acceptance plan that records the model and revision, input shape, runtime, GPU configuration, concurrency, target latency or job completion, and recovery expectations. Provider documentation is evidence of product design, not proof that this workload has been tested.

  • For instances, provision by current Verda CLI/API or Terraform, then verify instance type, image, location, volume and SSH configuration.
  • For Serverless Containers, test replica scaling, scale-to-zero, request queues, async handling and logs; use batch jobs for long inference durations where advised in docs.
  • Pin container and model revisions, keep durable state in managed storage and test restart/teardown behavior.

Sources and verification