Skip to content

Home

Jump to bottom
Muhammad Umer Nadeem edited this page May 17, 2026 · 1 revision

Welcome to the graveyard wiki!

Product Concept

Graveyard runs unified pre-deployment checks — security, tests, infra, cost, dependencies, compliance — and returns a single GO/NO-GO decision.

Last updated: 2026-04-30

Core Features (v1 MVP)

1. Test Verification

  • Reads JUnit XML, Cypress results, Postman reports
  • Checks: did all tests pass? Is coverage above threshold?
  • Configurable thresholds: "block if coverage < 80%"

2. Security Scanning

  • Integrates with Trivy (container vulnerabilities)
  • Integrates with Checkov (IaC misconfigurations)
  • Configurable: "block on CRITICAL, warn on HIGH"

3. K8s Configuration Checks

  • Resource limits and requests set?
  • HPA (autoscaling) configured?
  • Liveness/readiness probes defined?
  • Secrets management (not hardcoded)?

4. Dependency Health

  • Pings critical third-party APIs before deploy
  • Checks public status pages (Stripe, Twilio, AWS, etc.)
  • "Don't deploy payment-service if Stripe is degraded"

5. Cost Estimation

  • Compares new deployment resource requests vs. current
  • Estimates monthly cost impact: "+$47/mo"
  • Configurable budget alerts

6. Compliance Checks

  • CIS Benchmark alignment
  • RBAC properly configured?
  • Logging enabled?
  • Backup running?

User Flow

Developer pushes code → CI/CD runs → Before deploy step:
    ↓
graveyard check (CLI) or Graveyard API call
    ↓
Graveyard runs all configured checks in parallel
    ↓
Returns: GO ✅ / CAUTION ⚠️ / BLOCK 🛑
    ↓
If BLOCK: deployment halted, team notified via Slack + mobile push
If CAUTION: deployment proceeds with warning + audit log entry
If GO: deployment proceeds normally

Delivery Formats

Format Use Case
CLI (graveyard check) Local dev, CI/CD integration
Web Dashboard Team overview, history, trends
Mobile App (Flutter) Deploy approval on the go, push notifications
API Integration into IDPs, custom workflows
Slack/Discord Bot Team notifications, quick approvals

What Makes This Different

Individual tools exist for each check (Trivy, Checkov, CI/CD status, etc.), but nobody combines them into one unified pre-deployment decision. Graveyard's value is the integration and the decision, not any single check.

See also

Clone this wiki locally