Edge security at the perimeter.

Requests arrive from the open network, are inspected and filtered at the Cloudflare edge, then routed to compute running on AWS or Google Cloud, with cross-cloud connectivity between them and the enterprise workspace layer running on top.

Each service line below can be engaged independently or as part of a single managed environment.

A systems integrator, not a reseller

iceMax is a Singapore-based systems integrator and managed service provider. We do not sell one platform; we design the path between several. A typical engagement puts a Cloudflare perimeter in front of workloads placed across AWS and Google Cloud according to where each runs best, connects them with peering or dedicated interconnect, and layers a Lark workspace with its approval workflows integrated into the enterprise systems behind it.

The distinction matters in operation. When the perimeter, the compute and the network between them are designed by one team, a rule change at the edge is made with knowledge of what the origin expects; a workload moved from one cloud to another carries its inspection and access policy with it; a cost review looks at the whole estate rather than one invoice. There is one party accountable for the path, and one number to call.

How engagements are structured

Every service line follows the same four-stage shape: an assessment of what exists, a design specified against measured demand rather than a template, a staged deployment in which rules and capacity are verified before they are enforced, and ongoing operation in which the environment is reviewed for security posture, capacity and cost on a continuing basis.

Engagements begin either with a new build — an application moving to the cloud, a perimeter being put in place for the first time, a workspace being deployed — or with a takeover of an estate that has grown without an owner. Both start with the assessment; the difference is only in what it finds.

Who we work with

Organisations headquartered in Singapore or operating across Asia-Pacific, with public-facing applications, distributed teams, or infrastructure spread across more than one provider. Clients include those with in-house engineering teams who need a partner for the infrastructure layer, and those without a network or cloud function of their own for whom we are that function.