Horst IT Consultancy
NL/EN
Get in touch

A clear starting point. Concrete deliverables.

A cloud challenge does not have to become a large programme. Start with what is needed: clarity, a working platform or greater freedom of choice.

Scope, involvement and deliverables are agreed in advance. Advice and implementation from the same specialist.

Conceptual architectural model of connected foundation, platform and application layers.
Concept illustration: a platform consists of interconnected layers.

Cloud architecture review

The platform is growing. Do the decisions still hold up?

A focused review of architecture, identity, networking, governance and operations. Agree the scope first, then assess the implementation and its dependencies.

Deliverables An architecture overview, supported findings and a prioritised improvement plan.

Discuss cloud architecture review

Kubernetes & GitOps

Add clusters without starting from scratch each time.

Review or implement cluster onboarding, Argo CD and platform components. Cover version control, access boundaries, recovery and the day-to-day work of development teams.

Deliverables Version-controlled configuration, a tested deployment procedure and documented operational responsibilities.

Discuss kubernetes & gitops

Digital autonomy & exit

Changing providers should remain a practical option.

Map dependencies across data, identity, platform services and operational knowledge. Assess open standards and CNCF components where appropriate; move or recover an agreed component in practice.

Deliverables A dependency overview and an exit plan with tested assumptions, risks and next steps.

Discuss digital autonomy & exit

Cloud architecture

A platform that fits business operations.

The current environment, objectives and constraints provide the basis for the design. Identity, networking, governance and cost control are considered together.

Support

  • Azure foundations: identity, networking, access policies and logging considered together.
  • Trade-offs between managed services, self-management and provider dependencies.
  • Governance, cost visibility and recoverability built into the design.

Intended deliverables

An architecture overview, recorded design decisions and prioritised improvements, including assumptions that still need testing.

Migration & development

From a working script to a maintainable platform.

From a first Azure workload to a repeatable deployment process. Implementation proceeds in manageable stages, with attention to infrastructure as code, testing and operations.

A workstation with a laptop, code on a screen and hands on the keyboard.
Code, configuration and operations belong to the same platform.

Support

  • Assess workloads, map dependencies and migrate in manageable stages.
  • Infrastructure as code, pipelines and tests for repeatable deployments.
  • Kubernetes, Argo CD and GitOps for repeatable cluster onboarding and platform configuration.
  • API integrations and identity synchronisation with validation, error handling and operational visibility.

Intended deliverables

Version-controlled code and configuration, a tested deployment procedure and agreements on rollback, monitoring and ownership.

Knowledge transfer

Independent changes, operations and recovery.

A platform needs to be transferable. Building together, recording decisions and providing focused documentation keep knowledge within the organisation.

Support

  • Design and build together, reviewing both decisions and implementation.
  • Practical runbooks for deployment, incidents, recovery and recurring operational tasks.
  • Handover through a real change or recovery exercise, with time for questions.

Intended deliverables

Documentation that matches the platform, clear responsibilities and a team that has practised the handover.

Pascal van der Horst

From design to everyday operations.

Architecture decisions affect daily operations. The article by Pascal van der Horst on identity at Wigo4it explains how AFAS, Keycloak and Entra ID work together in one synchronisation chain.

Read the practical experience

Support for a cloud challenge.

The current environment, intended outcome and available expertise determine the support required. An initial conversation makes the options concrete.

Discuss the possibilities Explore the approach