CloudFirst

Yes. Performive rebranded as CloudFirst, and performive.com now resolves to cloudfirst.host. The business, the team and the service catalogue carried over — the same managed cloud, ransomware recovery and data-protection portfolio, built on VMware and Veeam, delivered from the same locations. Most of the product collateral still carries the Performive name, which is normal in the first year after a rename.

Three things that overlap: managed private and hybrid cloud, data resiliency, and the security services around them. In practice that means running your VMware or OpenStack environment as a managed service, holding immutable Veeam backups of it, and being able to bring the whole estate back after a ransomware event within a recovery time you agreed in advance. Established in 2005, headquartered in Marietta, Georgia, with delivery across the United States, Canada, the UK and Germany.

Both are ransomware recovery, and the difference is what happens to the compute before a disaster. Standby Recover uses shared, multi-tenant resources that only spin up when a failover is triggered — cheaper to run, with a best-effort RTO and RPO. Reserved Recover holds dedicated capacity ready, which is what allows a contractual RTO and RPO. Most buyers put a handful of systems on Reserved and everything else on Standby, rather than choosing one tier for the whole estate.

Yes, and this is the unusual part of the portfolio. Virtualisation, hosting, management and a separate IBM recovery path are all in scope. Most managed cloud providers will host x86 workloads and quietly decline the IBM i estate, which leaves manufacturers, distributors and insurers running a core system nobody will take responsibility for. If that describes your environment, it is worth putting on the requirement list explicitly — it eliminates a lot of the market quickly.

Yes. Workloads can sit on your own floor, in a third-party data centre, in a hyperscaler, or in a CloudFirst location, and the managed service wraps whichever you have. That matters if you are mid-lease on a colocation contract or have already committed to Azure — you do not have to migrate to buy the management layer.

Nothing. Fibi is paid a commission by the provider you select and you pay the same rate you would have negotiated directly. The comparison against other managed cloud and data-resiliency providers, the review of recovery-time commitments, and the contract support cost you nothing.

Three things, and they are the ones most often skipped. First, whether the stated RTO and RPO are contractual or aspirational — the tier you buy determines that. Second, what is actually in scope: servers are usually covered, but Microsoft 365, Salesforce and endpoints are separate line items. Third, how failover testing is scheduled and who pays for it. Fibi reads those clauses before you sign, because a recovery commitment nobody has tested is a document, not a capability.

A shortlist with indicative pricing normally comes back within 24 hours of the requirement being clear. Assessments, provider meetings and contract review typically run two to four weeks, and onboarding another two to six depending on how much data has to move and whether an IBM i estate is involved.