Guided setup
1 · Detect runtime
—
2 · Select model
—
3 · Test
—
4 · Certify
—
5 · Pair HomiCore
—
Detect → select → test → certify → pair. Nothing is installed automatically.
Node status & hardware
Runtimes
| Id | Kind | Endpoint | Models | Source | |
|---|---|---|---|---|---|
| Loading… | |||||
Advanced options
Endpoints must be on this machine (loopback) or a private network with the opt-in enabled — never the public internet.
Models & certification
| Model | Runtime | Size | Tier | Guidance | Context | Test | Actions |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Certification runs 26 probes against the model (schema conformance, evidence adherence, prompt-injection resistance, refused actions, latency) and assigns its tier — bound to the model digest, so a replaced model must be re-certified.
Pair device / paired clients
| Name | Role | Last seen | Status | |
|---|---|---|---|---|
| Loading… | ||||
Remote access (relay)
Remote access is outbound-only. No router port forwarding is used or needed.
Safe diagnostics
| Model | Requests |
|---|
| Error category | Count |
|---|
Metadata only: counts, latency, model ids, error categories. Prompts and household context are never recorded.
How to use this node
The short version: run a local runtime (Ollama et al.) → Run guided setup (detect → test → certify) → Pair device for the HomiCore app, Pair HomiCore gateway for the HomiCore cloud → away-from-home access uses the outbound relay, never port forwarding.
Open the full step-by-step guide → (deploy, tokens, runtimes, pairing, HRP linking, troubleshooting)