Managed Linux hosting, migration and support

Managed Linux hosting, migration and support.

Open technology. Expertly managed.

Thintech designs, migrates, secures and operates business-critical Linux environments across UK hosting, private cloud, public cloud and third-party infrastructure. One accountable partner for the platform, security, monitoring, backup and ongoing support agreed around your workload.

I need to discuss Linux support

New enquiries are assessed before support begins. Existing contracted customers should use their agreed service channel.

Cloud and data-centre infrastructure representing flexible managed Linux hosting
infrastructure and managed-service expertise
Since 2006
location and infrastructure choice
UK hosting options
coverage shaped around business impact
24x7 monitoring available
one connected service
Migration + hosting + operations

Freedom needs ownership

Linux gives you flexibility. Who takes responsibility?

Think Open is for organisations whose Linux estate has become too important to rely on fragmented suppliers, unsupported platforms or undocumented knowledge.

A critical platform is out of support

CentOS or another operating system has reached end of life, but applications, runtimes and dependencies make a safe replacement more complex than an in-place upgrade.

Linux knowledge depends on one person

Operational history, privileged access and application context sit with one specialist whose availability has become a business risk.

Several suppliers own fragments of the service

The hosting provider supplies a VM, the developer owns the application and nobody coordinates the operating system, network, backup and incident path.

Monitoring alerts without resolving ownership

Signals exist, but the organisation still has to decide who investigates, who can change the platform and who coordinates the response.

Backups exist, but recovery is uncertain

Jobs may show as successful while restore ownership, application validation, recovery priorities and testing remain unclear.

A migration is blocked by application risk

Legacy PHP, databases, libraries, control panels, certificates and integrations may not behave the same way on a modern target platform.

Security administration has become inconsistent

Patching, SSH keys, privileged accounts, firewall changes, certificates and vulnerability work are handled through disconnected processes.

The platform has become too important to run informally

An outage would affect customers, transactions, revenue or regulated operations, yet documentation and operational governance have not kept pace.

Think Open brings the infrastructure, operating system, security, monitoring, backup and support model under clear operational ownership.

One provider. Clear ownership.

Open infrastructure without fragmented responsibility.

Your environment may depend on several technologies and suppliers. Your support model should not depend on your team coordinating all of them during an incident.

Design

Create a supportable target around the applications, business impact, recovery objectives and operating model.

  • Architecture and capacity
  • Security and resilience
  • Network, backup and hosting model

Migrate

Move in controlled waves after dependencies and compatibility are understood, with acceptance gates and rollback.

  • Discovery and dependency mapping
  • Compatibility and remediation plan
  • Testing, cutover and hypercare

Host

Use the infrastructure model that fits the workload without tying operational responsibility to one provider.

  • UK private-cloud options
  • Dedicated or virtual servers
  • Public cloud and third-party infrastructure

Operate

Turn server administration into an agreed managed service with monitoring, maintenance, security and governance.

  • Linux administration and patching
  • Backup, capacity and incident response
  • Documentation, reporting and review

Hosting that fits the workload

You choose the right platform. Thintech provides the operational control.

Think Open can front the complete service or work with approved infrastructure providers in the background. Final location, service levels and supplier responsibilities are confirmed by design.

Thintech-managed UK hosting

Private-cloud, data-centre, dedicated and virtual Linux options can be designed around the workload and agreed data-location requirements.

  • Scalable compute, memory and storage
  • Managed backup and firewall options
  • DDoS, secure access and resilience options

Public cloud

Thintech can assess and operate approved public-cloud Linux services where the platform, access, skills and responsibility boundary are agreed.

  • Cloud and cloud-to-cloud migration
  • Configuration, capacity and cost review
  • Monitoring, security, backup and recovery

Your infrastructure or provider

Keep customer-owned, colocated or third-party hosting while Thintech manages the agreed operating system, controls and service path.

  • Customer premises and virtualisation
  • Existing hosting and private cloud
  • Hybrid and multi-provider environments

Broad expertise without stack lock-in

Open does not mean unsupported.

Distribution, runtime, control panel and provider choices remain flexible, while supportability and responsibility stay explicit.

Linux distributions

  • Ubuntu
  • Red Hat Enterprise Linux
  • AlmaLinux
  • Rocky Linux
  • Debian
  • CentOS migration

Supported versions and any other enterprise distribution are confirmed after assessment.

Hosting and control panels

  • cPanel
  • WHM
  • Plesk
  • Dedicated and virtual servers
  • Private cloud
  • Specialist hosting platforms

Control-panel version, licensing and migration compatibility are assessed before scope is agreed.

Web and application platforms

  • Apache
  • NGINX
  • PHP
  • Common database platforms
  • Web and SaaS platforms
  • APIs and middleware

Application-code support, vendor defects and redevelopment are not implied by platform management.

Infrastructure and operations

  • Physical and virtual platforms
  • Cloud and data-centre services
  • Networking and firewalls
  • Backup and recovery
  • Monitoring and logging
  • DNS and certificates

Every asset, service, tool and activity must be expressly included in the service schedule.

Move with control. Operate with confidence.

A Linux migration is an application and service migration.

Copying a server is not a migration plan. Think Open establishes what the platform does, what depends on it, how it will be accepted and what happens if the cutover cannot proceed safely.

  1. Discover

    Inventory servers, applications, owners, versions, data flows, dependencies, documentation and operating constraints.

  2. Assess

    Build a compatibility and remediation view across operating systems, runtimes, databases, control panels, recovery and external services.

  3. Design and build

    Create supported targets with agreed sizing, networking, security baseline, access, monitoring, backup and rollback controls.

  4. Migrate

    Move in dependency-led waves, synchronise data where appropriate, preserve parallel operation and complete technical and customer testing.

  5. Cut over

    Use approved change windows, final synchronisation, DNS, certificate and firewall actions, acceptance checks and a defined backout decision.

  6. Stabilise

    Provide agreed hypercare, monitor behaviour, resolve migration defects, update runbooks and retire legacy services through controlled change.

End-of-life platform migration

Still running CentOS or another unsupported platform?

A supported target must work with the complete application stack. Thintech assesses runtimes, databases, control panels, libraries, integrations, recovery and business constraints before recommending the route.

Plan your CentOS migrationTarget distribution, compatibility work, delivery waves and risk decisions are confirmed after discovery.

The platform stays open. The responsibility does not.

Operate. Protect. Recover.

Monitoring is only one part of managed operations. Scope must also define authority, engineering response, maintenance, security activity, recovery evidence and the owner of each next step.

Operate

Maintain the agreed Linux service, performance and operational path.

  • Monitoring and critical-incident routes
  • Operating-system administration and patch scheduling
  • Performance, capacity, certificates, DNS and firewall
  • Users, privileges, SSH keys and control panels
  • Reporting and service review where included

Protect

Apply security controls that fit the platform and the customer's risk decisions.

  • Supported builds and CIS-aligned hardening where agreed
  • Security patching and vulnerability attention
  • Least privilege, named access and MFA where supported
  • Malware and vulnerability scanning options
  • Centralised logging, alerting and controlled change

Recover

Make protection, ownership and recovery actions visible before an incident demands them.

  • Backup monitoring and exception review
  • Agreed restore testing and application validation
  • Recovery runbooks and escalation
  • Disaster-recovery and high-availability options
  • Post-incident learning and improvement

Think Open manages agreed controls for the Linux platform. It is not automatically a penetration test, source-code audit, PCI DSS assessment or formal compliance certification.

Governed, documented and visible

Turn server administration into a managed service.

Shared records and repeatable runbooks reduce key-person dependency, make responsibility visible and give service reviews evidence to act upon. The exact outputs depend on onboarding scope.

Indicative operating models

The right level of control for each workload.

These three shapes help frame a scoping conversation; they are not published service entitlements. Final names, support hours, response commitments, inclusions, recovery testing and governance are confirmed in Thintech's approved service catalogue and each customer schedule.

Think Open Essential

Best suited to: Smaller Linux workloads

A proposed foundation for organisations that need repeatable oversight and an agreed support route.

  • Monitoring
  • Patch management
  • Backup oversight
  • Defined support route and escalation
  • Basic Linux administration
  • Service documentation
Discuss this operating modelIllustrative only. Final scope is contractual.

Think Open Managed

Best suited to: Business-critical platforms

A proposed managed model for day-to-day Linux operations, security activity and critical-incident coordination.

  • Full Linux administration
  • 24x7 monitoring option
  • Agreed critical-incident response
  • Security and patch management
  • Backup, DNS, certificate and firewall management
  • Performance, capacity and service review
Discuss this operating modelIllustrative only. Final scope is contractual.

Think Open Critical

Best suited to: Revenue-generating or regulated systems

A proposed enhanced model for workloads needing greater recovery evidence, resilience attention and governance.

  • Enhanced response options
  • Dedicated service governance option
  • Vulnerability management
  • Agreed recovery testing
  • Resilience and high-availability review
  • Risk, capacity and improvement tracking
Discuss this operating modelIllustrative only. Final scope is contractual.

Commercial clarity

Major change is a project, not a support ticket.

Separating recurring operations from migration, modernisation and application remediation gives complex change the discovery, design, testing and governance it needs. It also keeps the recurring service focused and commercially clear.

Clear boundaries across infrastructure and applications

One accountable path does not mean one party owns everything.

The proposal and responsibility matrix make operational ownership, application ownership and joint decisions explicit before service acceptance.

Thintech responsibility

Where expressly included in the selected service:

  • Infrastructure and operating system
  • Monitoring and security patching
  • Backup oversight
  • Firewall, DNS, certificates and access
  • Control panel and database-platform administration
  • Incident response and service documentation

Application-owner responsibility

Unless separately agreed:

  • Application functionality and source code
  • Application defects and redevelopment
  • Vendor licensing and support
  • Business acceptance testing
  • Application content, data quality and releases
  • Application-specific configuration

Shared responsibility

Coordinated through the agreed change and service model:

  • Compatibility assessment
  • Migration and recovery testing
  • Performance troubleshooting
  • Security remediation
  • Cutover and rollback decisions
  • Vendor escalation and change approval

Understand before the incident

A managed service starts with controlled onboarding.

An unfamiliar estate does not become supportable at contract signature. Onboarding depth depends on its size, complexity, risk, evidence and supplier cooperation.

  1. Discover

    Confirm services, stakeholders, suppliers and business impact.

  2. Inventory

    Build the agreed server, application and service baseline.

  3. Map

    Record dependencies, data flows and support relationships.

  4. Review risk

    Identify unsupported components, known issues and urgent actions.

  5. Configure access

    Establish named, least-privilege operational access.

  6. Deploy monitoring

    Agree assets, signals, thresholds and the response path.

  7. Validate backup

    Confirm protection scope, exceptions and testing requirements.

  8. Document

    Create or improve configuration records, runbooks and ownership.

  9. Test escalation

    Validate contacts, priorities, supplier routes and authority.

  10. Accept service

    Agree remaining risks and move the defined scope into operation.

Grounded in delivery experience

A method shaped by real migration and managed-infrastructure work.

Think Open brings repeatable discovery, compatibility assessment, controlled migration and operational handover into one service model, while keeping project change and application responsibility explicit.

Anonymised delivery pattern

Replacing an end-of-life hosting estate

Thintech delivery material demonstrates structured discovery, supported Linux target design, dependency-led migration waves, testing, rollback, hypercare and a transition into managed infrastructure support.

The value is the delivery discipline: understand dependencies, control change, validate the outcome and leave a supportable service behind.

Anonymised delivery pattern

Modernising a complex hosted application estate

Thintech has scoped migrations involving legacy operating systems, control panels, web runtimes, databases, provider coordination, parallel running, DNS and firewall cutover, backup and ongoing operations.

Application compatibility and remediation are separated from infrastructure migration so risk, testing, ownership and cost remain explicit.

Why Thintech

Open technology. One accountable partner.

Thintech does not simply move a server and wish you luck. We establish how the platform works, manage migration risk and create the operating controls needed afterwards.

Infrastructure expertise since 2006

Experience across virtualisation, hosting, consultancy and managed operations for business-critical services.

Migration discipline

Discovery, dependency mapping, compatibility assessment, phased waves, testing, acceptance, rollback and hypercare.

Real operational ownership

Monitoring, administration, security, backup oversight, documentation, escalation and service governance within scope.

Infrastructure freedom

UK hosting options and management across customer, private-cloud, public-cloud and third-party environments.

Support beyond the server

Networking, firewalls, DDoS options, access, DNS, certificates, control panels, databases and recovery can be coordinated.

Certified information security management

Thintech operates an ISO 27001:2022-certified ISMS; customer compliance and service scope remain separate questions.

A natural part of the Thintech portfolio

The right service for the responsibility you need.

Explore with FiNN

Start with the question you already have.

FiNN can explain the public Think Open proposition and help you prepare for a conversation. Never share credentials, private keys, configuration exports, database content or customer-sensitive information.

Cover of the Think Open managed Linux service descriptor

Six-page service descriptor

Take the Think Open overview with you.

The supplied service descriptor summarises the Design, Migrate, Host and Operate model, migration lifecycle, managed operations and proposed service shapes. The customer proposal and service schedule define the final scope and commitments.

Download the Think Open descriptorPDF, 6 pages, approximately 3.5 MB. Service levels and inclusions remain subject to the agreed schedule.

Questions before we take responsibility

Think Open FAQs

What is Think Open?

Think Open is Thintech's managed Linux hosting, migration and support service. It brings design, migration, infrastructure, Linux administration, security controls, monitoring, backup oversight, documentation and support into one agreed operating model.

Is Think Open a hosting service or a support service?

It can be either or both. Thintech can provide an agreed hosting platform, manage Linux services on infrastructure supplied by another provider, deliver a migration project and then operate the resulting environment. The proposal states exactly which responsibilities apply.

Can Thintech manage servers hosted by another provider?

Yes, where discovery confirms suitable platform access, technical compatibility, supplier cooperation and a workable responsibility boundary. Thintech can act as the customer-facing operating partner while coordinating the underlying provider within the agreed scope.

Which Linux distributions do you support?

Think Open is intended for supported enterprise platforms including Ubuntu, Red Hat Enterprise Linux, AlmaLinux, Rocky Linux and Debian, plus CentOS migration. Exact versions and other distributions require assessment before Thintech confirms support.

Can you migrate CentOS 7?

Yes, subject to discovery and an agreed project. Thintech assesses applications, runtimes, databases, control panels, libraries, integrations and recovery needs before recommending the target distribution and migration sequence.

Can you migrate us to AlmaLinux or Rocky Linux?

Those can be considered alongside Red Hat Enterprise Linux, Ubuntu or another supported target. The correct choice depends on application and control-panel compatibility, vendor support, lifecycle, operational requirements and customer preference.

Do you support Ubuntu and Red Hat Enterprise Linux?

Thintech can support agreed Ubuntu and Red Hat Enterprise Linux workloads, subject to supported versions, licensing or subscriptions, application compatibility, access and the activities included in the service schedule.

Can you support cPanel and Plesk?

cPanel, WHM and Plesk assessment, migration and administration can be included where Thintech confirms the version, licensing, target platform, application estate and responsibility boundary. Application-code remediation is separate unless expressly scoped.

Can Thintech host our Linux servers in the UK?

Thintech can offer UK hosting and private-cloud options. Data location, facility, infrastructure, resilience, backup, connectivity and service commitments are confirmed in the customer design and contract rather than assumed from this page.

Can you manage Linux servers in Azure or AWS?

Public-cloud management can be considered, but Thintech confirms current platform capability, access, supported services, tooling and responsibility after discovery. No provider or service is universally included by this page.

Do you provide 24x7 monitoring?

24x7 monitoring can be included for agreed production assets. Monitoring scope, signals, alert handling, priorities, response path and customer responsibilities are documented in the service schedule.

Does monitoring include remediation?

Not automatically. Monitoring, alert acknowledgement, investigation, engineering response, remediation and resolution are separate commitments. The selected service defines what Thintech is authorised and resourced to do after an alert.

Do you provide critical incident response?

Agreed critical-incident response can be included for contracted services and priorities. It does not imply immediate support for an unknown environment or guaranteed resolution, and non-contracted enquiries follow the normal scoping route.

Is application support included?

Operating-system and infrastructure management does not automatically include application functionality, source code, defects, releases or vendor support. Application-platform administration and troubleshooting can be included where responsibilities are explicit.

Are PHP upgrades included in the support fee?

Major PHP upgrade, compatibility remediation, framework change and application redevelopment are project work unless a current service schedule expressly includes a defined activity. This protects both parties from treating material transformation as routine support.

Can you migrate legacy PHP applications?

Thintech can assess the platform, runtime and dependencies, build target environments and coordinate migration and testing. Changes to source code, frameworks or application behaviour require an agreed application owner or separately scoped remediation capability.

Can you manage databases?

Database-platform administration, monitoring, backup and resilience can be considered where the platform and responsibility are supported and expressly included. Data ownership, application behaviour, specialist tuning and vendor responsibilities remain defined separately.

Can you provide DDoS protection?

DDoS-protected connectivity or mitigation options can be designed through approved infrastructure providers. Coverage, limitations, escalation and commercial terms depend on the selected service and provider.

How do you manage SSH access?

Think Open can use named access, least privilege, controlled key ownership, logging, review and MFA or privileged-access controls where technically supported. The final access model reflects customer policy and the platforms in scope.

Do you test backups?

Restore testing can be included at an agreed frequency and scope. Backup monitoring alone cannot guarantee that every restore or complete application recovery will succeed; customer and application-owner validation may also be required.

Can you design disaster recovery or high availability?

Yes, as separately agreed design and delivery work. Recovery objectives, application architecture, data consistency, provider capability, testing and budget must be understood before a solution or commitment is made.

How long does a Linux migration take?

Duration depends on estate size, documentation, dependencies, compatibility, data, application remediation, provider lead times, testing, maintenance windows and customer acceptance. Thintech produces a plan after discovery instead of publishing a universal duration.

Can migrations be completed with zero downtime?

Thintech does not promise zero downtime without evidence and an agreed design. Parallel running, synchronisation and phased cutover can reduce disruption, but each application's consistency, DNS, integrations and acceptance requirements determine the achievable approach.

What happens if an application is not compatible with the target platform?

Thintech records the dependency and presents options such as a different supported target, an isolated runtime, phased remediation, a temporary control with explicit risk acceptance or a separate application work package. The customer approves the chosen route.

Can we keep our existing hosting provider?

Yes, where the provider can supply the required access, support boundary, infrastructure and cooperation. Think Open is not dependent on moving every workload to Thintech hosting.

How does Think Open differ from Think Response?

Think Response provides defined specialist technical support. Think Open adds a Linux-specific hosting, migration and managed-operations model with continuing responsibility for the services and activities agreed in the service schedule.

How does Think Open connect to Think Integrated?

Think Integrated can operate the wider customer IT environment. Think Open is the focused Linux and open-source infrastructure capability and can sit within, alongside or separately from that broader managed service.

What happens during onboarding?

Onboarding can include service discovery, inventory, dependency and risk review, access configuration, monitoring, backup validation, documentation, escalation testing and formal service acceptance. Depth and timescale depend on the estate and agreed service.

Ready to take control of your Linux estate?

Discuss your environment with Thintech.

Whether you are replacing an unsupported CentOS platform, moving away from unmanaged hosting or looking for one partner to operate business-critical Linux, the first step is to understand the estate and the responsibility you need.

  • No credentials or sensitive exports through this form
  • Migration and application remediation scoped separately
  • Support coverage and responsibilities agreed before acceptance
  • Existing customers continue to use their contracted support route

Fields marked are required.

Do not include passwords, private keys, SSH or API keys, security tokens, database exports or backups, sensitive configuration, customer data or personal data beyond the contact details requested above. See our Privacy Policy.

Trusted for regulated environments

Security and procurement assurance

Built for mid-market organisations where governance, resilience and accountable delivery matter.

ISO 27001:2022 certifiedInformation Security Management SystemCertificate 27083-ISMS-001 - View PDF
Crown Commercial Service supplierSupporting compliant public-sector procurementAssurance for regulated buyers