POND: Powerful On-premises Network Devices.
A POND is a local infrastructure scene: different systems, each with a role, connected into a workflow a buyer can imagine in their own shop, office, lab, or studio.
Print and automation POND
A small business can keep print control, document storage, and automation local. The diagram is not just technical; it is a room layout for an operating workflow.
flowchart LR
OP["Operator / API"]
KOI["Mini KOI LS
label and print control"]
PRN["Printer fleet
labels, invoices, forms"]
COD["Mini COD
documents and files"]
PF["PILOTFISH
n8n automation"]
CAT["CATFISH
backup target"]
TUNA["Mini TUNA
local apps"]
OP -->|"submits jobs"| KOI
KOI -->|"routes output"| PRN
KOI -->|"stores originals and history"| COD
PF -->|"triggers print workflows"| KOI
PF -->|"reads and writes business files"| COD
TUNA -->|"hosts dashboards and tools"| PF
COD -->|"protected by"| CAT
PF -->|"configuration backup"| CAT
classDef mini fill:#dceff4,stroke:#7aa8b6,color:#111;
classDef enterprise fill:#e3ede2,stroke:#88a584,color:#111;
classDef external fill:#f5f6f7,stroke:#c8d0d7,color:#111;
class KOI,COD,PF,TUNA mini;
class CAT enterprise;
class OP,PRN external;
School of Mini TUNA
A School repeats one species. Several Mini TUNA machines become a small application cluster for experiments, services, VMs, or container workloads.
flowchart LR
LB["Local router / load entry"]
T1["Mini TUNA
node 1"]
T2["Mini TUNA
node 2"]
T3["Mini TUNA
node 3"]
COD["Mini COD
shared storage"]
CAT["CATFISH
backup"]
LB --> T1
LB --> T2
LB --> T3
T1 <-->|"shared app data"| COD
T2 <-->|"shared app data"| COD
T3 <-->|"shared app data"| COD
COD -->|"protected by"| CAT
classDef mini fill:#dceff4,stroke:#7aa8b6,color:#111;
classDef enterprise fill:#e3ede2,stroke:#88a584,color:#111;
classDef external fill:#f5f6f7,stroke:#c8d0d7,color:#111;
class T1,T2,T3,COD mini;
class CAT enterprise;
class LB external;
Different roles working together
A POND is a small local ecosystem: COD for primary storage, CATFISH for backup, TUNA or PILOTFISH for apps and automation, KOI LS for print workflows.
It is useful when a buyer wants an understandable local infrastructure stack rather than one generic machine trying to do everything.
Same role clustered together
A School is a cluster of one species. For example, several Mini TUNA systems can form a School of TUNA for application nodes, lab experiments, or virtualization capacity.
This keeps the naming clear: POND means mixed roles, School means repeated role.
Common combinations
These are examples for future documentation pages, diagrams, and sales explanations.
Print and automation POND
Mini KOI LS plus Mini COD plus PILOTFISH for shipping benches, repair shops, small warehouses, printers, and local automation.
Small office resilience POND
Mini COD for active documents plus CATFISH or CATFISH Nephew for backup and restore practice.
School of TUNA
Multiple Mini TUNA application nodes for containers, VMs, experiments, and local service clusters.