What if

Mike's Notes

This is a note to self; there are some questions I need to answer.

I'm doing some helpful free "start-up" training at NZTE, CreativeHQ, Startup Aotearoa, etc., which involves thinking about some hard questions and putting words onto several canvases. The people are all excellent, making me do a lot of thinking.

Pipi is not a simple app. It uses a novel architecture to help solve enormous, complex, and challenging problems.

How do I explain to anyone interested in what Pipi provides?

Resources

• https://en.wikipedia.org/wiki/Open_platform
• https://www.blog.ajabbi.com/p/pipi.html
• https://wiki.ajabbi.com/eng/9/
• https://www.nzte.govt.nz
• https://creativehq.co.nz
• https://startupaotearoa.org

References

• Reference

Repository

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

Last Updated

17/05/2025

What if

By: Mike Peters

On a Sandy Beach: 20/02/2025

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

• A complete enterprise SaaS system took 24 hours to automatically deploy for a customer.
• Built out of reusable modules that automatically sync with no limit on the number of modules.
• New modules can be simply and quickly created using no code.
• It can start small and cheaply with minimal risk with one module, then add more as needed.
• No sales engineers.
• All self-service.
• Fully configurable by their DevOps team using no code.
• The enterprise SaaS was 100% open-source.
• Its underlying industry model was constantly improved by the users of all deployments.
• Industry Ontology and standards-based.
• Customer data stays with the customer and is invisible to the platform.
• Any human language or writing script can be used.
• Community-provided translation and localisation
• Its code base was completely obfuscated (all UUID).
• Each deployment had a unique code obfuscation.
• Only the UI, API and stored data use actual words.
• The platform is a closed-source black box with all parameters visible.
• A unique enterprise SaaS system was fully delivered on time and on budget.
• Costs are cut by an order of magnitude.
• Long-term low-cost of ownership.
• It can scale simply.
• Able to make use of existing tools like Kubernetes, Docker, etc.
• Designed to run on most Cloud providers, giving users options and data sovereignty.
• Encourages an open ecosystem without moats, including 3rd party support, training, plugins, etc.
• Had a fully-synced closed-source visible digital twin for experiments and system learning.
• It can be integrated via API without restrictions.
• It didn't need a super-computer with thousands of cores.
• The whole thing is owned by a public good foundation, so there are no investors, corporate highjacking or enshittification risks.
• Public open handbook.

Open questions

• What kind of problems does Pipi solve?
• Why do these problems exist?
• Why solving these problems is essential?
• Would it be beneficial to society?
• What's wrong with the existing alternatives?
• Would people use it?
• Would enough people pay to use it to make it viable?
• Would it reduce the waste of software failure?
• What kind of Foundation would be needed?
• How would the developer community be supported?
• How would R&D be supported?