tech/groveBook a call

DevOps & automation consulting

Infrastructure that matches its code.

AI app modernisation, OpenShift Virtualisation, VMware to OpenShift migration and cloud landing zones, set up properly and handed over with the documentation your team needs to run it.

~/infrastructure
$ terraform plan
aws_vpc.main: Refreshing state...
aws_instance.app[0]: Refreshing state...

No changes. Your infrastructure matches
the configuration.

$ ansible-playbook site.yml --check
PLAY RECAP *****************************
web01 : ok=24 changed=0 failed=0
web02 : ok=24 changed=0 failed=0
db01  : ok=31 changed=0 failed=0
years of enterprise DevOps
10+
years of enterprise DevOps
servers moved to monthly patching
2,800
servers moved to monthly patching
workloads migrated to AWS
500+
workloads migrated to AWS
industry certifications
8
industry certifications

Services

Fixed-scope work, delivered remotely

Every engagement ends with a written handover, so your team can run what was built.

Red Hat platforms

Owned, rebuilt and upgraded enterprise Ansible Automation Platform installs over several years.

AAP setup

5–10 days

A production-ready Ansible Automation Platform, configured as code so it can be rebuilt.

  • Architecture: controller, automation hub, Event-Driven Ansible, execution nodes
  • Install on RHEL VMs or OpenShift (containerised)
  • LDAP, Active Directory or SSO with role-based access
  • Organisations, inventories, credentials and job templates as code
  • Optional ServiceNow, Azure DevOps and Git integrations

You get: Working platform, config-as-code repository, admin runbook, handover session

AAP health check & upgrade

2–5 days

An assessment of an existing AAP install, followed by a planned upgrade.

  • Review of version, architecture, performance, backups and security
  • Written report with risks and prioritised fixes
  • Upgrade to AAP 2.5 within your change window
  • Rollback plan and post-upgrade checks

You get: Health check report, upgrade runbook, completed upgrade

Red Hat Satellite setup

5–10 days

Central content, patching and subscription management for RHEL servers.

  • Satellite and Capsule install and sizing
  • Content views and lifecycle environments (Dev → Test → Prod)
  • Host registration, activation keys and subscriptions
  • Patching and errata workflows, optionally driven from AAP
  • Provisioning templates for new RHEL builds

You get: Working Satellite, patching runbook, host onboarding guide

Ansible playbook development

1–5 days per workflow

Manual runbooks turned into tested, reusable automation.

  • Roles and playbooks with linting and tests
  • Packaged as collections, published to AAP or Git
  • Server builds, patching, user management, compliance checks

You get: Code in your repository, README per role, AAP job templates

Cloud & infrastructure as code

Secure, repeatable cloud foundations defined in Terraform, and bills that stop creeping up.

Terraform & AWS foundations

5–10 days

A secure AWS setup defined in Terraform, sized for startups and small businesses.

  • Multi-account structure with AWS Organizations and guardrails
  • Networking and baseline security controls
  • Click-built resources brought under Terraform with remote state
  • Plan-and-apply pipeline from Git

You get: Terraform repository, architecture diagram, operating guide

Cloud cost review

2–3 days

A fixed-price review of an AWS or Azure account that finds and ranks savings.

  • Spend breakdown by service, environment and owner
  • Idle and oversized resources, storage tiers, savings plans
  • Quick wins applied with your approval
  • Tagging and budget alerts so savings stick

You get: Savings report with estimated monthly impact, list of changes made

Containers, CI/CD & GitOps

Every change reviewed in Git and deployed the same way, every time.

Kubernetes / OpenShift GitOps

5–10 days

Cluster deployments driven from Git, so every change is reviewed and repeatable.

  • Argo CD with an app-of-apps structure
  • Helm charts or Kustomize overlays per environment
  • Tekton or GitHub Actions builds feeding the cluster
  • Health checks and monitoring with Prometheus and Grafana

You get: GitOps repository, onboarding guide for new applications

CI/CD pipeline setup

2–5 days

Build, test and deploy pipelines for teams still releasing by hand.

  • GitHub Actions or Azure DevOps Pipelines
  • Build, test, scan and deploy stages with production approvals
  • Secrets kept in the platform's vault, never in code
  • Static sites and serverless apps on AWS

You get: Working pipelines, documentation, handover session

Operations & AI automation

Hands-off operations, and AI that does useful, auditable work.

Patching automation

5–10 days

Hands-off patching for Windows and Linux fleets, from the approach that took 2,800 servers to monthly cycles.

  • Patch groups, schedules and maintenance windows
  • Pre- and post-patch checks, reboots and rollback triggers
  • ServiceNow change and incident integration
  • Fleet-wide patch status dashboard

You get: Patching automation, compliance report, operations runbook

AI automation prototype

3–5 days

Let staff run approved automation by chatting, or add AI to an existing workflow.

  • Teams or Slack chatbot that launches AAP job templates
  • Built on Amazon Bedrock or Azure AI Foundry
  • Guardrails: approved jobs only, with a full audit trail

You get: Working prototype, architecture notes, production recommendations

Training & enablement

Hands-on sessions online, in the evening or at weekends.

Workshops & coaching

Half-day sessions

Practical training built around your team's own use cases.

  • Ansible workshop: playbooks, roles, inventories, AAP basics
  • Terraform workshop: modules, state, workspaces, pipelines
  • CKA / CKAD exam coaching for individuals
  • Ongoing mentoring for teams adopting automation

You get: Session materials and lab exercises your team keeps

Approach

How an engagement works

A fixed scope and a written quote before any work starts. No surprises on the invoice.

  1. 01

    Free 30-minute call

    We talk through the problem and your environment.

  2. 02

    Written proposal

    Scope, deliverables, timeline and a fixed price, before any work starts.

  3. 03

    Delivery

    Work in agreed blocks, with a short progress update each week.

  4. 04

    Handover

    Documentation, code in your repository and a walkthrough session.

  5. 05

    Two-week support

    Questions and small fixes covered after handover.

Ways to work together

Fixed-price project

Agreed price for an agreed scope

Suits: Most services

Block of hours

Prepaid hours used as needed

Suits: Ongoing playbook work, ad-hoc fixes

Monthly retainer

Set hours each month

Suits: Platform support, mentoring

Availability: weekday evenings and weekends (Melbourne time). Maintenance-window work can be scheduled in advance.

About

Lead consultant, every engagement

Tech Grove Consulting is run by Ajay Paul, a DevOps Lead Consultant based in Melbourne with 10+ years of enterprise delivery. You work directly with the engineer doing the work, with no account managers and no hand-offs to juniors.

Ajay spent eight years automating and running platforms for Victorian Government agencies, and now leads infrastructure modernisation and migration work.

  • Moved patching for 2,800 servers from quarterly to monthly, cutting manual effort and overtime by 25%
  • Led automation for a migration of 500+ workloads from VMware to AWS
  • Led the move of Ansible Automation Platform from on-premises to OpenShift on AWS
  • Technical owner of enterprise AAP, OpenShift, Terraform and Azure DevOps platforms
Full background at ajpaul.cloud →

Certifications

  • AWS Certified Solutions Architect – Associate
  • Certified Kubernetes Administrator (CKA)
  • Certified Kubernetes Application Developer (CKAD)
  • Red Hat Certified Ansible Specialist
  • HashiCorp Certified: Terraform Associate
  • DevOps Foundation
  • ITIL
  • Cisco CCNA

Contact

Let's get your infrastructure back in line with its code

Book a free 30-minute call. Send a line about what you need and I'll reply within one business day.