01
Unclear access
Administrative privileges, MFA, and external access are not documented consistently.
Elkaza · Vienna, Austria
A concept for stable IT infrastructure in growing teams.
Elkaza is being developed as a possible future offering for networks, access, backups, and documented IT operations.
Three common starting points in small businesses
02
Unverified recovery
Backups exist, but restore procedures and ownership are unclear.
03
Processes built around individuals
Recurring tasks and system changes depend on knowledge held by one person.
Three planned service areas
The plan is to begin with clearly bounded assessments and project work. No offer is currently available.
IT & Security Baseline
Current-state review, MFA and access, backup/restore readiness, patch fundamentals, roadmap, and documentation.
View conceptInfrastructure & Access
Networking, remote access, segmentation, and clear system, access, and infrastructure documentation.
View conceptAutomation & Documented Operations
Recurring tasks, Linux/Docker where appropriate, monitoring concepts, runbooks, and deployment documentation.
View conceptPlanned workflow
How a future assessment could work
- 01
Current state
Capture systems, access, backups, and documentation in a structured review.
- 02
Priorities
Classify risks and dependencies in a way stakeholders can follow.
- 03
Roadmap
Document a realistic and clearly bounded action plan.
- 04
Later implementation
Implementation only after commercial activation and with a clearly defined scope.
Mohamed Elkaza
Founder / Technical Lead
Mohamed Elkaza is developing Elkaza in Vienna, with a technical focus on IT infrastructure, networking, and automation.
Vienna, Austria
Technical portfolioNot customer references
Illustrative scenarios
Fictional situations, possible approaches, and target states. Not customer references.
Illustrative scenario
Network Modernization for Retail Company
SituationUnstable remote access, inconsistent Wi-Fi, and insufficient network documentation.
Possible approachA possible approach would combine an inventory, segmentation concept, firewall-rule review, and updated network documentation.
Target stateA clearly segmented network with documented access paths and prioritized improvements.
Illustrative scenario
Security Baseline for IT Service Provider
SituationInconsistent MFA use, shared administrative access, and no documented restore verification.
Possible approachA possible approach would review access and MFA, examine patch routines, and document a backup-restore test.
Target stateA prioritized security baseline with clarified access, restore evidence, and practical next steps.
Project in preparation
Elkaza is not currently accepting inquiries or orders. A business contact channel will only be activated before a possible commercial launch.
Frequently Asked Questions
How could a future project work?
The planned starting model is a bounded assessment covering current state, priorities, and a documented roadmap. Timing and scope would only be set in a concrete future offer.
How would changes be controlled?
A possible future project would define maintenance windows, testing, and rollback options appropriate to the systems involved.
What would happen after a project?
The intended output includes clear documentation, runbooks, and an orderly handover. Ongoing support remains an unvalidated future model.
Can these models be ordered already?
No. The models shown only document the current planning stage and are not offers.