Mentary AI: Verifying a Private Inference Deployment on a Fresh Host
说明与用途
验证 Mentary AI 本地部署:网络隔离测试、包清单、健康与负载检查、合规评估及价格验证。
问题
Verify that a purchased Mentary AI package truly runs locally without external API calls and contains all promised components before deployment.
结果
The deployment runs locally without external calls, all promised artifacts are present, performance meets expected latency for single concurrent user, and compliance benefits are confirmed.
工作流
- Run network isolation test using
unshare -nto ensure no outbound traffic during inference. - Inventory package contents with
du -sh /opt/mentary/weights /opt/mentary/runtimeand list deployment scripts and Docker images. - Perform health check with
curl http://127.0.0.1:8080/healthzand load check measuring latency withcurl -w '\n%{time_total}\n'. - Review compliance claims: confirm absence of third‑party processors, request BAA/SOC‑2 if needed during support window.
- Verify pricing and payment options as listed on the product page.
证据
Block all outbound traffic for this process, then run an inference.
If a response comes back, the model is genuinely local. If it hangs or errors on DNS, you have a hidden call out — which is the single thing that would disqualify the product for a privacy buyer.
Before any tuning, inventory it. The page lists: model weights, the optimized inference engine, deployment scripts, a production Docker image with Compose orchestration, documentation, and 30-day priority support.
The page says CPU and GPU-accelerated runtimes are both included. That means two different performance profiles, and you should measure the one you will actually run.
What you do not get is a BAA, a SOC 2 report, or a signed residency guarantee.
- 记录日期: 2026-10-22T09:11:26.278Z