North.cloud has raised $60 million in Series B funding to expand software that helps businesses manage spending on cloud infrastructure, artificial intelligence and data services. The New York company announced the financing on October 15, with PeakSpan Capital leading the round. Other participants included Litquidity Ventures, Companyon Ventures, Alpaca, Uncommon Denominator, Gaingels and Mana Ventures.
The money will support engineering and product hiring, wider integrations and automated cost management across cloud providers. North says it manages close to $2 billion in cloud spending and has helped customers save more than $400 million. Those are company-reported figures, rather than independently verified savings. The funding announcement does not disclose a valuation or an India-specific investment programme.
What the funding will build on
The raise follows North v3, released on August 20. That version added generally available Microsoft Azure support alongside Amazon Web Services and Google Cloud Platform. It also brought OpenAI, Anthropic and Snowflake billing into the platform. These are earlier product changes, not features first announced with the new financing.
One part of that release, Autobot, makes purchases of cloud commitments held in a customer's own account. North describes smaller monthly purchases that blend one-year and three-year terms, with simulations before buying and customer-set limits on flexibility and coverage. Its separate Flexbot arrangement puts the commitments in North's accounts. The distinction matters because automated purchasing does not mean the customer has no contractual exposure. Ownership and the length of a commitment remain part of the decision. North says users can model different coverage strategies before authorising purchases, rather than making a single large commitment upfront.
A separate October 6 update expanded the Analyze tool to more than 90 filtering dimensions, with up to five combined in one view. A team can examine costs by account, service, region or environment instead of relying on a single total. North's examples include separating production systems from staging systems and comparing costs for the same service in different locations.
The tool also supports comparisons across time. That can help distinguish a newly appearing expense from a recurring charge or a growing workload. The company says its Noros assistant uses the same underlying detail when answering questions. These are descriptions of the company's reporting functions, not evidence that every cost increase represents waste.
Why AI bills need a different breakdown
In its October 8 engineering guide, North explains the problem behind its AI spending push: billing measures consumption, which is not the same as completed work. One request to an AI agent can trigger several model calls, including retries. Changing models, generating longer answers or reusing less cached input can increase a bill even when the number of customer requests is similar.
That guide also distinguishes a provider's billing records from a business's internal allocation of costs. A shared account does not automatically reveal which team should bear each charge. North says estimates should be identified separately and spending without an assigned owner kept visible. This is useful context for assessing its TokenFlow plans: tracking tokens alone cannot establish whether the resulting work justified the expense. The guide also calls for deciding which models staff can use and what should happen at a spending limit, including an approved fallback, before the budget is exhausted.
The expansion goes beyond AI models. North's September 30 Datadog integration added monitoring-service costs to the same reporting system. The company says customers can split that spending by service and usage type, allocate it to business units and include it in statements alongside their cloud costs.
Monitoring software itself adds to the cost of running applications. Bringing that invoice into a wider review can show whether its growth tracks the infrastructure being monitored. North describes this integration as a way to investigate charges and discuss contracts using a shared set of figures. It does not establish that a contract will be renegotiated or that a particular saving will follow.
For related enterprise-AI coverage, Dalimss News has reported on RapidCanvas's funding and India engineering plans and the Neysa-Mavenir sovereign-cloud partnership.
