Frequently Asked Questions

Common questions from teams evaluating or onboarding onto PushOps.

What clouds does PushOps support?

AWS and GCP.

Applications run on Amazon EKS or Google GKE, and managed data services are
provisioned in the matching cloud. If a different provider is a requirement,
raise it with your Customer Success Engineer before onboarding begins.

What does the migration and onboarding process look like?

Onboarding happens in two phases.

1. Initial onboarding — minimal intervention, to get the workloads running
   on the platform quickly and start reducing cost.
2. Optimization phase — a joint review to simplify and improve the
   infrastructure once it is established on the platform.

A full migration typically takes two to three months, depending on the
complexity and the number of services being migrated.

How does cost scale as we grow?

Cost scales roughly linearly with the infrastructure actually running. There is
no step change at a particular scale.

CTO2B also monitors spend and proactively recommends cost-efficient changes
based on how the environments are actually being used. Cost and compliance
reports are available in SVIEW at any time.

Does the platform work with a heavily customized infrastructure?

In most cases, yes. The platform is designed to be adapted to an existing
architecture rather than to require a rewrite before migration.

How well it fits a particular estate is assessed during onboarding, before any
migration work starts.

Can we choose which technologies are used, and understand their cost?

Yes. The technologies used in an environment are chosen together with the
customer, and CTO2B explains the trade-offs — what each option does, what it
costs, and what it saves.

Design and planning decisions are usually the largest driver of long-term
operational cost, so this is worth doing explicitly at onboarding rather than
later.

Can you advise on keeping our infrastructure simple?

Yes. The focus is on efficient, cost-effective infrastructure sized for the
team that has to run it, rather than on large-scale patterns that add
complexity without benefit at that size.

Dedicated sessions on specific architecture topics can be arranged through your
Customer Success Engineer.

What happens if we decide to leave?

The core infrastructure remains unchanged, because it is managed as code in
Git. If you migrate away, the system keeps running without disruption.

What you lose is access to CTO2B's monitoring, the SVIEW portal, the platform
automation, and support — not the underlying infrastructure.

Related articles

• What is PushOps — what the platform is and what it includes
• What You Can Do vs. What We Manage — the responsibility boundary
• Getting Help — raising a question that is not answered here