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. A cleaner name in a migration could break a collector that was working perfectly well.

New application-owned tables use a literal infr_ prefix. We did not enable a connection-wide Laravel table prefix, because that connection still needs to read legacy tables without it. The documented repository snapshot contains 88 migrations following this coexistence rule.

Put the reason next to the rule

“Never hard-code credentials” is easy to agree with and easy to regress. Our notes pair rules with reasons and repeatable checks. The useful outcome is an executable validation, not something someone must remember forever.

This matters when AI coding tools work on the repository. Plausible code can still violate an integration boundary. Explicit constraints and regression checks make that boundary inspectable.

We also standardized terminology: “domain” means a web hostname; responsibility boundaries use “role” or “area.” Ambiguous labels can become ambiguous permissions and navigation.

Preserve the operational story

The goal was a shorter path from diagnosis to response, with prepared installation material and a recovery path when something fails. Monitoring, detection, blocking, backup and restore verification belong to the same operational story.

This series follows six incidents from that rebuild. Next: a weekly backup repeatedly recreating a roughly 5 GB full archive.

Takeaway: Identify which “internal” structures are contracts with other running systems. Modernizing around those contracts can be safer than modernizing through them.

About this series: Adapted from InfraGuard engineering records. Measurements describe the recorded environment, not product-wide benchmarks. AI was used to draft and translate this article.

Disclosure: Solution Market develops and sells InfraGuard. This is our engineering devlog, not an independent review. InfraGuard is a self-hosted infrastructure operations and security platform. Project · Documentation · Solution Market