TrueLogic.cloud

Cloud and DevOps that fit the team you actually have

Automated pipelines, infrastructure in version control, security checks on every commit, and monitoring that only wakes someone when it should. We migrate you, then run it, or hand it over documented well enough that you never need to call.

The problem

Delivery slows down long before anyone calls it a crisis

Deployments start needing a specific person. Staging stops matching production. An outage gets fixed but nobody writes down how, so it happens again in six weeks. Security findings arrive the week before launch, when changing anything is expensive.

None of it is dramatic on its own. Together it quietly doubles how long everything takes.

Signs it's time to call someone

  • Deploys happen out of hours because they're risky
  • Only one person can release, and they're on holiday
  • Servers were configured by hand and nobody documented it
  • You find out about outages from customers
  • Cloud spend rises every month and nobody can say why
  • Security review is a phase, not a habit

Our practice

Eight services, available together or one at a time

Plenty of teams start with a pipeline audit and go from there.

01

DevSecOps implementation

Security checks move into the pipeline instead of waiting for an audit. Dependency scanning, container scanning, secret detection, IaC policy checks and signed builds. Problems surface on the pull request, not in production.

02

CI/CD pipeline automation

Build, test, approve, deploy and roll back without anyone SSH-ing into a box at midnight. We build pipelines in GitHub Actions, GitLab CI, Jenkins or Azure DevOps, whichever your team already knows.

03

Infrastructure as code

Your environments become Terraform, Pulumi or CloudFormation in version control. Staging matches production, changes get reviewed like code, and rebuilding a region takes an afternoon instead of a fortnight.

04

Kubernetes consulting

Cluster design, workload migration, autoscaling, ingress, RBAC and cost control on EKS, AKS, GKE or bare metal. Including the honest conversation about whether you need Kubernetes at all.

05

Monitoring and observability

Dashboards, logs, metrics, traces and alerts that page a human only when a human is needed. Built on Prometheus and Grafana, the ELK stack, Datadog or CloudWatch.

06

SRE and reliability engineering

Error budgets, SLOs, runbooks, on-call rotations and blameless post-incident reviews. The goal is fewer repeat incidents, not a thicker incident log.

07

GitOps implementation

Git becomes the single source of truth for infrastructure and applications. Argo CD or Flux reconciles the cluster to the repo, so every change is reviewed, auditable and revertible with one commit.

08

Managed DevOps services

An ongoing DevOps team without the hiring. We look after pipelines, cloud infrastructure, monitoring, patching, incidents and cost on a monthly retainer you can cancel.

Our working toolchain

AWSMicrosoft AzureGoogle CloudTerraformKubernetesDockerHelmArgo CDGitHub ActionsGitLab CIJenkinsAnsiblePrometheusGrafanaELK StackSonarQubeTrivyHashiCorp VaultCloudflarecPanel / WHMWordPressNext.jsLaravelShopify

Cloud migration

Moving to AWS, Azure or Google Cloud

Most migration pain comes from skipping the assessment. We map what you have, decide what's worth moving, rebuild it properly in the new environment, and cut over when nobody's watching.

Readiness assessment

An inventory of applications, dependencies, data volumes and licences, with a rehost, replatform, refactor or retire decision for each one, plus a cost model for the target state.

Landing zone design

Accounts, networking, identity, tagging, logging and guardrails set up correctly before the first workload arrives, so you're not retrofitting governance to a live estate.

Application migration

Moved in waves, least risky first, each one tested against real traffic before cutover. Rollback stays available until you're confident.

Database migration

Replication, consistency checks and a rehearsed cutover for MySQL, PostgreSQL, SQL Server, MongoDB and the rest. The rehearsal is not optional.

Disaster recovery

Backups that have been restored at least once, a documented recovery objective, and a failover path someone has actually tested.

Cost optimisation

Rightsizing, autoscaling, storage tiering, reserved instances and savings plans, reviewed a month after landing, when the real usage data exists.

Smaller moves

Coming off shared hosting or a single server?

Not every migration is an enterprise programme. A lot of businesses are on one ageing VPS, a cPanel account that has outgrown its plan, or a server sitting in an office cupboard.

That move is smaller, cheaper and quicker, usually a fixed-price job measured in days. We handle the DNS, the SSL, the email records and the bit everyone forgets about until the phones stop working.

Included in a small migration

  • Full backup taken and verified before anything moves
  • Site, database and files copied to the new environment
  • Email and DNS records mapped across correctly
  • SSL certificates reissued and tested
  • Cutover scheduled for your quietest hours
  • Old environment left running until you sign off

After the move

Managed hosting, with a human attached

Managed cPanel and WHM hosting, or a properly configured environment inside your own cloud account. Either way, patching, backups and monitoring are ours to worry about.

Managed cPanel / WHM

Familiar control panel, one-click staging, email accounts, LiteSpeed caching and a support conversation that doesn't start with a ticket number.

Cloud hosting in your account

We architect and manage the environment inside your own AWS, Azure or Google Cloud account. You hold the billing relationship and the keys.

WordPress hosting

Tuned for WordPress specifically: object caching, staging environments, core and plugin updates applied and tested rather than left on auto.

Security and SSL

Free auto-renewing SSL, a web application firewall, malware scanning, brute-force protection and hardened server configuration as standard.

Monitoring and uptime

Minute-by-minute uptime checks, resource alerting and a monthly report. We usually know before you do.

Backups and recovery

Daily off-server backups kept for 30 days, restore on request, and a documented recovery process that has been rehearsed.

Engagement

How a cloud or DevOps project runs

Assess what's there

We review your delivery process, cloud accounts, pipelines, monitoring and access model, and identify where the delays, risks and manual effort actually come from. It's rarely where people assume.

Current-state assessment · risk register · prioritised gaps

Agree a roadmap

A plan matched to your team size and budget, sequenced so the highest-value fixes land first. We're explicit about what we're deliberately not doing yet, and why.

Roadmap · tooling recommendation · fixed quote · timeline

Migrate and automate

Workloads move in waves with rollback available throughout. CI/CD pipelines, infrastructure as code, environment parity and security scanning land alongside them.

Working pipelines · Terraform modules · scanning in CI · tested rollback

Add observability and reliability practice

Dashboards, alert rules tuned to reduce noise, runbooks, SLOs and an incident process your team can follow at three in the morning without improvising.

Grafana dashboards · alert policy · runbooks · on-call rota

Run it, or hand it over

Either we stay on as your managed team, or we train your engineers and leave documentation good enough that they don't need to call us.

Managed retainer, or full handover with training

Cloud & DevOps FAQ

Common questions about DevOps, migration and hosting

What are DevOps consulting services?

DevOps consulting helps a business improve how software gets built, tested, deployed, monitored and supported. In practice that means auditing what you have now, then implementing CI/CD pipelines, infrastructure as code, monitoring, security checks and incident processes that fit your team's size and skills.

What is DevSecOps, and how is it different from DevOps?

DevSecOps is DevOps with security checks embedded in the delivery pipeline instead of performed as a separate audit at the end. Dependency scanning, container image scanning, secret detection, infrastructure policy checks and signed builds all run automatically on every change, so issues appear on the pull request while they are still cheap to fix.

Do we need DevOps if we're not a software company?

If you depend on a website, a customer portal, an internal system or any cloud infrastructure, the same practices apply. The value is fewer outages, faster fixes and less time spent on manual server work. That matters whether you sell software or plumbing supplies.

Do we actually need Kubernetes?

Often not. Kubernetes is excellent for teams running many services that scale independently, and expensive overhead for a team running three containers. We'll say so during scoping if a managed container service or plain virtual machines would serve you better.

How long does a cloud migration take?

A single application typically moves in two to six weeks including testing. A full estate is planned in waves, with the least risky workloads first, and can run over several months. The assessment phase gives you a realistic schedule before you commit to anything.

Will our systems go down during the migration?

For most workloads, no. We replicate to the new environment, run both in parallel, test against real traffic patterns, then cut over during your quietest window with the old environment still standing by. Some legacy databases genuinely need a maintenance window, and we tell you that upfront rather than discovering it live.

Which cloud should we choose?

It depends on your workloads, your team's existing skills, your compliance obligations and any credits you already hold. AWS has the broadest service catalogue, Azure integrates most neatly with Microsoft estates, and Google Cloud is strong on data and Kubernetes. We have no reseller incentive pushing us either way.

Is the cloud actually cheaper than our servers?

Not automatically. A straight lift-and-shift often costs more than the hardware it replaced. Savings come from rightsizing, autoscaling, reserved capacity and switching to managed services, which is why cost optimisation is part of the project rather than an upsell afterwards.

What does managed DevOps and hosting include?

A monthly retainer covering pipeline maintenance, cloud infrastructure management, monitoring and alerting, patching, incident response, release support and cost review. On the hosting side it adds daily off-server backups, SSL, a web application firewall and uptime checks every 60 seconds.

Are we locked in?

No. There's no long contract, and everything lives in accounts under your name: repositories, cloud accounts, domains. If you leave we hand over a complete backup, the documentation and help pointing DNS wherever you're going.

Start with a pipeline audit

A week of our time, a written report, and a clear view of what's slowing your delivery down. No obligation to do anything with it.