How Intelligent Manufacturing Planning Reduces Supply Chain Disruptions

A Note to Our Community

Hi from the LMNAs team,

Last month, we told you something big was almost ready to come out from behind the curtain. This is that edition.

This month, we kept coming back to a different question, one every IT team running ERPNext eventually asks:

Why does the ERP work fine, but running it never gets easier?

The answer doesn't live in the software. It lives in everything sitting underneath it: the environments, the access, the upgrades, the bill nobody can explain.

This edition follows that gap from where it starts to where we closed it.

Before You Read On

Picture this.

Two IT teams, both running ERPNext for a fast-growing company. Both technically capable. Both know Frappe well.

One spends Monday morning provisioning a new environment for a client demo, chasing access across three separate logins. The other has it live before their coffee's gone cold.

Same skillset. Same ERP. Wildly different mornings.

Hold that image. By the end of this edition, you'll see exactly why.

The Wall Every ERPNext Team Hits

Ask any team running ERPNext on their own servers and you'll hear the same five complaints:

Adding or removing a person means logging into every environment separately → There's no safe place to test, so changes go straight into production → Upgrades get skipped for years because nobody wants to risk a live system → Cloud bills arrive with zero breakdown of what's actually costing you → Data residency is whatever the hosting provider decides, not you

None of this is a Frappe problem. It's an infrastructure problem. That's exactly why managed hosting platforms exist in the first place.

So if the problem is well known, why did we still feel the need to build another one?

Why We Built LensCloud This Way

Before writing a single feature, we listed every pain point IT teams face running ERP in production. Every decision after traced back to that list.

Four decisions came out of it:

1. Full control for IT teams, not just access management. Deploy sites, manage access across every environment, and shape business processes, all from one place.

2. Built as capabilities, not bundled tools. Analytical Cloud for analysis. Chordium for SDLC. CRM Cloud for customers. LENS IPS for planning. Each one usable on its own, so teams only run what they need.

3. Make the modules talk to each other. LUMI, our AI agent, connects data across every module. No exporting reports between tools just to get one answer.

4. Don't force a rip and replace. LensCloud is built to integrate with the ERP systems teams already run, not replace the whole stack overnight.

Control for IT teams. Modular capabilities. Connected data. Integration instead of disruption. Four decisions, one platform.

Good intentions on a slide are one thing. How does it actually hold up against the platform teams already know?

How LensCloud Actually Compares

Frappe Cloud is the familiar name here, and it's earned that. It's been running production Frappe sites for years, starting around $5/month on shared compute.

LensCloud takes a different angle. Instead of just hosting a site, it's built around how growing teams actually operate: multiple environments, multiple people, and a real need to know what's happening across all of it without logging into five different places.

Environments: Dev, QA, and Production bundled together, versus separate setups per site
User management: add or remove a person across every environment in one action, versus managed per site
Upgrades: scheduled, tested, with a rollback option, versus managed upgrades and backups
Billing: usage-based, broken down by environment in real time, versus compute-based, not per user
Ecosystem: a connected platform (analytics, testing, SDLC, CRM, tender intelligence, an AI agent), versus hosting only

This was never an argument about which one is better. It's about which one fits how a team actually works.

Four decisions, a real comparison, and a platform that's been "almost ready" for a month now. So, is it ready?

LensCloud by the Numbers

Workspace live in 6.5 minutes
Totally free to start, no credit card needed
15+ teams opted in on day one
8 core capabilities on one connected platform
Built to integrate with SAP, Odoo, and Salesforce, not replace them

The Answer

Two teams, same ERP, same skillset. One spent the morning logging into three environments to provision a demo. The other had it live before their coffee went cold.

The difference was never the team. It was whether the environment layer got in the way or got out of it.

On July 29, LensCloud went live.

Sign up, fill in a few details, and a LENS workspace goes live in 6.5 minutes. In the first day alone, 15+ teams already opted in for early access.

Watch the trailer → See the launch day post → Reserve your spot →

Beyond Our Own Feed

Launch day didn't stay on our own timeline.

We showed up in Frappe forum threads, talking directly with other teams and organizations building on the same stack, not just posting and waiting for replies.

We also reached out to startups outside India, walked their founders through what LensCloud does, and the read-back was consistent: teams well outside our usual audience recognized the same gap we built the platform to close.

A launch is only as real as the rooms it holds up in. This one held up in more than one.

What Caught Our Eye

McKinsey's latest research on CIO technology budgets puts a number on the exact gap this edition has been circling: organizations that keep run-based infrastructure costs under control spend at least 20% less of their technology budget just keeping things running, freeing that budget for the work that actually moves the business forward.

That's not a people problem or a discipline problem. It's the same environment-and-access gap we spent this edition on, just measured in budget instead of minutes.

Future Updates

What's Coming in August

July was the launch. August is everything underneath it.

In August, we'll cover:

Deploy ERPNext in Under 15 Minutes — from account creation to a running instance
Inside LensCloud — customer journey, deployment workflow, and platform experience
Building for Reliability — the architecture powering secure, scalable ERPNext hosting

If July was the reveal, August is the walkthrough.

Subscribe here — you won't want to miss this one.

Thank you for reading, and for the trust you place in us each month.

Team LMNAs

Reader's Corner

The Wall Every ERPNext Team Hits "None of this is a Frappe problem. It's an infrastructure problem."

Why We Built LensCloud This Way "Every decision after this traces back to that list."

How LensCloud Actually Compares "You're not hosting a site and bolting on tools one by one."

Also from our founder: Why Gen Z May Not Listen to Us, But That Shouldn't Stop Us From Supporting Them "They may not always listen to us. But they are always observing us."

Feedback and Suggestions

If something in this edition resonated, or if there's a hosting or infrastructure challenge you're facing that we haven't addressed, we would genuinely like to hear it.