ABOUT / SETHIOS
Software is not only what I build. It is how I transform ideas, research, and real problems into working systems.
I transform ideas, research questions, and real constraints into coherent software systems.
● Open to meaningful conversations
Relevant project, architecture, research, and knowledge-sharing discussions are welcome.
01 / PROFILE
A practice across disciplines.
SETHIOS is an independent technology practice spanning product engineering, system architecture, applied AI, digital health, and technical research.
The work begins with the system around the software: the people, institutions, data boundaries, operating conditions, and outcomes that shape what should be built.
Engineering
Build reliable interfaces, services, and platform foundations.
Architecture
Define boundaries, responsibilities, and change paths.
Research
Investigate questions through explicit methods and evidence.
Product
Connect technical possibility to useful system behavior.
HealthTech
Model trust, continuity, and clinical-system constraints.
02 / CURRENT FOCUS
Privacy-preserving AI
Collaborative intelligence with explicit data boundaries.
Federated learning
Distributed healthcare experimentation and orchestration.
Health information systems
Continuity across citizens, care, institutions, and intelligence.
Scalable digital platforms
Modular systems designed to evolve.
Resource-aware architecture
Software shaped by real infrastructure constraints.
Research engineering
Turning experimental evidence into inspectable systems.
03 / PRACTICE TIMELINE
Experience shaping the current direction.
- Current direction
SETHIOS
ENTRY / 01Independent technology practice
Building a connected body of products, frameworks, research, and technical writing around modern systems and digital health.
- Product and system architecture
- Full-stack engineering
- Research framework design
- Technical communication
Next.jsTypeScriptDistributed systemsApplied AI - Ongoing practiceENTRY / 02
Research and product translation
Connecting experimental questions to architecture without presenting prototypes as production systems.
- Experiment architecture
- Privacy-aware system design
- Capability modeling
Federated learningFlowerHealth dataSystem modeling
04 / CAPABILITIES
Engineering
- Full-stack applications
- API and service design
- Type-safe systems
- Performance and accessibility
Architecture
- Domain modeling
- Distributed systems
- Platform boundaries
- Interoperability
AI / Data
- Applied AI direction
- Federated learning
- Experiment systems
- Privacy-aware design
Research
- Protocol translation
- Technical figures
- Results presentation
- Research tooling
Infrastructure
- Delivery systems
- Observability direction
- Resource-aware design
- Resilient workflows
05 / TECHNOLOGY PERSPECTIVE
Tools change. Architecture, constraints, and outcomes matter more.
Technology choices are useful when they clarify boundaries, reduce operational burden, preserve trust, and make a system easier to evolve.
06 / PRINCIPLES
Systems thinking
Understand relationships and constraints before optimizing a component.
Research-driven engineering
Separate verified evidence from assumptions and product promises.
Maintainable boundaries
Design responsibilities so systems can change deliberately.
Privacy-aware design
Treat data custody, consent, and access as architecture.
Resource awareness
Design for the environment that actually exists.
Real-world usefulness
Judge technical choices by the outcomes they enable.
SELECTED ENGINEERING
Explore Work
INTELLIGENT SYSTEMS
Explore Research