Blog

We are starting a weekly Change Updates series for AGGREGATE: short notes on what shipped, for people running it. This week, Beta v2026.10.14.

Sooner or later, someone auditing a system asks three plain questions. Who changed this setting? Who created that account? When did it happen? In a lot of analytics tools, those questions are hard to answer for the tool itself. The reports are polished. The record of who did what inside the tool is thin, scattered, or missing.

What a public college actually needs from analytics: own the data, respect the visitor, keep the definitions stable, and let a small team answer simple questions with confidence.

A read-only MCP server for AI assistants, with sign-in by dashboard approval or API token. It is off by default.

Reporting API v1: read the reporting views over HTTPS with a token, for scripts, notebooks, and AI tools that cannot open a database connection. Off by default; private views need their own switch.

Why Subschema keeps choosing Grav CMS: flat-file speed, an admin panel clients can use, blueprints and Twig, the GPM plugin ecosystem, and honest limits, plus the use cases where Grav fits best.

For twenty years the default answer was buy, do not build. AI and compounding SaaS prices have changed the facts underneath that answer. A look at the new build versus buy equation, the condition that decides it, and why internal open source matters.

Treat web analytics as a curated data source you own and govern: events not visitors, protection enforced in the database, documented views for BI tools and AI assistants.