CentralIA: the version-control provider is the backend
Published:
CentralIA: the version-control provider is the backend
Once you run more than a handful of initiatives across many repos, the state of the whole portfolio lives nowhere: scattered across READMEs, plan files, issue trackers and your own head. A static dashboard goes stale the moment a repo moves. CentralIA fixes that by making the version-control provider itself the backend of the console.
GitHub / GitLab / offline emulator to a management repo via its structure map
A filterable portfolio grid, per-initiative 5-axis status (development, design, implementation, deployment, value), live open issues, and a hub growth graph. Never staler than the last commit.
It is a real tool, not a mockup: the connectors are genuinely implemented and the offline emulator is a self-contained backend with a bundled fake management repo, so it runs with no credentials. The access token lives in the server environment only, never the browser or a database, and a server-side anonymize toggle redacts client info for screen-sharing. Single-user auth; the public instance is private, the offline emulator is how to see it. Live · source.
