PRODUCTS
Three precision tools. One connected stack.
Acheron Vault for backup readiness verification. Blackglass for Linux operational integrity. Charon Gate for webhook reliability. Tools for free utilities.
Acheron Vault EARLY ACCESS
Backup readiness verification — ephemeral restore, documented proof of recoverability. Are your backups actually recoverable?
Blackglass
Linux operational integrity — SSH posture, fleet baselines, drift with severity, audit-ready exports. Live at blackglasssec.com.
Charon Gate
Webhook reliability — durable ingest, exponential retries with jitter, dead-letter queue, manual replay with lineage. Live at charongate.com.
At a glance
Three independent tools. Pick the row that matches your gap.
| Product | Core problem | Best for | Status | Next step |
|---|---|---|---|---|
| Acheron Vault | Backup recoverability proof | Teams who cannot prove restores work under real conditions | Early access beta | Explore → |
| Blackglass | Linux drift, posture, audit evidence | Platform and security teams managing Linux fleets | Live · blackglasssec.com | Explore → |
| Charon Gate | Webhook ingest, retries, DLQ, replay | Teams receiving inbound webhooks from third parties | Live · charongate.com | Explore → |
How the three tools close the loop.
Each product solves a distinct problem. Used together, they form a self-reinforcing infrastructure layer: when one detects a risk, the others respond automatically.
Acheron Vault detects a restore failure → Charon Gate routes the alert
When Acheron Vault completes a verification run and the restore fails, it fires a signed event. Charon Gate ingests the event, queues it durably, and guarantees delivery to your alerting destination — Slack, PagerDuty, or your own endpoint — regardless of downstream availability at the moment of failure.
Blackglass detects drift → Charon Gate routes the alert → Acheron Vault runs a health check
When Blackglass detects an unauthorized configuration change on a Linux host, it fires a signed webhook to Charon Gate. Charon Gate delivers the alert to your team and simultaneously triggers Acheron Vault to run a backup health check on the affected target — so you have both an incident alert and a fresh recoverability report at the same moment, without any manual steps in the critical path.
Infrastructure events trigger verification → not just clocks
Most teams verify backups on a fixed cron schedule. With Charon Gate routing your infrastructure events, you can trigger Acheron Vault immediately after a major database migration, a deployment pipeline, or any other event that warrants a fresh recoverability check — replacing fragile time-based schedules with event-driven verification.
Which first?
Where should I start?
Start with Acheron Vault if you cannot answer the question “will our backups restore under ransomware conditions?” with documented evidence. Start with Blackglass if the gap is Linux fleet drift, SSH posture, and audit evidence. Start with Charon Gate if the gap is inbound webhooks — providers that retry inconsistently, deploys that drop events, or DLQ-and-replay that is missing.
What does Acheron Vault do?
Acheron Vault verifies your backups are actually recoverable. It spins up an ephemeral sidecar, performs a real restore from your backup storage, validates the result, and returns a timestamped proof report. Currently in controlled beta — join the beta.
What does Blackglass do?
Blackglass delivers Linux operational integrity: SSH posture, fleet baselines, drift detection with severity, and audit-ready evidence exports. Live at blackglasssec.com.
What does Charon Gate do?
Charon Gate is a webhook reliability layer: durable ingest, exponential retries with jitter, a dead-letter queue, and manual replay with lineage tracked end-to-end. Live at charongate.com.
How do I get access?
Acheron Vault is in controlled beta — contact us to join. Blackglass and Charon Gate access is handled via the contact form. Onboarding tracks are available for Blackglass and Charon Gate.