AGGREGATE Beta v2026.10.16: Forensic database sync with hashed identifiers
This week, Beta v2026.10.16.
Blog
AGGREGATE Beta v2026.10.15: Security fix, installation hardening, and a maintenance skill for AI assistants
This week, Beta v2026.10.15.
AGGREGATE Beta v2026.10.14: Global website selector, token fixes, and safer event names
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.
Who Changed What, and When: Auditability in AGGREGATE
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 (and Why GA4 Is Not It)
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.
AGGREGATE Beta v2026.10.13: MCP server, transactional email, and two-step sign-in
A read-only MCP server for AI assistants, with sign-in by dashboard approval or API token. It is off by default.
AGGREGATE Beta v2026.10.12: Reporting API v1, audit trail, and website settings
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.
The CMS We Keep Choosing: Grav
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.