Hello Frappe Community! 
We’re building LensCloud, a platform by LMNAs Cloud Solutions to make it easier for organizations to deploy, run, and manage Frappe applications.
If you have ever been involved in a Frappe or ERPNext project, you may have experienced this: Building the application is one challenge. Running it reliably in production is another.
As a business grows, so does everything around its ERP. You end up needing to:
→ Launch new environments fast
→ Manage multiple customers, companies, or sites
→ Ship updates safely
→ Scale resources as usage grows
→ Cut the operational load on technical teams
→ Give business teams a reliable application without making them worry about the infrastructure underneath.
That’s the problem LensCloud is trying to solve.
Why We Started Building This
We’ve spent years building both simple and complex Frappe solutions across industries. In most of those projects, we weren’t just implementing, we were also the ones hosting and running things in production.
That taught us the same lesson, over and over: Frappe is excellent for building business applications. Running those applications at scale is a whole different job, usually scattered across a dozen tools and processes.
We wanted something simpler: deploying and managing Frappe apps that feels like using a service, not maintaining a platform.
That idea became LensCloud.
What Is LensCloud?
At a high level, LensCloud manages the full lifecycle of a Frappe application:
Application → Deployment → Infrastructure → Operations
→ For the business: more focus on the app, less on what’s under it
→ For developers: an easier path from dev, to test, to production
→ For infra teams: no need to build the entire operational layer from scratch
Our Vision
We’re starting with the Frappe ecosystem, because we think it has enormous room to grow, not just for single implementations, but for larger, more complex application environments.
Longer term, we see LensCloud growing into a broader application platform that supports other ERP ecosystems too.
What We’re Focused On
The core idea: the complexity of running an app shouldn’t be the reason a team can’t use it.
Faster deployment. Spin up Frappe environments without every team rebuilding the setup from scratch.
Easier management. One place to manage applications and environments across their whole lifecycle.
Room for different setups. A small business wants something simple. A SaaS company needs to manage multiple customers. An enterprise wants isolation and control. LensCloud is built to flex across all three, not force everyone into one shape.
Built to Stay Flexible
We didn’t want LensCloud locked to one infrastructure provider or one way of running apps.
The goal: separate the platform experience from the infrastructure underneath it. However you’re hosting, public cloud, private infra, or something else, the way you manage your applications should stay consistent.
Standing on the Shoulders of This Community
LensCloud wouldn’t exist without the work already happening across the Frappe ecosystem. While building it, we studied projects like CastleCraft Helm Charts and the Frappe Operator, and leaned on a lot of what we learned from them. related post
We’re not trying to reinvent everything. We’re building on what already exists and solving the operational problems we kept running into ourselves.
Where We Are Right Now
LensCloud is in active testing. Backend functionality and reliability are maturing fast, and the UI is still getting polished before public release.
A beta is coming soon, and it’s meant to be a two-way thing. We want to learn from how the Frappe community actually uses this.
Take a Look
Repos are public, so dig in, follow along, or tell us what’s wrong with it:
→ Infrastructure on GitHub
→ Platform on GitHub
→ Get free beta access
Would genuinely love to hear what you think. 
