Okulo mark — stylized eye aperture

About

Okulo is a behavioral code analysis CLI. The name — and the mark — come from an older idea of looking carefully: the Ser Oculado of Peru’s Paracas culture.

The Ser Oculado

On the south coast of Peru, Paracas artisans wove and painted a recurring figure known as the Ser Oculado (Oculate Being) — sometimes described in Spanish as a “ser ocular”: a mythical presence defined by large, concentric eyes. It appears on funerary cloths, ceramics, and ritual objects from roughly the first millennium BCE onward, and is often read as a being that watches, remembers, and marks what matters across life and ancestry.

Those oversized eyes are not decoration. They signal attention — a gaze that does not skim the surface.

Okulo takes that idea into software: see the code that is actually costing you time — not every line, but the places where complexity, change, and people collide.

Why that fits the tool

Static analysis looks at structure. Okulo looks at behavior: Git history, how often files change, who owns knowledge, where debt collects interest. Like the Ser Oculado, it is built to notice what a quick glance misses — hotspots, temporal coupling, ownership islands, and refactor paths that pay back.

The product stays local and terminal-first. You bring your repo; Okulo helps you see it with clearer eyes.

Creator

Okulo is created by Erikson Murrugarra — Lead Staff Engineer and architect focused on secure, domain-driven systems, and an author who writes about complex technical ideas in plain language.

His work centers on Domain-Driven Design, event-driven and clean architectures, with experience across Blockchain/Web3, artificial intelligence, and IT strategy. He holds a Master’s degree in IT Management and mentors engineers who want to think critically about systems — not just ship features.

Areas he cares about:

Okulo comes from that same instinct: reduce noise, surface risk, and help teams act where it counts.

Connect on LinkedIn →