Enterprise workflow systems
BPMN-driven and integration-heavy systems designed to coordinate real business processes without hiding operational constraints.
Projects
Systems and products framed around the problems they are trying to solve.
The goal here is to make projects like Onklave and Fnez read as serious platform narratives: security, architecture, workflow design, and the longer-term systems thinking behind them.
Narrative case studiesSystem designProduct depth
What the project work signals
A broader body of work behind the flagship narratives.
Cloud platform delivery
Work across APIs, control planes, frontend systems, and internal platforms where reliability and scale matter.
Product-oriented infrastructure
Systems designed not only to function, but to shape how teams and users safely interact with complexity.
Narratives
Project pages that support credibility and discovery.
Onklave
A platform rethinking browser security through zero-trust principles, isolated execution, and stricter credential boundaries.
Onklave is the clearest expression of the long-term technical narrative behind jono.me: building secure computing environments that question inherited assumptions. The project explores how browsing, identity, and remote access can be decomposed into safer runtime boundaries rather than treated as a monolithic desktop browser experience.
- Secure browsing environments
- Credential isolation
- Distributed execution
- Identity security
Fnez
A SaaS product focused on making complex workflows feel dramatically easier to use without reducing technical capability.
Fnez represents the product and usability side of the brand. It reflects the belief that many technical systems are harder than they need to be because complexity is exposed directly to users instead of being absorbed by the platform.
- Workflow simplification
- Platform usability
- Operational clarity
- Developer-first product design
Platform engineering work
Cloud infrastructure, CI/CD systems, automation tooling, and internal platforms that help teams build and deploy software more reliably.
This body of work ties the consulting, enterprise, and systems-thinking sides of the brand together. It focuses on the foundations that allow engineering teams to move with more confidence: repeatable infrastructure, better delivery pathways, stronger operational models, and internal tooling that creates leverage.
- Cloud architecture
- Infrastructure automation
- Developer tooling
- Delivery systems
Framing
A portfolio that reads like applied systems thinking.
Context
Each project is presented around the constraints, decisions, and tradeoffs that shaped it — not only the outcome.
Signal
That creates a stronger impression of senior technical judgment than a conventional gallery of screenshots or feature lists.