guest@stargatelabs:~$ whoami
private lab — infrastructure, security, systems

STARGATE LABS

Custom water loops, cryogenic rigs that should not exist, and the software that keeps them alive. Nothing taken for granted here: every number gets measured, every defect becomes a test.

./systems --live

17Orchestrated scanners
14,071TypeScript lines, ARGUS
29,537Python lines, ARA
23,286Rust lines, StargateCryo

[i] Measured from the code, not declared.

./projects --all

[01]ARGUS

[security] Seventeen scanners, one verdict: 6 recon, 4 DAST, 1 SAST, 2 SCA, 2 secrets, 1 API, 1 fuzz. Pinned images, authorised targets only. Two AI models: one plans, one executes. v0.2.0.

[02]ARA

[voice] Voice in, voice out, no cloud: Whisper transcribes, Kokoro answers, the router decides in under 5 milliseconds. Seven destructive actions ask for confirmation. Local RAG memory.

[03]StargateCryo

[thermal] Cold with numbers: serial PID, measured condensation margin, 6 alarm channels and 3 profiles. If the pump stops, the TEC scales itself down to 50%. No sockets in the code: it runs wherever the controller reaches.

[04]TechDash

[monitor] The rig under your eyes: CPU/GPU temperatures, load, fans, pumps, disks. Condensation and thermal alarms. Reads fast, does not do pretty charts.

[05]Cryogenic setups

[hardware] Sub-zero without dying: TEC cooling on 10th and 13th gen Intel, managed condensation, safe boot curves. Protections first, records later.

[06]SignalRGB plugin

[reverse] Real pixels on a lying deck: Loupedeck protocol rewritten in RGB565, clean 480 × 288 where the stock overlay stamps its logo in the middle.

[i] ShipExpress, the production ERP, lives on its own site: shipexpress.it. Not here: this page is about the lab, not shipping.

./stack --list

Next.js 16React 19TypeScript strictPostgreSQL 17Prisma 6Redis 8BullMQTailwind CSS 4Zod 4VitestPlaywrightPythonRust

Next.js, React, TypeScript, PostgreSQL, Prisma, Redis, Tailwind CSS, Python, Rust, Linux, Docker, Git

./method --show

  1. Validation at the edges. Zod on all external input, unknown never any, parameterised queries, transactions on multi-table operations.
  2. Verified isolation. Wherever there is a boundary — tenant, network, process — I test it, I do not declare it.
  3. Every finding becomes a test. The defect does not come back. exit 0.
  4. Operational security. 2FA on root, audit trail on critical ops, rate limits, brute-force detection, session blacklist on Redis.

./hardware --rules

./contact --open

Private lab. For a hardware project, an audit, or a question worth measuring: