01 / About me
About me
My goal is to understand technical systems end to end: how they are designed, implemented, secured, deployed, monitored, backed up and reviewed.
I currently work across software development, IT infrastructure, cybersecurity, identity and access management, monitoring, automation and AI-assisted engineering. My practical technology stack includes .NET and C#, Blazor, PostgreSQL, Docker, Windows Server and Linux-based environments.
Rather than presenting unfinished ideas as completed products, I document projects according to their real state. Implemented functionality, active experiments and future plans are kept clearly separated.
02 / TCS
What is TCS?
TCS stands for Trace Core Security.
It is the working name for a growing portfolio of practical technology projects focused on security, infrastructure visibility, identity, monitoring and operational automation.
Projects such as TCS.Core, TCS.IAM and TCS.Monitor explore different parts of this wider direction — from cybersecurity and operational context to identity foundations and service-level monitoring. Each project is developed incrementally, and its current status is documented openly.
03 / Areas of work
Areas of work
Software engineering
Building maintainable applications and services with clear boundaries, testable behaviour and documented architecture.
Infrastructure and monitoring
Exploring infrastructure operations, observability, asset visibility, deployment, backup and recovery.
Cybersecurity
Designing systems with security, access control, auditability and operational risk in mind.
Identity and access
Working on identity foundations, authentication, authorization and controlled administration.
Automation and applied AI
Using automation and AI-assisted workflows to support implementation, analysis, verification and technical documentation.
NIS2- and GDPR-aware design principles are considered where they are relevant to the system and its intended use.
04 / Working principles
How I approach projects
Evidence over claims
Project status should reflect what has actually been implemented and verified, not what is merely intended.
Traceable decisions
Important architectural and technical decisions should include their reasoning, constraints and consequences.
Secure and predictable behaviour
I prefer explicit boundaries, deterministic logic, fail-closed behaviour and systems that can be reviewed and audited.
Continuous verification
Implementation is only one part of the work. Testing, review, documentation, backup, recovery and operational validation also matter.
05 / Purpose
Why this site exists
This site serves as both a public portfolio and a technical record of my work.
It contains project overviews, technical articles, architecture notes, implementation decisions, experiments and lessons learned. Project pages present the concise current state, while the writing provides the deeper context behind individual decisions and results.
The purpose is not only to show completed outcomes, but also to preserve how those outcomes were reached.
06 / Direction
Current direction
My current direction is to deepen my ability to design, build, secure and operate reliable systems independently.
At the same time, I want to develop the strongest TCS concepts into practical tools that are understandable, maintainable and genuinely useful beyond the learning process itself.
Explore
Explore the work
Follow the current state of TCS projects or read the technical notes behind them.