Skip to content

Infrastructure and ongoing support

Windows Server, Linux, Active Directory, networks and services. From diagnosing outages and incidents to standardizing procedures and publishing websites with version control.

Chat on WhatsApp(opens WhatsApp in a new tab)

What usually improves

  • Fewer recurring incidents
  • Predictable changes, with a rollback plan
  • Decisions based on logs, not perception
  • A documented environment, less dependent on one person

How much each point improves depends on the environment: volume, structure and data maturity. That is why no percentage is promised here. The assessment measures the current situation and defines, before any work starts, how the gain will be measured.

Diagnosis

Signs this solves your problem

  • The same incident comes back every week.
  • Changes in production are improvised.
  • Nobody can explain why the network or the service went down.
  • Knowledge of the environment lives in one person’s head.

Delivery

What gets done

  • Environment administration

    Windows Server, Linux, Active Directory, GPO, DNS, VPN, file shares and backups.

  • Networks and connectivity

    Switches, segmentation, mapping of network points and log-based diagnosis of outages.

  • Controlled change

    Diagnosis, change and validation kept separate, with a backup and a way back.

  • Technical web publishing

    Version control with Git, a test environment, a custom domain, technical SEO and accessibility.

  • Documentation and procedures

    Manuals, checklists and records so someone else can operate the environment and carry on the work.

Most-used tools

  • Windows Server
  • Linux
  • Active Directory
  • DNS and VPN
  • Git
  • Technical SEO

Projects

Related projects

Described anonymously: context, approach and outcome, without exposing the client or the implementation.

Publishing with Git, a test environment and a custom domain

Context
A website had to be developed and published safely, keeping every version and with no direct changes in production.
Approach
A repository with branches, pull requests, a test environment, static publishing and domain setup through DNS.
Outcome
Development, validation and production kept separate, with a change history and the ability to roll back.
  • Git
  • GitHub
  • GitHub Pages
  • DNS

Technical SEO, semantics and accessibility audit

Context
A website had to be prepared for launch with better indexing, semantic structure and technical consistency.
Approach
Review of headings, metadata, robots.txt, sitemap, Search Console, indexability, alt text and semantic elements.
Outcome
Lower technical indexing risk, a better structure for search engines and assistive technologies, and a reusable launch checklist.
  • Technical SEO
  • Semantic HTML
  • Accessibility
  • Search Console

Contact

Recognize any of these signs?

Describe how the problem shows up day to day. The first conversation is for understanding the situation and saying honestly whether and how help is possible.