Concept

Infrastructure should be easy to imagine.

The fish names are a language for local infrastructure. They help describe rooms, workflows, and combinations before anyone has to read a specification table.

Scene

Start with the room

A shipping bench, small office, home lab, repair shop, or local dev stack gives the buyer a picture of where the system belongs.

Role

Fish taxonomy

COD, CATFISH, DOLPHIN, TUNA, KOI, and PILOTFISH name the job the system performs: storage, backup, database, application, printing, or automation.

Combination

PONDs and Schools

A POND combines different roles. A School repeats one role, such as several Mini TUNA application nodes.

POND

Powerful On-premises Network Devices

A POND is both a practical acronym and a visual idea: different fish living together in one local infrastructure environment.

The public promise

We show how local systems can work together before we ask the buyer to care about model numbers, controllers, drive bays, or network ports.

Performance

Role-Based Power

DIRT BEEN GOLD does not define power only by the newest processor, newest platform, or highest benchmark score. Power is evaluated in context: how effectively a system fulfills its intended local infrastructure role.

Power through specialization

A business desktop may be ordinary as a general-purpose PC, but powerful as a Mini KOI LS print and label station, document node, automation station, or lab appliance.

Purpose-driven performance

A previous-generation enterprise server can still be powerful as CATFISH backup, COD storage, DOLPHIN database, or TUNA application infrastructure when matched to the right role.

In a POND, every system does not need to do everything. Each system should be strong in its own role, and the combined local ecosystem can be more useful and resilient than one oversized general-purpose machine.

Hardware classes

The same role can be built in different physical classes.

Mini

Desktop-class local systems

Mini systems use Dell OptiPlex MT 7050 hardware: compact, familiar, practical, and well suited to small rooms and local workflows.

Enterprise

Full/Mid-size tower systems

Enterprise systems use Supermicro tower platforms, Xeon E5 processors, ECC registered memory, server storage controllers, and remote management.

Nephew

Same Blood - Smaller Frame

Mid tower enterprise-grade

Nephew is planned as the in-between class: Xeon E3, ECC UDIMM, server discipline, and less expansion than the larger Enterprise systems.

Mini build levels

Mini systems are practical desktop-class infrastructure. The levels describe the buyer experience: accessible, convenient, or professional.

Base

Mini COD 3D / Mini COD 4

The simple, accessible starting point. A prepared storage platform for buyers who want local files, lab experiments, and a clear way to begin without paying for features they do not need yet.

Plus

Mini COD 3D Plus / 4 Plus

The same approachable Mini COD idea, upgraded for everyday convenience. Plus is for people who expect to touch the machine, change drives, organize media, and live with the system instead of only owning it.

Pro

Mini COD Pro S24 / S28

The professional Mini choice. Pro is for serious small offices, studios, labs, and self-hosters who want a more refined build, better serviceability, and a higher ceiling while staying below full Enterprise class.

Role matrix

The role is the job. The class is the body it lives in.

Role name Code Primary job Example classes
COD COD Primary storage / document server COD, COD Nephew, Mini COD (Plus/Pro)
CATFISH CAT Backup server CATFISH, CATFISH Nephew, Mini CATFISH
DOLPHIN DOL Database server DOLPHIN, DOLPHIN Nephew, Mini DOLPHIN
TUNA TUN Application / virtualization server TUNA, TUNA Nephew, Mini TUNA
GROUPER GRO Workstation GROUPER
KOI MKO Print Server, Label Station Mini KOI LS (Mini KOI Label Station)
PILOTFISH PTF Automation Server, Workflow Orchestrator PILOTFISH

Products are what we sell. Architecture is what we know.

A single unit may be sold through eBay. The broader architecture explains why that unit exists, what it should be paired with, and where it fits in a local infrastructure POND.

Public proof, when useful

  • Plain-English product guides
  • Compatibility and limitation notes
  • Testing summaries when buyers need them
  • Links to active marketplace listings