Nishi FamilyCompare › Deployment and Live Hosting

Nishi vs the Field

Deployment and Live Hosting — mechanically measured, liar-killed, sovereign.

The sovereign mgmt control plane (upload -> build-on-target -> health-gated promote -> auto-rollback, all simple API calls over own TLS) vs Vercel and Fly.io and Render and Kubernetes with Argo

How this is scored. Every Nishi cell is measured: the generator reads the real organ source on disk and requires the implementing symbol to exist (no self-grading). Competitor cells record documented capability presence. Best=leads this axis, Yes=present, Part=partial, No=absent. This is capability presence, not depth or scale: the majors lead on index size and neural ranking. Nishi's genuine exceeds are the sovereignty / neutrality / determinism axes.
CapabilityNishiVercelFly.ioRenderKubernetes+ArgoNotes
Health-gated promote with auto-rollback watchdogYesYesYesYesBestArgo Rollouts is the reference; Fly and Render health-check releases; Nishi /api/deploy stages .new then promotes then an async watchdog verifies health and ROLLS BACK by construction -- never-brick is the default not an option
Instant manual rollbackYesBestYesYesYesVercel instant alias flip to any prior immutable deployment is Best; Nishi POST /api/rollback restores the .prev binary
Build on the target from sourceYesBestYesYesPartVercel build pipeline is Best-in-class; K8s delegates builds to CI; Nishi POST /api/build compiles with the sovereign toolchain ON the NAS -- no external CI
One-command source to liveYesBestYesYesPartvercel deploy set the DX bar; Nishi nx_ship packs the tree then uploads over sovereign TLS then builds on target in ONE command
Staged content publish (sha-pinned, atomic)YesYesYesYesYesEveryone stages then swaps; Nishi /api/promote_content and /api/compare/publish re-hash the stage and install atomically with .prev backing
Service supervision with crash-loop backoffYesYesYesYesBestK8s liveness probes are Best; Nishi hostctl supervise runs live (PID + SERVING probe, HUNG-aware, backoff) and respawns from the promoted binary
Live fleet inventory APIYesYesYesYesBestkubectl get is the reference; Nishi GET /api/services serves the multi-service inventory
Deploy and ops event streamYesYesYesYesBestK8s watch API Best; Nishi GET /api/events serves SSE to EventSource clients
Ops dashboard UIYesBestYesYesPartVercel dashboard is Best; Nishi Sovereign Fleet at /health is LIVE behind the operator login with per-service cards and allowlisted actions
Fail-closed deploy-target registryYesYesYesYesBestK8s RBAC-scoped resources are the reference; Nishi allowlists every uploadable and deployable target BY NAME -- unknown targets are refused
Machine-readable control-plane specYesYesYesYesBestK8s OpenAPI is the reference; Nishi GET /api/openapi.json describes the whole plane for auto-driving agents
EXCEED control-plane auth is OPAQUE PAKEBestNoNoNoNoIncumbents authenticate deploys with bearer tokens and OIDC; the Nishi plane authenticates with OPAQUE-3DH -- the password never crosses the wire and the server stores no password-equivalent; sessions are Ed25519-minted and TTL-bound
EXCEED sovereign end-to-end hostingBestNoNoNoNoThe live site terminates its own TLS 1.3 and routes SNI without a third-party terminator -- no nginx no cloud LB no CDN vendor; every byte from ClientHello to response is auditable sovereign source on owned hardware
EXCEED the control plane deploys ITSELFBestNoNoNoNoProven live: the mgmt API was upgraded THROUGH its own upload-deploy-watchdog chain (DEPLOYED-GREEN) -- self-hosting deployment with never-brick protection; platform vendors upgrade their planes outside your view
Canary and progressive traffic shiftingNoYesYesYesBestArgo Rollouts weighted steps are the reference; Nishi promotes whole-service -- percentage shifting is a named gap
Preview environments per changeNoBestYesYesPartVercel preview-per-PR defined the category; Nishi has no ephemeral preview instances yet
Blue-green dual-slot instant switchNoYesYesYesYesNishi has .prev restore but not two warm slots with instant cutover
GitOps declared-state reconcilerNoPartPartPartBestArgo/Flux reconcile the cluster to a declared repo state; the Nishi registry is imperative API calls today
Multi-node and multi-region placementNoBestBestYesBestFly regions and Vercel edge network lead; Nishi runs one sovereign host plus workstation
Autoscale including scale-to-zeroNoBestBestYesYesServerless platforms scale to zero; Nishi services are always-on supervised processes
Secrets manager with rotationNoYesYesYesBestK8s secrets plus external-secrets is the reference; Nishi has key files and a vault doctrine but no rotation-managed deploy secrets plane
Domain purchase API with spend wall + dry-run-firstYesYesNoNoNoLIVE-PROVEN to the server pre-flight (Porkbun dryRun, 0 charge): refusal ladder = spec-verified endpoint, creds, literal confirm-spend, quote<=cap; Vercel sells domains via API too -- ours adds the client-side spend wall (their docs not banked, so no exceed claimed)
DNS records API on the live registrar (A/TXT)YesYesYesPartPartLive-KAT proven against andelinwest.com over sovereign TLS; platforms manage DNS on their own edges; K8s external-dns is Part
TLS certificate acquisition (bundle retrieve + ACME DNS-01)YesYesYesYesPartLIVE: 10509-byte LE bundle retrieved (0600, key never printed) for andelinwest.com; platforms auto-provision on their edge -- ours lands certs on the sovereign edge
Purchase-to-live orchestration (ordered, once-only spend)YesYesNoNoNoGated 8/8: dryrun-then-confirm spend, double-purchase impossible by construction, operator-gated edge step; Vercel buy+auto-cert is the incumbent flow without explicit spend caps
coverage 720/1000EXCEEDS 3PRESENT 15ABSENT 7
Honest verdict. Nishi has broad, sovereign search-engine presence — a real organ behind every core ranking and crawl axis, built bits-up in one language. It is not yet a scale or neural-ranking rival: the majors lead on index size (billions to trillions vs a Common-Crawl-seeded slice) and trained rerankers. Nishi's genuine exceeds are structural — owning the whole stack, neutrality by construction, and a zero-JS integer-deterministic result page. The climb is a bigger index and a trained reranker.

Generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/deploy.matrix — every Nishi cell verified against real organ source on disk. Zero JS, zero trackers.