Frappe Vault

We built Frappe Vault to make it easier to manage passwords, API keys and other shared credentials across our team and client projects. This month, feedback from users continued to shape the product. We worked on better secret organisation, codebase refinement around Frappe conventions, and explored support for TOTP credentials and simpler user management.

The broader lesson remains the same: managing secrets is not just about storage, but about making access and organisation easier as teams grow.

Frappe Local

Getting Frappe running locally can still be a barrier for beginners, client teams and anyone who wants a quick sandbox without dealing with infrastructure first. This month brought more UI and reliability improvements, along with one of the most requested additions: Windows support. Early users are already helping us surface platform-specific issues and shape what comes next.

We are also following Frappe Pilot closely as we think about how Local should evolve alongside newer bench and site management tooling.

Frappe Playground

Frappe Playground started as an experiment to remove the setup required just to explore or demonstrate a Frappe app. A major refactor this month improved compatibility, persistence and reliability. Playground can now install selected apps, retain multiple instances and, for the first time, boot ERPNext. We also added URL-based boot configuration to make pre-configured demos possible.

That brings Playground closer to becoming a useful sandbox for exploration, testing and lightweight app demos without provisioning infrastructure first.

Frappeverse 2026

We spent two days at Frappeverse learning what the Frappe team is building and, more importantly, talking with people working through real ERPNext implementations and migrations.

Those conversations gave us better context on where friction still exists across the ecosystem and where projects such as Local, Playground and Vault may be useful. That perspective will continue to influence what we experiment with and contribute next.

What We’re Learning and Applying

Each month, we take a step back and look at what’s happening around the industry and ecosystem, picking a few ideas and tools that we can learn from and bring into our own work.

A few things stood out this month:

• WordPress keeps expanding its native design toolkit. WordPress 7.1 brought more responsive styling controls, pseudo states, an SVG Icon API and continued block improvements. The direction is interesting: more design capability is moving into native WordPress, reducing the need to recreate it through custom or page-builder-specific layers.
• WordPress is expanding the Abilities API to make functionality easier for external clients and AI agents to discover and execute. That could provide a cleaner foundation for future AI and automation workflows in WordPress.
• Frappe Pilot is one to watch it continued evolving through August across site management, backups, logging and infrastructure tooling. We are following it closely because it overlaps with a question we are exploring through Frappe Local: how much infrastructure should someone need to understand just to create and manage a Frappe environment?
• Laravel added a read-through filesystem driver that can fall back to an old storage location and progressively move files as they are accessed. We liked the underlying idea: migrations do not always need to happen as one large, risky cutover. Sometimes the better system is one that transitions gradually.
• Laravel Boost is exploring ways to extract project conventions and turn them into reusable instructions for coding agents. The interesting part: better AI-assisted development may depend less on better prompts and more on giving agents the context behind how a codebase is built.
• Coding agents are becoming a workflow problem. The conversation around agents is moving beyond how well they can write code towards context, decomposition, review, testing and control. That matches what we are seeing ourselves: useful agent workflows depend less on the perfect prompt and more on the environment, instructions and processes built around them.