Managed hosting and practical technical care after launch.
We manage suitable websites and web software in client-owned hosting accounts, with continuous automated checks, daily backups, supported updates and clear incident handling. Choose managed hosting, combined hosting and care, or maintenance on a suitable environment you already control.
Ownership
Client-owned provider accounts
Monitoring
Continuous automated checks
Support
UK business hours, critical cover available
Start with the system, its condition and the access available.
Eligibility is confirmed only after a technical review. Existing and third-party-built systems can be considered, but acceptance is not automatic.
Supported after review
Suitable websites and web software
- Public websites and content-managed sites
- Online stores and booking systems
- Customer portals and dashboards
- Internal tools, dashboards, CRM systems and admin interfaces
- APIs, databases, background jobs and supporting web services
- Supporting systems behind mobile apps
- Approved automations and scheduled processes where their specialist operating requirements are understood
- Suitable systems originally built by another supplier
Remediation, specialist terms or decline
Conditions that need resolving first
- Systems without lawful source, account or provider access
- Obsolete or unsupported runtimes and dependencies
- Environments that cannot be reproduced, backed up, monitored or safely changed
- Systems with unresolved critical vulnerabilities or undocumented data handling
- Infrastructure whose current owner will not provide transfer or administrative access
- High-risk, regulated or unusually sensitive workloads outside the available compliance and operational service
- Third-party SaaS products the client does not control; approved integrations may be maintained, but the provider's platform cannot be hosted or patched by Flippify
Technical review determines eligibility
The review confirms access, ownership, supportability, data risk, deployment, backup and monitoring options. It may lead to onboarding, prior remediation, specialist scope, migration planning or a decision that the system cannot be responsibly supported.
Keep hosting and application care together or separately scoped.
These are enquiry-based service modes, not fixed-price packages. Provider and infrastructure usage is billed directly to the client wherever practical and remains separate from Flippify's service.
Managed Hosting
Hosting operations for an agreed system in a client-owned provider account.
- Deployment and hosting configuration for the agreed system
- Continuous automated availability and basic health checks
- Daily encrypted backups with 30-day retention where the standard model is supported
- Quarterly representative restore testing
- Certificate and selected expiry checks where scoped
- Business-hours incident acknowledgement and hosting support
Application dependency updates, content changes, defect remediation and feature development are not automatically included.
Managed Hosting & Care
A common complete option combining managed hosting with an agreed application-care scope.
- Everything in Managed Hosting
- An agreed monthly maintenance window
- Supported dependency, framework, CMS, plugin or runtime updates as appropriate
- Risk-based urgent handling of critical supported vulnerabilities after testing
- Defect triage and agreed maintenance work
- A proposal-sized monthly allowance for minor content or small change requests
- Maintenance records and an operational review appropriate to the plan
New features, redesigns, major migrations, unsupported-version upgrades, compliance projects and work beyond the allowance are estimated separately.
Care on Your Hosting
Application care on a suitable client-managed hosting environment you already control.
- Agreed monitoring and backup visibility according to available access
- Supported update work, defect triage and support
- A proposal-specific minor-change allowance where requested
- A clear split between application duties and infrastructure retained by the client or another provider
- Safe deployment, access control, backups, monitoring and rollback capabilities confirmed during review
Flippify does not accept responsibility for provider or infrastructure layers outside the agreed access and scope.
Monitor the signals that matter to the agreed system.
Coverage is selected according to system architecture, available access and service mode. Not every check applies to every website or application.
Environments and deployment
Environment and deployment configuration for the agreed system and provider setup.
Availability and application health
Selected availability, endpoint, application-health and error checks appropriate to the service.
Resources and data services
Resource, database, queue, background-job or scheduled-task checks where relevant and accessible.
Backups and retention
Backup-success, failure and retention checks for the data and services included in scope.
Expiry and integration signals
Certificate, domain and selected integration-expiry alerts where provider access permits.
Logs, alerts and records
Centralised logs, failure alerts, routine maintenance records and agreed reporting suited to the system.
Continuous checks, agreed human coverage
Automated checks may run continuously. Human investigation and response follow the service's support hours unless separately agreed out-of-hours critical cover applies.
Selected monitoring has limits
Monitoring does not prove that every business journey, security issue, data error, provider failure or user-visible problem will be detected.
Keep a tested backup baseline without pretending every incident is predictable.
Backup scope is documented system by system, including whether databases, uploaded files, environment configuration and external provider data are covered.
Daily encrypted backups
The standard managed schedule where the system supports this model.
30-day retention
A rolling baseline for covered backup data, subject to the agreed provider setup.
Backup-failure alerts
Selected job failures are surfaced for investigation under the agreed coverage.
Quarterly restore testing
A representative sample is tested each quarter and after material backup changes.
Documented coverage
Know what the backup actually contains.
Restore testing provides evidence for a representative sample; it does not guarantee every backup, external dependency or future restore will succeed.
Recovery boundaries
- Changes since the latest successful backup may not be recoverable on a daily schedule.
- Restore time depends on system size, provider health, data integrity, incident type, access and dependencies.
- The standard baseline is not a guaranteed recovery-point or recovery-time objective.
- More frequent backups, longer retention, cross-region copies, immutable storage or contractual recovery objectives require separately scoped infrastructure and terms.
- Third-party SaaS and provider-managed data may depend on the provider's own backup or export capability.
Plan routine updates and separate maintenance from new product work.
Updates are assessed against support status, compatibility risk, available fixes and test evidence. Not every vulnerability can be patched immediately or without compatibility impact.
Routine model
Monthly maintenance with risk-based urgent handling
- 1Use an agreed monthly maintenance window for supported routine updates.
- 2Review and test updates proportionately before production deployment.
- 3Handle critical supported vulnerabilities urgently according to risk, available fixes, test evidence and service access.
- 4Use rollback or recovery steps where the system and change permit them.
- 5Record material maintenance work.
Routine maintenance
Supported dependency, runtime, framework, CMS, plugin, configuration and certificate work within scope.
Defect triage
Investigation of behaviour that differs from the agreed system; remediation depends on cause and plan scope.
Minor changes
Small content or configuration work within an allowance clearly defined and sized in the proposal.
Feature work
New behaviour, workflows, integrations, redesigns, migrations and substantial changes are estimated separately.
Security projects
Audits, penetration testing, certification, incident forensics, compliance programmes and out-of-scope remediation require separate specialists or scope.
Supported updates are not complete security management
Critical supported vulnerabilities receive urgent risk-based handling after proportionate testing. Unsupported-version upgrades, broad remediation, compliance work and specialist security projects remain separately scoped.
Clear acknowledgement targets, with authority kept within agreed limits.
Standard support window
Monday-Friday, 09:00-17:30 UK time, excluding England and Wales bank holidays.
Critical
Target acknowledgement within 1 business hour
Complete service unavailability, active serious data risk, or a severe security event affecting the managed system.
High impact
Target acknowledgement within 4 business hours
Major degradation or an unavailable core function affecting multiple users.
Normal
Target acknowledgement within 1 business day
Non-urgent defects, questions, and maintenance requests.
Acknowledgement targets, not resolution promises
These are acknowledgement targets during the standard support window, not guaranteed resolution times or a contractual SLA. Investigation and recovery depend on cause, access, provider response, system state, available fixes, and client decisions. No service credits are offered through this standard model.
Incident process
Stabilise first, without bypassing material decisions.
- 01Detect or receive the report.
- 02Confirm scope and severity.
- 03Acknowledge and identify the responsible parties.
- 04Take reversible stabilising actions within pre-agreed authority.
- 05Seek client approval for material production changes or new third-party costs.
- 06Restore service or reduce impact where possible.
- 07Communicate status at a frequency appropriate to severity.
- 08Record the incident and review significant events.
Out-of-hours critical cover
- Available only for eligible systems under a separately agreed add-on.
- The coverage window, contact route, severity definition, response target, escalation contacts, and exclusions are set in the service agreement.
- Routine requests and non-critical defects remain in standard business hours.
Third-party provider incidents remain subject to provider status, access, and response. Pre-agreed authority covers only documented, reversible stabilisation; material production changes and new third-party costs require client approval.
Your accounts stay yours. Our access stays limited to the service.
Hosting-provider accounts are client-owned and provider usage is billed directly to the client wherever practical. Flippify receives only the administrative access required for the agreed work.
Flippify may manage within scope
Agreed technical operation
- Deployment and environment configuration within the agreed scope
- Monitoring and alert triage
- Backup checks and scheduled restore tests
- Supported maintenance windows and updates
- Incident investigation and pre-agreed reversible stabilisation
- Maintenance records and operational communication
The client retains or provides
Ownership, decisions, and timely access
- Ownership and direct billing for provider, domain, repository, and relevant third-party accounts
- A current business owner, technical contact, and escalation contact
- Timely approval for material changes, downtime, data restoration, or new costs
- Legal, privacy, regulatory, content, licensing, and data-retention decisions
- Accurate user, traffic, business-criticality, and data-sensitivity information
- Internal access control and staff account management outside Flippify's agreed duties
- Provider terms, licences, transaction costs, and service limitations
Named access, least privilege, clean removal
Access should use named accounts, least privilege, and a documented removal process. Domains, DNS-provider accounts, source repositories, production services, and third-party accounts remain client-owned or are transferred as agreed. Flippify access must be removable without taking ownership of the client system away from the client.
Client ownership does not remove provider dependency or guarantee portability between incompatible services. Provider terms, licences, limits, fees, and availability still apply.
Keep sensitive access out of the enquiry
Do not send production credentials, passwords, API secrets, private keys, production exports, or backup archives through the public contact form. Secure access arrangements are agreed during onboarding.
Review an inherited system before accepting responsibility for it.
Suitable systems built by another supplier can be considered, but account access, technical condition, recovery evidence, and operational risk must be understood first.
What the technical review covers
- Source rights and repository access
- Provider, account, domain, DNS, and certificate ownership
- A reproducible build and deployment process
- Runtime, framework, CMS, plugin, and dependency support
- Hosting architecture, regions, environments, and provider limits
- Database, storage, queues, jobs, integrations, and external services
- Existing backups, retention, restore evidence, monitoring, logs, and incident history
- Known vulnerabilities, defects, outages, renewals, and contracts
- Data sensitivity, user access, business criticality, and operational contacts
- Migration windows, DNS changes, rollback options, and incumbent-provider exit constraints
Review before commitment
Takeover is conditional, not automatic.
Acceptance, a zero-downtime migration, preservation of provider-specific features, a fixed onboarding cost, and a migration date cannot be promised before review.
Start with system and ownership details only. Do not send credentials, private keys, production exports, backup files, or other sensitive artefacts through the public form.
Request a takeover reviewThe review can lead to five responsible outcomes
Accept and onboard
Bring the current system into an agreed hosting or care service.
Stabilise or document
Address priority gaps before ongoing care begins.
Upgrade selected parts
Rebuild infrastructure or deployment processes that cannot be supported safely.
Plan a migration
Move the system through a separately scoped and reviewed plan.
Decline or refer
Recommend a specialist when the risks cannot be responsibly supported.
Validate the operating model before support begins.
Initial review and straightforward setup may take 1-3 weeks. Migrations, remediation, unsupported-version upgrades, complex data, DNS dependencies, or incumbent-provider constraints are estimated separately and can extend onboarding.
- 01Eligibility and technical review
- 02Proposal, service mode, access, responsibility, and escalation agreement
- 03Remediation, migration, or managed setup where required
- 04Monitoring, backup, restore, deployment, and update validation
- 05Go-live and support handoff
- 06Ongoing monitoring, maintenance windows, incident handling, and service reviews
The 1-3 week guidance is not a guaranteed migration or onboarding time. Ongoing operation starts only after review, access, responsibilities, and escalation routes have been agreed and the required validation is complete.
What we need from you
Ownership, operational context, and a safe access plan
- Current system, technology, environments, and known dependencies
- Provider, domain, DNS, repository, and third-party account ownership
- A secure plan for the administrative access the service requires
- Business owner, technical contact, and incident escalation contacts
- Approved maintenance, migration, downtime, and change windows
- Data sensitivity, user levels, traffic, and business criticality
- Current provider contracts, renewal dates, and incumbent exit constraints
Sensitive credentials and production artefacts are exchanged only through an agreed secure onboarding process, never through the public contact form.
Price the real operating burden, then keep the exit controlled.
Pricing is enquiry-based because system condition, support coverage, recovery needs, and provider architecture change the work. No public package includes unlimited usage, maintenance, changes, or third-party costs.
What shapes the estimate
- Number and complexity of systems and environments
- Provider, traffic, storage, database, bandwidth, and regional needs
- Backup frequency, retention, restore testing, and recovery requirements
- Monitoring depth and scheduled-process coverage
- Update burden and inherited technical condition
- Standard or out-of-hours support coverage
- Monthly change allowance
- Migration, onboarding, remediation, and reporting needs
- Third-party provider and licence charges
Commercial model
- Provider and third-party usage costs are paid directly by the client where practical.
- Onboarding, migration, or remediation may be quoted separately.
- Ongoing service is rolling monthly after onboarding with 30 days' notice unless a proposal states otherwise.
Late payment, suspension, exceptional usage, liability, and other contractual provisions belong in the service agreement and legally reviewed Hosting Terms, not in this marketing summary.
A controlled exit
Client-owned provider accounts and data remain with the client, subject to provider terms and unpaid provider charges. A standard cancellation does not include an unscoped migration to another supplier.
- 01Agree the transition date and responsibilities.
- 02Provide agreed operational records and account or access information already under Flippify's control.
- 03Support additional migration work under a separate estimate where required.
- 04Remove Flippify access after transition.
- 05Retain Flippify-controlled backups for 30 days after service end, then securely delete them unless law or an agreed exception requires otherwise.
Launch dependency
Hosting Terms are still a separate work item
The separate /hosting-terms page requires follow-up specification, implementation, and legal review before launch. This service page is not contractual terms. The signed proposal, service agreement, and legally reviewed Hosting Terms will define delivery, including any proposal-specific variation to rolling service, notice, and post-service backup handling.
Use hosting care for operation, not as a substitute for a new project.
Hosting and application care can be combined or separated. When the primary need is design, substantial development, mobile release work, or specialist automation, start with the relevant service instead.
Operational answers before you agree ongoing care.
This is a service overview. The future signed proposal, service agreement, and legally reviewed Hosting Terms will govern delivery.
Show us the system you need to keep available, recoverable and maintainable.
Share enough non-sensitive context for us to assess eligibility, operating scope, support coverage, and the right service mode.
Do not include passwords, API secrets, private keys, production exports, or backup files in the contact form.
Useful details to include
- Current URL and system type
- Technology and provider, if known
- Whether Flippify built it
- Number of environments and broad traffic or user level
- Data sensitivity and business criticality
- Existing monitoring, backups, update process, and current support problem
- Desired support hours
- Planned launch, migration, or incumbent-contract date