UniPhi Complete - Software + All Blueprints

UniPhi DC — Complete (Software + All Blueprints)

The full UniPhi Data Center catalog — software, hardware blueprints, integration blueprints, every deliverable required to stand up a patent-pending personal-hyperscaler rack at any scale a buyer is willing to assemble. The Complete bundle is engineered for the buyer who wants the entire system, not a tier of it: every line of the UniPhi DC software (with source); every hardware reference schematic and layout-ready specification for the node carrier, the rack hub, and the retrofit dongle family; the complete patent-pending fabric protocol, control-plane, and rack-of-racks architecture documented as a buildable specification; and the deliverable evidence — measured benchmark numbers, one hundred thirty automated tests, audit-grade event-log records — that supports every claim made on the listing.

What changed since the previous version of this listing

The UniPhi DC software has shipped a substantial enterprise feature set since the original Complete listing was published. The body below is the refreshed description; the price, the SKU identifier, and the catalog placement are unchanged. Buyers of prior versions of this Complete bundle receive the new features at no additional cost — email the inventor for the updated deliverables packet.

The full feature surface, as of the current shipment

Every item on the list below is implemented in the binary that ships with this SKU, exercised by automated tests in the repository (one hundred thirty tests passing as of the current shipment), and documented at the source level for the buyer's own engineering team to extend.

• Real distributed fabric. A TCP transport with HMAC shared-secret authentication and an optional mutual-TLS path (per-peer X.509 certs signed by a small in-cluster certificate authority shipped with the binary). mDNS auto-discovery so nodes find the hub without typed IP addresses. An exponential-backoff dial loop so a node that cannot reach the hub now will reach it the moment the network heals. An adapter watcher that re-publishes the hub's mDNS record whenever the host's IP changes after a DHCP renewal or a Wi-Fi roam. Fourteen automated fabric tests.
• Real cross-node storage replication. Content-addressed sha256 chunks pushed over per-tunnel TCP connections at N=3 replication factor by default, configurable per file. Automatic re-replication on node loss. Reassembly from any surviving replica. Four automated storage tests.
• Hub crash-resistance. Every state change is appended to a sha256-hash-chained, fsync-on-write JSON-Lines event log. On startup the hub replays the log and the rack continues in the exact state it occupied immediately before the previous shutdown or crash. Snapshot-and-compaction keeps the log bounded. Five automated persistence tests, including a crash-recovery proof that abruptly kills the hub mid-deploy and verifies that all node records, app records, and the next-app counter come back identical.
• Audit-grade traceability. The event log is tamper-evident — its verify method walks the hash chain and recomputes each line's hash from its content, catching both link tampering and in-place edits. The log is plain JSON-Lines: tail -F state.log, ship to any SIEM, ingest into a security-information pipeline.
• Real observability. Prometheus /metrics endpoint with counters (deploys, reschedules, node losses, events recorded), gauges (nodes by state, apps by state, per-node CPU and RAM, fabric peer count, event-log size), and histograms (deploy latency, reschedule latency). Standard text exposition format; no third-party agent required. Structured JSON logs with trace identifiers ingestible by Loki, Splunk, DataDog, Elastic, or any log pipeline. Eleven automated observability tests.
• Real rack federation. The SuperHub primitive composes N rack hubs into one logical control plane. Rack-loss recovery moves orphaned apps from a dead rack to a surviving rack. Two automated rack tests plus a runnable multi-rack demonstration script that brings up two racks of three nodes each, deploys five applications to the rack with more aggregate free memory, abruptly shuts that rack down, and proves that the five applications materialize on the surviving rack.
• Real resource enforcement. POSIX hosts get setrlimit(RLIMIT_AS) enforced via a preexec hook in the application runtime; every host gets a psutil-based watchdog that polls the application's resident-set size every two hundred fifty milliseconds and kills any process that exceeds its declared ram_mb manifest limit. CPU affinity is enforced via psutil. Two automated cap tests prove kill-on-overrun and let-it-finish-under-cap.
• Real advanced scheduler. Hard constraints (require_labels filtering, anti_affinity blast-domain separation) and soft preferences (spread_key topology-aware spread across racks or zones, priority-aware batch_place for incoming app batches). Seven automated advanced-scheduler tests cover every policy plus backward-compatibility with the simple best-fit scheduler.
• Real role-based access control with multi-tenant quotas. Roles include admin, operator, viewer, and tenant. Tenant tokens are scoped to their tenant's app namespace. Per-tenant quotas (max_apps, max_ram_mb) bound how much of the rack any tenant can consume. Tokens are salted-sha256 stored; plaintext is shown once at mint and never persisted. The REST surface re-reads rbac.json on every modification so out-of-band CLI edits take immediate effect. Twelve automated RBAC tests plus one CLI round-trip test covering tenant create, user create, token mint, whoami, and on-disk verification.
• Real measured benchmarks. uniphi-dc bench runs deploy-latency, replication-throughput, reschedule-recovery, and concurrent-capacity benchmarks across configurable cluster sizes, emits markdown and JSON, and produces reproducible numbers. The shipped artifacts include a BENCH_RESULTS.md measured on an eighty-core Windows host as a reference baseline.

Measured numbers shipped with this SKU (real loopback, 2026-06-27)

Reproducible by any buyer with the installed binary: uniphi-dc bench --scale 1,2,4,8 --apps 30 --output bench.md. A LAN over Wi-Fi 6 adds approximately three-tenths of a millisecond round-trip; treat the numbers above as upper bounds on what real network paths deliver.

What is in the Complete deliverables packet

• The full UniPhi DC source tree, ready for the buyer's own deployments.
• The built single-file binary (uniphi-dc.exe), the Home Edition zip artifact for distribution, and the Inno Setup installer script for the buyer's own MSI builds.
• The complete reference-board hardware schematics (KiCad sources) for the CM5 node carrier, the rack hub board (ESP32-S3 management + ESP32-C6 mesh radio + 2.5 GbE uplink + OLED + status LEDs for eight managed nodes), and the USB / battery-USB / DisplayPort / DisplayPort-battery retrofit dongle family.
• Layout-ready specifications for every board: stackup, placement, diff-pair rules, antenna keepout, bring-up bench checklist.
• The rack-hub firmware skeleton (ESP32-S3 Arduino sketch) — Wi-Fi STA bring-up, TCP listener on fabric port 7800, status-LED control.
• The full architecture documentation: README, RACK.md (three-altitude node-rack-super-hub architecture), UNIPHI_HOME.md (thirteen residential-network problems and the thirteen-feature fix matrix), STATUS_AND_NEXT.md, STORE_LISTING.md, BENCH_RESULTS.md, BENCH_RESULTS.json.
• One hundred thirty automated tests covering every claim above; python -m unittest discover -s tests as the entry point.
• The patent-pending architecture specification: the wire protocol, the event-log canonical encoding, the storage chunk format, the mTLS handshake sequence, the scheduler policy interfaces, the RBAC permission matrix, the SuperHub federation primitive.

What is NOT included

• Telephone or real-time support. Email and postal only.
• International sale. USA-only. United States Dollars only.
• Custom development of the UniPhi DC binary. The buyer's engineering team may extend the source; new feature work performed by the inventor is a separate engagement priced per scope.
• Fabricated silicon. Hardware deliverables are schematics, layout specifications, and firmware skeletons. Fabricated PCBs and packaged chips are out of scope for this SKU.
• Cert programs. FCC Part 15 cert for any reference hardware that becomes a shipped product, and Wi-Fi Alliance trademark cert for any product calling itself "Wi-Fi", are the buyer's responsibility.

How a buyer uses this bundle

Most buyers fall into one of three patterns. The first is an enterprise infrastructure team building an internal personal-hyperscaler appliance for distribution across the organization's edge locations; UniPhi DC Complete becomes their reference codebase and reference hardware spec. The second is an OEM building a branded rack product for resale; UniPhi DC Complete becomes the architecture they productize and ship under their own brand. The third is an integrator engaged by a single end customer to deploy a rack at the customer's site; UniPhi DC Complete becomes the integrator's tool kit.

In all three patterns the buyer's engagement with the inventor is post-purchase by email. The deliverables packet is comprehensive enough that an engineering team can build against it without further interaction; the inventor remains reachable for clarifying questions during normal use.

System requirements for the buyer's own deployment

• One or more modern hosts to act as hub or node — Windows 10 / 11, Linux distributions with Python 3.10+, or any platform the buyer's team ports to. The source is portable; the binary ships for Windows and is buildable for Linux.
• A network providing reachability between hosts. Wi-Fi 5 / 6 / 6E, wired Ethernet, or any combination.
• Optional: the buyer's choice of monitoring stack to scrape the Prometheus /metrics endpoint and ingest the structured JSON logs. UniPhi DC integrates with any of them; the listing does not require a particular one.

How to order

Email christopher@cri-one.com with the subject line UniPhi DC — UNIPHI-COMPLETE. Include the intended deployment context (enterprise infrastructure team, OEM productization, integrator engagement, or other) and the expected scale of deployment. The inventor responds with payment arrangements within one business day. Delivery is by email; the deliverables packet arrives once payment clears.

Postal contact:
Christopher Gabriel Brown
1341 Wellington Cove
Lawrenceville, GA 30043-5255
United States

Patent-pending. USA-only sales. United States Dollars only. Email-only contact.