Bring dark code into the light. Hold the system to true.
Production systems accumulate two quiet failures. Logic no one understands anymore. Scope that drifts from the specification it was built against. SolarNorth surfaces the first and measures the second, continuously, and without ever touching your code.
Two failures that compound in the dark.
Logic no one understands anymore.
Every production system older than a few years contains code that nobody on the current team can fully account for. Authors left. Integrations were added under deadline. Documentation fell behind. The logic still runs, still affects outcomes, and still carries risk, but it has gone dark.
Existing tools find bugs and vulnerabilities. None of them answer the question of what no one understands anymore.
Scope that quietly leaves its specification.
Systems rarely fail by breaking. They fail by slowly becoming something other than what they were designed to be. A small change here, a new integration there, an expedient fix that never made it back into the specification. Each deviation is reasonable in isolation.
The sum of eighteen months of reasonable deviations is a system that no longer matches its documented design, its security model, or its compliance posture.
“Sunlight is the best disinfectant.”
Brandeis was writing about finance, but the principle transfers. The corruption that persists is the corruption that nobody can see. SolarNorth treats continuous visibility as the product itself, not as a feature of the product. Everything else, remediation, audit, defense, depends on it.
Two products. One discipline.
SolarNorth is built as two instruments that share a reference. Illuminate produces the baseline. Plumbline holds the system against it. Most organizations start with one and adopt the other as the discipline takes hold.
The diagnostic.
A scoped engagement producing a baseline inventory, ownership map, and risk surfacing for an existing system. Run on inheritance, pre-acquisition, post-reorg, or regulatory trigger.
The ongoing discipline.
Continuous read-only monitoring of a deployed system against a declared scope. Drift is detected as it happens and captured as an audit-ready artifact.
The two products are sold separately. They work better together.
Built for systems people have to defend.
Read-only by design
No write access to customer systems, ever, not under any credential, not in any escalation path. The instrument cannot become the vector.
Single-tenant by default
Observation data never crosses customer boundaries. Customer-deployed option for organizations with sovereignty or residency requirements.
Audit-ready output
Drift events produce artifacts with full attribution, timeline, and scope reference, formatted for regulators, auditors, and counsel.
Dual-readable by design
Structured equivalent of every page available at mcp.solarnorth.work. Same content, two surfaces.
Know what your system does. Know when it changes. Know it with evidence.
That is what SolarNorth is built to produce.