From a Moyai commit to any customer site
Handover from Ankra to Moyai · 3 November 2026
Moyai merges, Ankra builds, scans and stores a scanned, immutable release. Each customer gets one pull-only robot account and installs that exact release on-prem, or mirrors it into an air-gapped site. No customer ever touches Moyai's source, cloud or CI.
1 · Moyai ships
Every merge becomes a release
Ankra Pipelines tests, builds, scans (Trivy, Semgrep, Checkov) and blocks on findings. What passes lands in Moyai's private registry with an immutable sha- tag, next to its Helm chart.
2 · Customer gets access
One robot per customer
Moyai issues a pull-only login with one command. It reaches Moyai's registry and nothing else, expires on a date, and is revoked in one command.
3 · Customer installs
On-prem or air-gapped
Connected sites install straight from the registry, with Helm or with Ankra. Air-gapped sites mirror one release once, then install from their own registry.
What the customer brings
Moyai's release carries Moyai only. The site provides the platform around it: production dependencies →
- Kubernetes, 3 × 4 vCPU / 8 GiB
- CloudNativePG
- SeaweedFS (S3)
- Valkey, when a release needs it
- Ingress + TLS
- An LLM endpoint
Status
| Link in the chain | State | Owner |
|---|---|---|
| Commit → pipeline → registry (images) | Live every Moyai service | Ankra |
| Helm chart in the registry | Next one pipeline stage to add | Moyai, Ankra helps |
| Robot accounts for customers | Ready issue on request | Moyai |
| Air-gapped bundle (chart + image list per release) | Next | Moyai, Ankra helps |
| On-prem trace-lake settings confirmed | Next | Moyai |