Zlatko Lakisic

Logo

Private Networks Architect & Practice Lead · Enterprise Presales & Connected Solutions

View the Project on GitHub zlatko-lakisic/zlatko-lakisic

Technical Strategy

← Main Portfolio · Resume · Architecture Case Studies


Engineering Philosophy

Outcome-first delivery

Complex technical debt and legacy modernization only matter when they connect to measurable business outcomes. My practice centers on translation: customer workflows and operational KPIs become integration patterns, discovery artifacts, and reusable implementation playbooks that engineering teams can execute against.

Technical governance

High-performing delivery depends on architectural north stars, quality baselines, and early mitigation of long-term risk — whether integrating ~50 systems for a global retailer or hardening national payment infrastructure. Governance is not bureaucracy; it is the scaffold that keeps scale from becoming fragility.

Recycle-first engineering

Operational waste is often a design choice, not a budget constraint. Repurposed hardware, localized inference, and sandbox clusters provide production-faithful test beds without standing cloud cost — the same mindset that drives efficient enterprise platform adoption.

The home lab is not a hobby layer on top of enterprise work; it is where those principles get pressure-tested. Maximizing bare-metal efficiency and container density on repurposed nodes directly parallels how organizations should right-size cloud estates: fewer idle VMs, higher utilization per host, and workloads placed where latency and data-sovereignty requirements actually justify the cost. Running Ollama inference, Frigate NVR, and agent sandboxes locally before recommending architecture to clients means proposals are grounded in real utilization curves — not vendor sizing calculators.

That recycle-first discipline also mitigates vendor lock-in. When you can reproduce production-shaped failures on bare-metal Kubernetes clusters built from hardware that would otherwise be retired, you reduce dependence on a single hyperscaler’s managed primitives for every experiment. The enterprise translation is straightforward: higher container density and disciplined workload placement slash cloud spend; standardized integration boundaries (MCP, REST, MQTT) keep teams portable across providers; and governance applied early — segmented networks, credential-scoped catalogs, documented runbooks — prevents the technical debt that inflates corporate infrastructure overhead over time.


AI Transformation Framework

The portfolio homepage illustrates four pillars for enterprise AI adoption:

Pillar Focus
Strategy Outcome-first roadmaps aligned to business metrics
Integration API and MCP tool boundaries
Empowerment Self-hosted inference and agent workflows
Governance Credential-scoped catalogs, segmented trust, operational sustainability

How Strategy Maps to Delivery

Domain Strategic approach Where to read more
Enterprise integration Discovery → HLSD → dual-mode bridges for legacy and modern estates Walmart case study
Healthcare connectivity Private networks as integrated solution elements, not commodities Healthcare architecture
Identity & access SAML/OAuth federation, segmented trust zones, credential-scoped catalogs Identity & Access
AI & MCP platforms Local inference, agent orchestration, MCP tool layers Local AI and MCP
Infrastructure efficiency Bare-metal density, VLAN isolation, production-faithful sandboxes Infrastructure and Home Lab

Representative Impact

Selected outcomes that illustrate how strategy translates to delivery — full career history is on the Resume.


← Back to Main Portfolio