Productized evidence services

Services that turn change into verifiable record.

EdgeRecord starts as a focused service business. Each engagement has a fixed scope, a defined output, and a record the business owns at the end. The path begins with one change and grows into recurring record operations and platform access.

Entry engagement

Change Evidence Sprint.

A fixed-scope engagement built around one upcoming change — migration, vendor visit, firewall change, cloud update, device deployment, or incident review. The output is a plain-English evidence report showing what changed, what was verified, and what still needs attention.

• Baseline of systems, accounts, configurations, and dependencies in scope.
• Recorded change events with operator, approval, and supporting evidence.
• Verified after-state with drift and side-effects called out explicitly.
• Receipt as PDF for humans and JSON for systems.

Foundation

System Snapshot.

A current-state evidence bundle for the assets, configurations, accounts, vendors, and recovery assumptions that matter most. Useful before a migration, an MSP change, an acquisition, or a planned modernization.

• Before-state record across the systems in scope.
• Dependency and accountable-owner matrix.
• Portable PDF and JSON export.

Control

Vendor Work Record.

A clean record of who accessed what, why, when access expired, and what changed during the engagement. Useful for any operation where outside parties touch the systems.

• Access scope, approver, and expiration recorded.
• Before and after change log for each session.
• Closure checklist signed by operator and vendor.

Response

Incident Evidence Package.

A timestamped narrative of what changed in the hours and days before an incident, with evidence attached at each step. Built for the post-incident review most teams have to assemble from scratch.

• Reconstructed timeline from operator notes, tickets, and system state.
• Verified hash chain over the assembled evidence.
• Plain-English summary readable by insurers and counsel.

Continuity

Monthly Change Record.

A recurring engagement that produces an ongoing record of meaningful change across the systems in scope. Useful when the business needs to demonstrate operational continuity month after month without standing up a heavy monitoring stack.

• Monthly recorded change events with operator and scope.
• Quarterly recovery readiness review.
• Year-over-year exports for insurance and audit.

Platform

API and Integration Access.

For teams that already have process discipline and want to feed structured events from their own scripts, MSPs, vendors, or future automation. The API accepts events, returns receipts, and exposes verification endpoints.

• Event ingest with operator and approval metadata.
• Receipt issuance and verification endpoints.
• Portable record export with hash chain.

Start here

The first engagement is one change.

If there is an upcoming change that the business needs a defensible record of — or an incident that needs reconstruction — the Change Evidence Sprint is the entry point.