Infrastructure & networking
Build development and production environments, including the networks, storage and recovery procedures needed to run them.
- Environment design and implementation
- Systems, data services and recovery
Infrastructure &
DevOps consulting.
I plan and build infrastructure, connect it to the way your team develops and releases software, and help improve the systems you already run.
Services
How I can help
I work with teams that are building a new environment, improving an existing system, or bringing consistency to infrastructure and software delivery.
Kubernetes & platform engineering
Build and maintain Kubernetes platforms with shared configuration, a tested upgrade process and defined access for the teams using them.
- Cluster design and component standards
- GitOps, releases and platform monitoring
CI/CD & integration
Connect code changes to builds, tests and releases, from application deployment to integration across repositories and hardware.
- Application releases and software integration
- Shared pipelines, runners and test hardware
Identity & infrastructure security
Make it clear who can access each system, who approves it and how that access is enforced and recorded.
- System ownership and access approvals
- Directory groups, permissions and audit records
Selected work
Experience in practice.
From building a startup’s first environment to improving shared platforms, software integration and infrastructure access.
All project storiesBuilding startup infrastructure from the ground up
Complete development and production environments for startup teams, with client previews, automated delivery, company account access and recovery procedures.
- Infrastructure
- Application delivery
- Backup & recovery
Making Kubernetes platform upgrades predictable
Shared configuration and a staged release process across more than 25 clusters, giving application teams time to test changes before production upgrades.
- Kubernetes
- GitOps
- Release management
From a code change to a release candidate
Embedded Linux changes move through builds, baseline testing and wider system integration, with hardware preparation and Eiffel events connecting results to the software under test.
- Yocto
- Jenkins
- Eiffel
- Hardware testing
Bringing infrastructure access under control
A growing organisation moves from shared administrator credentials and informal access requests to individual accounts, system owners and documented approvals.
- Identity and access
- Asset management
- Infrastructure security
How I workFrom the first conversation
From the first conversation
to the handover.
I can take on a defined project or work alongside your team over time. We agree the scope and shape of the engagement around the work.
Understand the situation
Discuss the systems, the team and what needs to change. Agree whether a technical assessment is the right starting point.
Define the work
Set priorities, scope, responsibilities and the expected outcome. Agree how the work fits into your existing team and processes.
Build and improve
Implement the agreed changes, review them with the team and validate them in the relevant environments.
Document and hand over
Leave the configuration, procedures and context needed to operate the result. Agree further support if it is useful.
Working together
A few practical questions.
Can you work with our existing systems and team?
Yes. I can join an existing project, review the current setup and work with your engineers on improvements. We agree responsibilities, access and the change process before implementation.
Do we need a detailed specification before getting in touch?
No. Describe what you have, where you are getting stuck and what you want to achieve. We can agree an initial assessment if the next steps or scope still need to be defined.
What kinds of engagement do you consider?
Project work, ongoing collaboration and longer engagements are all possible. Scope, availability and commercial terms depend on the work and are agreed together.
How do you handle access and confidentiality?
We agree confidentiality requirements and access before work begins. I use your access and review procedures, with permissions appropriate to the agreed scope. An NDA can be included where needed.
What happens at handover?
Documentation and a walkthrough are part of the agreed scope. This can include configuration, pipeline definitions, operating procedures and an explanation of the decisions behind them. Further support can be agreed separately.
Get in touchTell me what
Tell me what
you’re working on.
A new environment, an existing system or a delivery process that needs attention. Describe where you are and what you want to change.