The Future
Ideas built into Azquo’s foundations that haven’t yet had their moment, and partner-shaped opportunities for the years ahead.
Ready but not yet routine
Several capabilities already proven in the work but not yet routine, awaiting their moment.
Portable databases as packages. An Azquo database can be packaged with round-trip scripts so a colleague or partner can unpack it on a foreign machine with a single command, rebuilding the on-disk working folder from the database itself. We have proved the pattern internally. The goal is to make it routine: every customer’s database becomes a distributable artefact that travels with its conventions intact.
Self-documenting institutional memory. Every Azquo instance ships with the Azquo_Skills database — the conventions for working with the platform. As agents work, they write what they learn into per-business meta-information, and the next agent reads it back. The store accumulates institutional memory. Today this loop is hand-tended; the goal is conventions and tooling that make it automatic, so each session leaves the database a little richer than the last.
External-data anchoring. Agents can fetch external context — weather, regulatory filings, market data, public datasets — and anchor it to the same hierarchies as a business’s internal data. This turns Azquo from a static store into a live cross-reference layer between proprietary data and the world. Demonstrated; not yet a deployment pattern.
Where a partner could help
Concrete asks, where the right collaborator could shorten timelines.
Deeper Excel integration. Custom Functions, MCP-backed cell formulas, workbook-as-database projections. The current Excel taskpane is functional but clunky; deeper integration is where the spreadsheet stops being a viewer of database content and becomes a working surface for an agent. Office-extensibility experience would land in days, not weeks.
Hosted Streamable HTTP MCP. Today evaluation access uses an SSH-tunnelled onboarding flow — fine for serious evaluators, friction for casual ones. A hosted MCP exposed over Streamable HTTP transport, registerable in any MCP-capable runtime, would drop the trial barrier to a one-click install.
Agent-harness conventions. System prompts, tool surface and meta-info shapes that make agent operation safe and productive across deployments. The patterns exist in the work we do; what is needed is the harness that lets a customer point an agent at their Azquo instance and have it operate by convention rather than by improvisation.
The open-source horizon
We have decided that Azquo should be released under a permissive open-source licence. The work is in preparation; details will follow when the licence is filed and the repository is published. The intent is to make the architecture available to anyone building agent systems that need a memory-and-audit layer underneath them, and to invite contributors who care about the same problems.
Get involved
If anything here resonates — especially if you have built agent harnesses, care about data lineage and audit trails, or have an Office-extensibility instinct — we would like to hear from you.