TenkaCloud Docs

Runtime capability matrix Preview

A pack declares the (provider, engine) runtimes it requires. The matrix below is a normative reference generated from RUNTIME_CAPABILITIES in @tenkacloud/problem-runtime/capabilities.

Matrix

ProviderEngineModeRecognizedAdapter wiredExecutableLive verifiedMaturityBlocking issuesEvidence
awscloudformationcloudyesyesyesyesStableDefault competitor-account CloudFormation lifecycle is production and live verified.
azurebicepcloudyesyesnonoPreview#2081Adapter, credential wiring, and inline-ARM-template materialization (precompiled JSON or a Bicep compile, fail-closed when neither is available) ship; live acceptance remains open.
dockercomposelocalyesyesyesyesPreviewExecutable and verified through the AWS-free make local lifecycle; never cloud deployed.
gcpinfra-managercloudyesyesnonoPreview#2081Adapter, WIF wiring, and Terraform source materialization to GCS ship; only live acceptance remains open.
sakuraappruncloudyesyesyesnoPreview#2081Adapter and current AppRun API wire contract ship; real-account lifecycle acceptance remains open.

Independent capability facts

  • Recognized — metadata and schema accept the exact provider/engine pair. This does not imply that deployment code exists.
  • Adapter wired — a concrete adapter plus its credential/composition wiring ships in the repository. This still does not prove artifact handling or provider API correctness.
  • Executable — the complete materialization and provider wire path is expected to run in its declared mode (cloud or local).
  • Live verified — a real lifecycle has been demonstrated. Mock and unit tests are required regression evidence, but they never count as live verification.

Azure, GCP, and Sakura are adapter-wired. Their live verification remains false while multicloud acceptance #2081 is open. Azure and GCP also remain non-executable until their artifact/output blockers shown in the table are closed. Sakura's API contract is executable after #2746, but it is not competition-ready until the real-account lifecycle is attached to #2081.

The local docker/compose runtime is independently executable and verified in the make local mode; it is not a cloud runtime. AWS CloudFormation is the default stable, live-verified cloud runtime.

Related: problem metadata reference.