We've built all kinds of internal tools using Lowdefy, CRMs, reporting apps, ticketing systems, workflow, SOP and QC tools, call centre automation tools, customer portals, survey apps and more.

We find that having a well define abstraction framework in place helps us scale our custom apps really efficiently, particularly from a maintenance pov. Also sharing work across our team, etc. It helps if everything is pluggable, and well documented. By making Lowdefy open-source it has helped our team maintain the discipline to enforce best practices across our stack.

Lowdefy is very declarative, and it lets you build data intensive web apps in just a few lines of yaml. With AI code gen, this is where the power of the framework guard rails and generated apps really accelerate the apps we can create while following the same patterns that our team applies over all the solutions we build.

As for change in direction, no. We have a demand for building agentic experiences from our customers, and found that we could wrap it really nicely into the Lowdefy framework, especially when building in additional functionality like agents co-authoring web forms and more.

We feel that agents inside your apps is a great fit, since you can expose the same api routes, auth roles and more to agents with ease.

Well done on spawnfile. Looks very interesting!