Mike's Notes
This is the revised Pipi roadmap now that the data centre is running. The recent Ajabbi Research report, "The Workspace Issue," has also been revised to reflect these changes.
Resources
- https://www.blog.ajabbi.com/2026/02/pipi-data-centre-operational.html
- https://www.blog.ajabbi.com/2025/05/a-roadmap-to-pipi-10.html
- https://www.blog.ajabbi.com/2026/02/agent-card.html
- https://www.blog.ajabbi.com/2025/11/pipi-engines-to-build-deploy-and-manage.html
- https://www.blog.ajabbi.com/2026/02/the-workspace-issue.html
- https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
References
- Reference
Repository
- Home > Ajabbi Research > Library >
- Home > Handbook >
Last Updated
01/03/2026
Having a Data Centre changes the roadmap
Mike is the inventor and architect of Pipi and the founder of Ajabbi.
Having a separate Pipi Core Data Centre changes everything. This has a direct impact on what is possible and on the best path forward.
This is the revised working Deployment Roadmap for Pipi. The sequence is correct; the timing is a guess. Start at Option A.
Option A
| When | Task | Detail |
|---|---|---|
| February 2026 | Data Centre migration | Separate networks for the isolated Pipi Core Data Centre and the Ajabbi Office. |
| March 2026 | Data Centre configuration | Pipi running autonomously 24x7x365, with a x10 increase in productivity. |
| April 2026 | Workspace testing 2 | Workspaces containing 15,000 web pages are rendered by the CMS Engine with no errors. |
| May 2026 | Workspace testing 3 | Workspace UI Menu rendered without errors. |
| June 2026 | Workspace testing 4 | Draft in-context help & learning material generated for each workspace without errors. |
| July 2026 | Workspace testing 5 | Module-based UI forms and data grids rendered with sample data without errors. |
| Workspace testing 6 | Complete HTML workspace demo with connected initial developer documentation rendered without error | |
| Workspaces for Pipi & Developers | Workspaces are deployed in the Data Centre for production use by System Admin and DevOps, with a x10 increase in productivity. | |
| Mission Control | Telemetry on the Data Centre. | |
| IaC | Deploy infrastructure on GCP Free Tier |
|
If Ajabbi then gets into a Google Startup program with lots of credits, go to Option B; otherwise, go to Option C.
Option B
| When | Task | Detail |
|---|---|---|
| IaC | Deploy infrastructure on every non-free part of GCP. | |
| IaC | BoxLang VM containing Pipi Open-Source, deployed to GCP via IaC. | |
| MCP, A2A | Pipi > Gemini DeepMind > Pipi | |
| Working Demo | Fully working demo workspaces available on GCP for customers and developers to tryout. | |
| Customer Deployments | Ajabbi Personal, Developer, and Enterprise account Workspaces are available on GCP. | |
| Security | Google Threat Intelligence + Mandiant deployed. | |
| TPU | Pipi deploys to TPU (experimental). | |
| Customer Deployments | Ajabbi Researcher and SME account Workspaces are available on GCP. | |
Try Pipi out on every available cloud platform using the free tier, waiting for any door to open and being ready to move fast.
Option C
| When | Task | Detail |
|---|---|---|
| IaC | Deploy infrastructure on the AWS Free Tier. | |
| IaC | Deploy infrastructure on the Azure Free Tier. | |
| IaC | Deploy infrastructure on the Digital Ocean Free Tier. | |
| IaC | Deploy infrastructure on the IBM Free Tier. | |
| IaC | Deploy infrastructure on the Oracle Free Tier. | |
| IaC | Deploy infrastructure on the Wasabi Free Tier. | |
| ... |
At a certain threshold, Pipi 10 will come into being, creating many more possibilities.
No comments:
Post a Comment