Solomon e3, the energy infrastructure company, today announced that it has moved the platform’s development and MVP environment to NexQloud One, and that total monthly cloud spend has fallen by more than half after a Qlarity FinOps review.
Solomon e3 is an AI-powered geospatial platform cities, utilities and healthcare systems use to turn energy funding into completed upgrades. Deployments channel contracts to local, minority-owned businesses.
Moving Solomon e3 to NexQloud
The environment runs the portal, gateway and API as containers on managed Kubernetes, with a self-hosted OpenSearch cluster and PostGIS. Application code was not rewritten. NexQloud monitoring has recorded no unplanned downtime.
A NanoServer is an ISV-certified Lenovo device built on the Intel Core i9-14900T, which Intel rates at 35 watts across 32 hardware threads. It needs no cooling plant or power distribution, so it can sit in a building already lit and conditioned.
“Solomon e3 was not stuck on AWS. It was surrounded by AWS,” said Raju Vegesna, Chief Technology Officer of NexQloud. “Once search and geospatial were running on our infrastructure, the rest got simpler.”
DynamoDB, S3 and AWS Glue remain as bridge components while Postgres with PostGIS is built out as the production data layer.
A Bill That No Longer Matched the Product
Solomon e3 cloud bill had climbed for a year. “Our bill grew to a size that did not match our product, and I couldn’t tell you why,” said Aaron Wright, CEO of Solomon e3. “NexQloud went line by line and showed us what each one was doing.”
Solomon e3 provided its bill, codebase and infrastructure definitions. NexQloud’s engineers read the three against each other to establish which services were running, which were billing, and which were doing neither, a Qlarity FinOps review: the principles NexQloud’s Qlarity product automates, applied by hand.
The savings came from three areas. Idle resources: services billing while doing no work were retired. Overprovisioned capacity: workloads resized to the measured load. Less expensive compute: for identical shapes, NexQloud costs about a third less than AWS at published list prices.
The Question
“We spend our days telling people how to use less energy, while running our platform on infrastructure that strains the grid was a contradiction we thought we had to accept,” said Wright. “The cost results raised a second question. If this architecture uses infrastructure differently, does it change the energy required for the same workload? That is what we want measured independently.”
Solomon e3 and NexQloud will commission an independent academic review of cost, compute, energy efficiency, and publish the findings.
The Figures
The “about a third” figure compares identical configurations at published list prices in us-east-2, on-demand, no Savings Plan applied. The “more than half” figure is Solomon e3 own, measured across total cloud spend including AWS services still in use.
Read Also: Document Strategy Recognizes DataOceans Among Its 2026-2027 HOT Companies
