InfraGuard Engineering Devlog, part 1 of 6.
Rewriting an application is one problem. Rewriting it while a fleet keeps writing into its database is another.
InfraGuard grew out of an internal Laravel 8 monitoring project. Node.js collectors were submitting server and network telemetry; backup scripts were already running against the existing schema. We could replace the application, but we could not casually rename the tables beneath those processes.
New application, old data contract
The legacy review recorded hard-coded credentials in 77 places across 36 files. It also identified raw SQL assembled from user input, plaintext remember-me cookies, and embedded cryptographic or OAuth secrets. The replacement started on Laravel 13.8 and PHP 8.4, with one constraint: leave existing table names, columns and structure intact.
The database was an integration contract, not merely private storage.…