Documentation
Platform site
Docs/Product guides

Production lifecycle

Kernary Fleet

Signed updates, staged cohorts, health gates, rollback, vulnerability mapping and agent-assisted diagnosis for deployed device families.

Deployment loop

SIGNED RELEASEv1.4.0policy: production-canary1% → 10% → 100%health-gated cohorts
A release expands only while cohort health remains within policy; rollback remains available at each stage.
  • Cryptographically signed artefact and device-family compatibility policy
  • Canary and staged cohorts with measurable health gates
  • A/B, recovery and rollback design validated before production
  • CVE relevance mapped to actual package, kernel and configuration inventory
  • Field failures linked back to Board reproduction and Engineer repair workflows

Define a rollout policy

rollout.yaml
apiVersion: fleet.kernary.dev/v1alpha1
kind: RolloutPolicy
metadata:
  name: production-canary
spec:
  compatibility:
    deviceFamily: orbit-controller
    hardwareRevisions: [rev-b]
  stages:
    - name: lab
      percentage: 0
      requiredEvidence: physical-regression
    - name: canary
      percentage: 1
      observeFor: 24h
    - name: early
      percentage: 10
      observeFor: 48h
    - name: general
      percentage: 100
  health:
    maxBootFailureRate: 0.1%
    maxRollbackRate: 0.5%
  onFailure: pause-and-rollback

Propose a deployment

Terminal · proposed CLI
kernary fleet deployment propose \
  --release release://orbit-controller/1.4.0 \
  --policy rollout.yaml

# Signing and approval occur outside the agent cell.
kernary fleet deployment status \
  deployment://orbit-controller/1.4.0-rc3 \
  --watch

These docs are part of the product design. Interfaces remain proposals until an implementation is published.

View the platform →