Skip to main content

Cloud and Infrastructure Strategy

Put Each Workload Where it Makes Most Sense

Independent guidance for cloud migration, cloud repatriation and multi-cloud decisions

Cloud is not automatically the right destination for every workload. Neither is on premises infrastructure.

  • Cloud expenditure is rising or difficult to forecast
  • Workloads are underperforming in their current environment
  • You lack a clear view of cost by workload, service or team
  • A single provider has become a commercial or operational dependency
  • Data location, security or governance requirements have changed
  • An acquisition, consolidation or growth plan is reshaping the estate
  • Resilience and recovery arrangements need to be reassessed
  • A migration is being proposed without a workload-by-workload business case
Download our service datasheet
Start with your current environment

Move to the cloud

Bring workloads back

Combine environments

Use more than one cloud

  • Linux workloads, applications and technical dependencies
  • Current cloud, on-premises and hosted infrastructure
  • Utilisation, demand patterns and capacity requirements
  • Direct costs and material operational costs
  • Performance and latency requirements
  • Availability, backup and disaster recovery
  • Security, access and data-location requirements
  • Governance, visibility and accountability for consumption
  • Platform and provider dependencies
  • Internal skills, support and operating responsibilities
  • Migration feasibility, sequencing, testing and rollback
  • Target architecture and ongoing optimisation priorities
Book a discovery call

Deliverables

  • A current-state infrastructure and workload summary
  • An agreed set of business and technical decision criteria
  • Workload placement recommendations
  • Cost and risk assumptions for the shortlisted options
  • Identified opportunities for optimisation or consolidation
  • A prioritised roadmap for migration, repatriation or redesign
  • A target operating and support model
GET HELP NOW

What is cloud repatriation?

Cloud repatriation is the movement of workloads or data from public cloud services to private, hosted or on-premises infrastructure. It is sometimes called declouding. It should be considered workload by workload rather than treated as a blanket reversal of cloud strategy.

Does Tiger recommend moving out of the cloud?

Not by default. Some workloads are well suited to public cloud platforms; others may be better placed elsewhere. Tiger assesses the requirements and trade-offs before recommending a direction.

Will repatriation reduce our costs?

It may reduce costs for some workloads, but that cannot be assumed. A sound comparison should consider migration, hardware, facilities, software, support, staffing, resilience and future capacity as well as the current cloud bill.

Does multi-cloud remove vendor lock-in?

Using more than one provider can reduce some dependencies, but it can also add tooling, skills, governance and operational complexity. A multi-cloud model needs a clear reason and an operating approach that can support it.

Can Tiger carry out the migration as well as the assessment?

Tiger can discuss assessment, design, migration and ongoing support requirements. The platforms, technical scope, responsibilities and service coverage are agreed for each engagement.

Do you only work with Linux environments?

Linux is Tiger Computing’s specialist focus. The initial conversation should confirm whether the workloads and wider environment fall within the services Tiger can support.