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.
Update 25/03/2026
A very nice chap from Google contacted me to assist with applying to join one of the Google AI Accelerators. I started the application, then stopped when I realised the 2 years of support and generous free credits start as soon as it's approved. I need to complete all Stage 1 steps in the roadmap below, and the Stage 2 IaC connection to the GCP free tier to deploy Pipi open-source before applying, to make the best use of the opportunity.
I'm requesting support from Google DeepMind to experiment with connecting Pipi via MCP to DeepMind Gemini and to find a way for Pipi closed-core to use Google TPU. Stage 3 will be highly experimental and may produce unexpected results.
Pipi is a non-generative multi-agent system with no tokens. It doesn't need tokens to work and its 27 layers deep so far and counting. I expect it to get very barnacled and crusty over time.
Update 31/03/2026
Setting up data centre automation has revealed that workspace deployments need to be performed in this order of account types due to the permissions cascade.
- Operations Accounts (to admin Pipi)
- Researcher Accounts (to edit UoM, ontologies and physical laws)
- Developer Accounts (to create enterprise workspaces)
- Personal Accounts (to sort out personal profiles - UI fonts, etc)
- Enterprise Accounts (to test and use the system for work)
- etc
Update 17/04/2026
Containers, named Pipi Nest, were created to deploy Pipi.
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/03/cascade-of-permissions-on-pipi.html
- https://www.blog.ajabbi.com/2026/02/the-workspace-issue.html
- https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
- https://www.blog.ajabbi.com/2026/03/accelerate-and-rubber-hits-road.html
- https://cloud-servers.ortusbooks.com/
References
- Reference
Repository
- Home > Ajabbi Research > Library >
- Home > Handbook >
Last Updated
16/10/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 directly affects what is possible and the best path forward.
This is the revised working Deployment Roadmap for Pipi. The sequence is roughly correct; the timing is just a guess.
Stage 1
Production foundations to enable automation and rapid use.
| When | Task | Detail |
|---|---|---|
| February 2026 | Migration ✔ | Separate networks for the isolated Pipi Core Data Centre and the Ajabbi Office. |
| March - April 2026 | Pipi Nest ✔ | Pipi deployment container |
| April 2026 | Mission Control ✔ | Telemetry on the Data Centre. |
| April 2026 | Automation | Pipi Core running autonomously in a Pipi Nest 24x7x365, with a x10 increase in productivity. |
| May 2026 | Data Centre Admin | Agent Workspace rendered by the CMS Engine with no errors. |
| May 2026 | Workspace | Workspaces containing 15,000 web pages are rendered by the CMS Engine with no errors. |
| 2026 | Workspace | Workspace UI Menu rendered without errors. |
| 2026 | Workspace | Draft in-context help & learning material generated for each workspace without errors. |
| 2026 | Workspace | Module-based UI forms and data grids rendered with sample data without errors. |
| 2026 | Workspace | Complete HTML workspace demo with connected initial developer documentation rendered without error |
| 2026 | Workspaces for Agents & Developers | Deploy workspaces in the Data Centre for production use by System Admin and DevOps, with a 10x increase in productivity. |
| 2026 | ||
| 2026 | ||
| 2026 | ||
| 2026 | ||
| 2026 |
Stage 2
Automate Pipi deployment across every available cloud platform, with a free tier.
| When | Task | Detail |
|---|---|---|
| 2026 | IaC | Deploy infrastructure on the AWS Free Tier. |
| 2026 | IaC | Deploy infrastructure on the Azure Free Tier. |
| 2026 | IaC | Deploy infrastructure on the DigitalOcean Free Tier. |
| 2026 | IaC | Deploy infrastructure on the GCP Free Tier. |
| 2026 | IaC | Deploy infrastructure on the IBM Free Tier. |
| 2026 | IaC | Deploy infrastructure on the Oracle Free Tier. |
| 2026 | IaC | Deploy infrastructure on the Wasabi Free Tier. |
| 2026 | ... |
Stage 3
Deploy to any platform that admits Ajabbi to its startup program and offers lots of credits to enable experimentation and scaling with early customers.
| When | Task | Detail |
|---|---|---|
| IaC | Deploy infrastructure on every non-free part of the platform. | |
| IaC | BoxLang VM containing Pipi Open-Source, deployed via IaC. | |
| MCP, A2A, Skills | Pipi > LLM > Pipi | |
| Working Demo | Fully working demo workspaces available for customers and developers to try out. | |
| Customer Deployments | Ajabbi Personal, Developer, and Enterprise account Workspaces are available. | |
| Customer Deployments | Ajabbi Researcher and SME account Workspaces are available. | |
| Scientific Workflows | TPU | |
No comments:
Post a Comment