A roadmap to Pipi 10

Mike's Notes

Pipi 10 in production must run on BoxLang.

I sent draft notes to Ortus yesterday to discuss future use of BoxLang. I then edited the notes and shared them with the growing Pipi community. I will add the answers as more is discovered about what needs to be done to make it possible for Pipi 10 to use BoxLang.

Training is available on BoxLang Academy.

Can you spot any errors in my assumptions? Do you have other ideas or queries?

Contact me.

Resources

• https://www.blog.ajabbi.com/2025/05/boxlang-100.html
• https://www.blog.ajabbi.com/2024/12/pipi-builld-roadmap.html
• https://www.blog.ajabbi.com/2025/05/a-three-data-centre-model-for-pipi.html
• https://boxlang.io/download#modules
• https://learn.boxlang.io/

References

• Reference

Repository

• Home > Ajabbi Research > Library >
• Home > Handbook > 

Last Updated

30/05/2025

A roadmap to Pipi 10

By: Mike Peters

On a Sandy Beach: 21/05/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Draft roadmap

• This is a draft, so expect it to change
• This roadmap is probably for the next 2-3 years at least
• The finalised plan will be published for the Pipi Community.
• No money is available right now.
• A plan is needed to avoid rework.
• Don't expect Ortus to do work for free.
• Realistic expectations of what is possible.
• Good income will come later from paying customers for solving complex problems.
• Focus on the core by outsourcing other work to experienced contractors.
• Open-source all modules on GitHub.

Ajabbi

• The common name of 
• A company to handle payments
• Non-profit foundation to support users (to be established)
• Research Institute for ongoing development (to be established)
• Description
• Solved a huge, expensive problem with no existing competitors
• Pre-revenue start-up with no $$$
• Growing community
• Purpose
• Act like other foundations (Wikimedia, Apache and Linux) and use the income surplus to support
• Minority languages i18n
• Open-source efforts (especially CFML, including Ortus)
• User groups
• User conferences
• Book publishing
• Open research grants
• Etc

Pipi

• The name of the software
• Mike has been the architect since 1997
• Versions 1-4 were in production eventually with 300K lines of code, an 800-table database, ESRI Web GIS, 500 classes, 3K methods, a 5 FTE team and a 3-rack data centre
• Versions 6-8 were working, non-production, undergoing refactoring
• Version 9 works, moving to production (current)
• Version 10 (planned)

Current Pipi 9

• Works great
• Runs in a dev environment
• Unique architecture with 20+ layers and hundreds of autonomous agents
• Uses nature-inspired algorithms
• Going from headless to a Pipi-generated UI
• Migrating to a 42U server rack completely isolated from the internet.
• Using old Windows server boxes will do for now.
• The CFML code runs on ColdFusion Server 2021 Developer Edition.
• The CFML code could run on ColdFusion MX, Open Blue Dragon, or Lucee. 
• Uses <CF> tags as in Ben Forta, et al. (don't tell Michaela, I don't want to die)
• Uses 300+ embedded config databases (MS Access)
• Uses PostgreSQL for production data
• Writes CFML code and then executes it
• Writes SQL and then executes it to create and populate tables
• Static HTML generator (90K page websites)
• Uses XML, XML Schema, etc, internally
• Mostly self-managing
• Self-documenting
• Currently rendering a 20,000-page static website for developers
• The code base will self-grow 10x larger over time

Planned Pipi 9

• Some money is coming soon
• Generate revenue from niche batch render jobs
• Code generators and the generated code must be rewritten to be BoxLang compatible, so no refactoring by Ortus is required.
• Pipi 9 will create Pipi 10
• Pipi 10 to be BoxLang native
• BoxLang (+++++++) paid support
• Pipi 10 to become geodatabase capable
• BoxLang will enable the future use of Python, PHP, etc

Planned Pipi 10 Systems

• Render System
• Functions as an automated AI-assisted development environment
• Isolated from the internet
• Uses VM
• Run on BoxLang installed on Windows on new 64 hardware
• JDK 21+
• Ortus to supply a ready-to-run VM image.
• 100% self-managing via CommandBox dynamic CFML scripts
• Renders working enterprise system modules (database, code, UI, API, user documentation)
• MS SQL edition
• MySQL edition
• Oracle edition
• PostgreSQL edition
• Exports modules to the Staging System via manual hard drive transfers
• Staging System
• Connected to the internet
• Uses VM
• Runs on BoxLang installed on Debian
• JDK 21+
• Ortus to manage the BoxLang platform VM on a long-term contract
• Uses PostgreSQL
• Adds i18n to modules
• Creates updates
• Integrates i18n modules into customised enterprise systems for paying customers
• Exports
• Github
• i18n modules to GitHub for open-source
• i18n user documentation
• Cloud
• Customised i18n enterprise systems
• System updates
• Cloud System
• Connected to the internet
• Uses VM
• Runs on BoxLang installed on Debian
• JDK 21+
• Ortus to manage the BoxLang platform VM on a long-term contract
• VM hosted
• AWS
• Azure
• Digital Ocean
• GCP
• IBM
• etc
• private cloud.
• The customer chooses their production RDMS database(s) for their data.
• MS SQL
• MySQL
• Oracle
• PostgreSQL

Questions for Ortus

• Is a list of supported (or not supported) CFML tags available?
• Is <Cf tags> style coding supported?
• Could BoxLang use MS Access via JDBC on the isolated Render System, and how much would it cost to create a module to do this?
• What kinds of modules can be developed by Ortus?
• What is the cost for Ortus to provide dedicated platform support?
• Can patched VM images be supplied?
• What about the time zone differences between New Zealand, the US, and Spain?
• Is a 24/7/365 platform supported by Ortus possible in the future?

Questions for the Pipi Community

• Would support also be available from independent CFML contractors?
• Where is the boundary between community contributions and paid contractors?
• What other new BoxLang Modules would be useful?