Hamburg
Local base
Based in Hamburg, with projects and operating models across Germany.
IT for care teams, practices and regulated organisations
IT that stays calm, secure and understandable in day-to-day operations
Koek takes over, stabilises and modernises operating environments where sensitive data, many stakeholders and tight schedules leave no room for improvisation.
Hamburg als lokaler Anker, deutschlandweite Delivery für Organisationen, die stabile Systeme, schnelle Hilfe und saubere Dokumentation brauchen.
Schwerpunkte
Hamburg as the base, with projects and operations across Germany
Care services, practices, MVZ organisations and regulated businesses
Operations, security, cloud, support and integrations in one model
Clear technical ownership instead of vendor ping-pong
Care + practices
Sector focus
Koek aligns technology with real workflows in care and healthcare environments.
Managed operations
Delivery model
Support, security, documentation and infrastructure are treated as one operating model.
Clear structure
Collaboration
Clear prioritisation, documented systems and transparent escalation paths.
Who Koek supports
IT models for organisations where downtime and unclear ownership are expensive
The entry paths follow real operating situations instead of generic technology lists.
Regulated operations
Healthcare
In healthcare, working IT is not enough on its own. Systems need to be secure, documented and resilient in daily use, because outages, access errors or integration failures have direct consequences for care, administration and compliance evidence. Koek combines operations, security and data flows into one durable model.
- • Patient-related or health-related data demands controlled access and clean evidence trails
- • Specialist systems, communication, endpoints and infrastructure need to work together end to end
- • Outages or security gaps have immediate consequences for operations, trust and compliance
Care services
Care services work under time pressure, on the move and with sensitive documentation. When access fails, devices break down or specialist software is poorly integrated, routes, evidence and communication are hit immediately. Koek builds an operating model that reduces exactly that friction.
- • Mobile staff need secure, simple and always understandable access
- • Care software, email, devices and connectivity must work as one system
- • Time-sensitive field work and documentation duties cannot tolerate long disruptions
Practices & MVZ
Practice environments depend on working systems, clear reachability and fast response. When reception, treatment, documentation or billing slow down, patients and teams feel it immediately. Koek builds the technical foundation that reduces exactly those points of failure.
- • Practice software, communication and infrastructure must work continuously
- • User roles, permissions, endpoints and cover situations change frequently
- • Outages directly affect patient service, scheduling and billing
Turnkey practice IT
A new practice or site rarely fails because of one single issue, but because delivery dates, technology, specialist software and go-live are poorly coordinated. Koek brings planning, procurement, rollout, commissioning and stabilisation into one controlled sequence.
- • Many moving parts have to be coordinated cleanly in a short time
- • Delivery dates, fit-out work, specialist software and system setup all interact directly
- • A poor launch creates long follow-up work across operations, support and user adoption
Services
Services designed to work together in live operations
Support, security, infrastructure, cloud and modernisation are intentionally connected so one improvement does not create a new gap elsewhere.
Operational ownership
Managed IT Services
Koek takes over day-to-day IT operations for organisations that need clear ownership, clean standards and dependable follow-through.
- • Fewer operational interruptions and clearer response patterns
- • Traceable ownership for management, business teams and external partners
- • A more stable base for security, audits, expansion and integrations
Monitoring & maintenance
Koek monitors critical systems, plans maintenance windows and spots risks early so teams are not surprised by the next outage.
- • Higher availability for critical applications and services
- • Fewer unplanned disruptions outside agreed maintenance windows
- • Better data for priorities, SLAs and investment decisions
Backup & recovery
Koek combines backup with recovery planning, restore testing and clear responsibilities so backup turns into real operational readiness.
- • Lower outage risk during failures, attacks or operator mistakes
- • Clearer roles for IT, business teams and escalation during an incident
- • Better auditability for backup, retention and recovery
Cloud & infrastructure
Koek designs cloud, hybrid and infrastructure environments so identities, data, network zones and operations work together cleanly.
- • A more stable platform for growth, multi-site delivery and new services
- • Better control over identities, access and security zones
- • Higher readiness for compliance, backup and operational handover
Server & systems
Koek runs physical and virtual servers so roles, capacity, patching and dependencies do not become the blind spot of the operating model.
- • A more stable base for business applications and connected services
- • Less key-person risk and clearer ownership
- • More predictable hardware, refresh and migration decisions
Cloud migration
Koek plans migrations so teams stay productive, risks become visible early and the transition into the new operating state remains controlled.
- • A plannable migration instead of permanent exception mode
- • Stronger protection for sensitive data and permissions during transition
- • A cleaner base for further cloud, workplace or integration projects
IT structures that respect real care and practice workflows
Care teams, practices and healthcare-adjacent organisations do not need generic standard IT. They need systems, ownership and support routes that work with sensitive data, tight time windows and many stakeholders.
What this means in practice
Sensitive data, operating windows and user roles are built in from the start, not added later.
Care and practice software is treated as part of a stable operating model, not as an isolated tool.
Support, security, endpoints, identities and networks are planned and reviewed together.
Software environments
Specialist software works properly only when the rest of the environment supports it
Koek frames these pages as operating and integration context, not as unverified vendor partnership claims.
Care software
MEDIFOX DAN
When MEDIFOX DAN supports day-to-day care, mobile endpoints, access, connectivity, backup and support all need to work together. Koek builds that stable operating frame.
- • Care software combined with mobile endpoints, M365 and secure communication
Euregon SNAP Ambulant
Euregon SNAP Ambulant only runs smoothly when endpoints, access, secure communication and support paths are aligned. Koek puts that technical foundation in place.
- • Care workflows, mobile teams, endpoints and secure communication
Curasoft
With Curasoft, workstations, access, networking, backup and support need to fit together cleanly in day-to-day practice work. Koek provides that stable technical foundation.
- • Practice software combined with workplace, network and backup foundations
TOMEDO
In TOMEDO environments, Apple workstations, identities, access, backup and support need to stay aligned. Koek sets up that operating model so practice work remains dependable.
- • Apple-oriented practice environment, endpoints, backup and security
Why Koek
Calm in operations instead of loud project theatre
The collaboration should give decision makers orientation: clear status, clean ownership and priorities that hold up under pressure.
01
Koek does not build disconnected fixes, but operating models that hold up in daily work.
02
Technical delivery and communication stay close to the people actually responsible for operations.
03
Priorities follow risk, operational impact and feasibility, not the loudest ticket.
Approach
From assessment into stable day-to-day operations
Not every environment starts at the same point, but the framework of assessment, prioritisation, delivery and stabilisation stays clear.
01
Assess the environment
We map risks, dependencies, user roles and operational bottlenecks before defining the delivery scope.
02
Set the priorities
Measures are prioritised by operational risk, security impact and implementation effort.
03
Implement and document
Technology, permissions, fallback paths and operating documentation are implemented and documented cleanly.
04
Operate and optimise
After go-live we take over monitoring, support, changes and continuous optimisation.
Selected projects
Examples from real operations and migration situations
The case studies show typical starting points, delivery scope and credible outcomes without inflated success language.
Ambulatory care provider View case study →
Practice group / MVZ View case study →
Healthcare-adjacent business View case study →
Turning a grown care IT estate into a structured managed operations model
An ambulatory care provider was operating with many mobile devices, high support pressure and weak documentation. Koek took over the environment, clarified ownership, standardised operations and made support, security and recovery paths predictable.
Strukturiert
Support and escalation model restructured
Einheitlicher
Endpoint and documentation baseline consolidated
Belastbarer
Monitoring, backup and security baseline introduced
Bringing a multi-site practice group onto one consistent IT standard
A growing practice group was running each site with different networks, devices, telephony and support paths. Koek established one shared technical standard so new and existing locations no longer had to be operated like separate islands.
Einheitlich
Shared standard introduced for networking, workplaces and communication
Planbar
Rollout managed in waves instead of exception-driven steps
Nachvollziehbar
Support paths and ownership aligned across sites
Delivering a cloud migration with security and operational control
A healthcare-adjacent business wanted to modernise infrastructure and collaboration services without pushing operations into a risky big-bang cutover. Koek planned the migration in waves, tightened permissions and security logic, and deliberately carried go-live into a stabilisation phase.
Kontrolliert
Migration delivered in waves instead of one big-bang cutover
Gehaertet
Identity, security and backup model strengthened
Stabil
Go-live moved into a stable operating model
Direct access to ownership instead of an anonymous escalation chain
Koek is meant to feel like an operating partner, not a loose chain of tickets, handovers and vague updates. Decisions, risks and next steps should remain visible to the client team.
- - Direct access to technical ownership
- - Clear communication instead of vague consulting language
- - Close to operations, security and delivery instead of slideware
Profile
Berkay Koek
Strategic direction and technical concept
Connects technical direction, operational ownership and calm delivery for care, practice and regulated organisations.
- Pflege-IT
- Operations
- Security
- Cloud
Profile
Koek Delivery Team
Operations, security and infrastructure
Carries operations, security, infrastructure and delivery discipline into the client environment and supports a cleaner path into steady-state operations.
- Operations
- Infrastructure
- Integrations
- Practice IT
Trust
Why healthcare organisations should experience Koek as a calm operating partner
Trust here should not come from awards but from operational reality, clarity and accountable ownership.
Healthcare-adjacent workflow reality
Koek does not argue from the tool alone. The real context is documentation pressure, availability, sensitive data and the consequences of disruption.
Clear escalation instead of vendor ping-pong
Koek creates a framework where support paths, ownership and technical priorities stay traceable.
Security without corporate theatre
Controls need to be operated, documented and realistic for smaller and mid-sized teams. That is exactly what the model is built for.
Resources
A resource layer for expert content, checklists and next steps
Resources, guides, FAQ pages and articles support search intent while also helping internal orientation.
Insights
Insights and articles
Practical content on care IT, security, cloud, Microsoft 365 and operational structure.
- • Practical topics instead of shallow SEO filler
- • Focused on operations, risk and delivery
- • Regularly extended expert content
Guides and checklists
Structured guides for backup, Microsoft 365, takeovers and dependable operating foundations.
- • Compact and easy to review with stakeholders
- • Close to care, practice and SME realities
- • Useful for first assessment and internal alignment
Frequently asked questions before the first step
Answers on collaboration, security, takeovers, support boundaries and delivery topics.
- • Straightforward and without sales language
- • Grouped by theme instead of one long list
- • Useful for first orientation
Short operational updates instead of marketing noise
For teams that want relevant notes on care IT, practice operations, security and modernisation.
- • No daily marketing spam
- • Focused on concrete operational decisions
- • GDPR-conscious intake via the contact flow
Guides
Current checklists for operations, security and governance
Short, readable and built for teams that want clearer risk and priority structure.
Backup checklist for care providers and practices
A compact checklist for teams that want clearer backup, recovery and ownership in daily operations.
Best fit: Care providers, practices, MVZ organisations and regulated teams handling sensitive data
Updated: 4/18/2026
IT takeover checklist for historically grown environments
A guide for organisations taking over an estate, clarifying ownership or moving from diffuse responsibility into structured operations.
Best fit: Organisations with historically grown IT, multiple vendors or unclear technical ownership
Updated: 4/18/2026
Microsoft 365 governance checklist for regulated teams
A practical guide for roles, approvals, devices, sharing and cleaner platform rules in Microsoft 365.
Best fit: Care organisations, practices, MVZ structures and businesses with sensitive data flows
Updated: 4/18/2026
Insights
Latest articles for decision makers and operational teams
The content layer is meant to satisfy search intent while answering real questions from care IT, security, cloud and practice environments.
Backup strategies for care services without dangerous gaps
Why green backup jobs are not enough and how care providers should validate real recoverability.
2 min read 4/17/2026
Learn more → Cloud in healthcare: when it makes sense and what to watch
Cloud is not a goal by itself. This article explains when it is useful in healthcare and how security and operations need to align.
2 min read 4/17/2026
Learn more → IT for care services: the building blocks of stable operations
What ambulatory care providers need from infrastructure, mobile access, support and security to keep daily operations stable.
2 min read 4/17/2026
Learn more → FAQ
Typical questions before the first conversation
The FAQ covers the most common entry questions. Detailed prioritisation follows in the technical conversation.
Does Koek only work with healthcare customers?
The primary focus is on care services, practices and healthcare-adjacent organisations. Koek also supports selected regulated SMEs with similar operational needs.
What sets Koek apart from a general IT service company?
Koek combines operational ownership, security, documentation and integration capability. The focus is not isolated projects, but a durable operating model.
Can Koek take over existing environments?
Yes. In many cases we start with a technical assessment, stabilise the current estate and derive the prioritised improvements from there.
Next step
Assess the current situation clearly and define the next steps
If it is already clear that operations, security, cloud or integration need to be reorganised, a structured first conversation is the most useful starting point.