Cloud platform architect

Cloud platforms.
Built to stay reliable.

I build cloud platforms that hold up under real production load, with reliability, security, and cost control designed in from the start. I also work directly with customers, in their environments, and build and run my own products end to end.

Prudhvi Raj Anupoju Prudhvi Raj Anupoju

10+ years Enterprise cloud & platform architecture
$2.5M+ Projected cloud TCO & licensing savings
1,000+ Workloads profiled, migrated & modernized
6 Sectors Telecom, Tolling, Healthcare, FinTech, AdTech & Education

Forward-deployed work

Close to the customer.
Through to production.

Working inside customer environments, building my own products, and tracing failures to their cause.

Discovery inside customer estates

Profiled 1,000+ servers across EU and US facilities, assessed migration readiness, and wrote the directional business cases used to qualify for AWS MAP funding.

See the engagements

A product built end to end

A PDF product taken from a broken serverless deployment to a self-audited, self-hosted app. First load is about 93% lighter and nine security findings are fixed.

Read the case study

An assistant that shows its sources

An HR tool whose assistant answers policy questions by quoting the company handbook with the document and page, and says so plainly when nothing matches.

Read the case study

Debugging live systems

Written root-cause analyses, from a silent call-record ingestion failure to an EKS ingress incident, tracing each from symptom to cause.

Read an RCA

How I work

From architecture to delivery.

The work connects architecture with delivery: setting up the foundation, moving workloads onto it, keeping costs in check, and making sure it stays healthy after launch. The learning paths explain these practices step by step.

Delivery process

How a change reaches production

Every change leaves a record of what changed, who approved it, and how to undo it.

  1. Scope it

    A work breakdown structure: work packages, owners, dependencies, and the order they land in.

    Sequenced wave roadmap
  2. Raise the change

    A change request with the risk, the rollback plan, and CAB approval before anything is scheduled.

    Regulated CI/CD delivery
  3. Prove it

    Review the plan output and rehearse outside production, so the real run holds no surprises.

    Keep Aurora DR in parity
  4. Ship it

    Roll out in stages inside the agreed window, with the rollback ready rather than improvised.

    Rolling patches on Oracle RAC
  5. Verify and review

    Check the outcome, not just that the deploy finished, then close it with a post-implementation review.

    Silent CDR ingestion failure

Experience

A decade of delivery.
From systems to architecture.

I started in Linux systems engineering, moved into automation, and now lead cloud platform architecture across multi-account AWS environments.

2021 to Present

Cloud Destinations · Lead Cloud Platform Architect

Lead architect for multi-account AWS governance, landing zones, database modernization, and cloud cost work for enterprise clients.

2020 to 2021

Spectromax Solutions · Senior Cloud Engineer

Worked on large database clusters and distributed storage behind ERP systems for manufacturing clients.

2016 to 2020

Vortex Technologies · Cloud/DevOps Engineer

Built the foundations: CI/CD automation, Linux administration, and early container work for Java apps on AWS.

Background & credentials

Certifications and education.

AWS Certified Solutions Architect, Associate

Amazon Web Services

HashiCorp Certified: Terraform Associate

HashiCorp

AWS Migration Acceleration Program (MAP), Accredited Practitioner

AWS Partner Program

B.E., Mechanical Engineering

KL University, 2010 to 2014

Get in touch

Questions about any
of this work?

I'm happy to talk through any case study or learning path: the architecture, the trade-offs, or why I made a particular call. Send a message here, or use email or LinkedIn.