Import a deliberately bounded, metadata-only infrastructure snapshot.
Personal / local infrastructure tooling
Platform State Explorer
Make cloud state searchable without turning the browser into an admin console.
01 / Purpose
A tool with a reason to exist.
A local-first, read-only prototype for exploring point-in-time Azure infrastructure metadata across tenants, subscriptions, Key Vaults, access assignments and reference comparisons. It grew from a recurring operational problem: cloud state exists everywhere, but understanding it should not require opening every resource separately.
Work-inspired, but independently built as a personal/local prototype. It is not an official DataBalk product or active employer deliverable.
Search resources and access assignments quickly without retrieving secret values.
Separate observed state from approved expectations and incomplete evidence.
Keep the tool useful offline while preserving a narrow path for future live checks.
02 / Decisions
The interesting part is why.
Offline first
Most exploration does not need a live cloud session. A fixed local snapshot reduces authentication, availability and privacy risk.
No secret-value path
The inventory schema, importer, API and interface omit secret values by design instead of relying on a UI promise.
Incomplete is not missing
Coverage remains part of the evidence so an inaccessible subscription or failed scan cannot silently become a false absence result.
Exact IDs live separately
Ordinary search stays readable and privacy-conscious; identifiers require a deliberate exact lookup.
03 / Architecture
A deliberate path through the system.
Collect
A guarded inventory process exports only approved Azure metadata and explicit coverage information.
→Validate
Strict schemas, hashes and row-count reconciliation reject incomplete or secret-bearing input.
→Index
A completed snapshot is published atomically into an immutable SQLite run with bounded FTS5 search.
→Explore
A loopback-only React interface provides grouped search, exact-ID lookup, detail views and comparison evidence.
04 / Technology
The working parts.
TypeScriptReactNode.jsFastifySQLiteFTS5PowerShellAzure REST APIs
05 / State & roadmap
What is real now—and what comes next.
- The source, type checks, production builds, privacy checks and 192 automated tests pass.
- Real snapshot import and signed-out browser exploration have been verified locally.
- The immutable Windows package and its embedded payload hashes were independently verified.
- The project remains a personal/local prototype rather than an official employer product.
- A separately approved visible-desktop pilot for the bounded live-read path.
- Metadata-only correlation between application identities and infrastructure access.
- Further search and comparison refinements based on real operator use.
- Any hosted version would require a new company-owned identity and security architecture.