# Radock

*/Startups/Radock*

## Startup Overview

This continuous remediation engine detects and corrects infrastructure drift across multi-cloud environments. By monitoring live cloud configurations against declared code states, the system automatically applies infrastructure-as-code corrections the moment deviations occur. Engineering teams use it to eliminate the persistent vulnerability gap between what is version-controlled and what is actually running in production without triggering manual incident responses.

Traditional delivery pipelines and control planes like Terraform Cloud, Spacelift, and env0 rely on engineers to manually review and approve state reconciliation plans. In contrast, this platform operates with zero human intervention by design, instantly executing fixes for unauthorized configuration changes to maintain compliance. Organizations abandon manual remediation workflows and adopt a model priced purely per successful state remediation, paying only for resolved infrastructure discrepancies rather than passive compute time or user seats.

## Startup Founding Hypothesis

**Approach**: that continuously remediates infrastructure drift across multi-cloud environments
**Competitors**:
- [Terraform Cloud](/Competitors/Terraform_Cloud)
- [manual state reconciliation](/Competitors/manual_state_reconciliation)
- [Spacelift](/Competitors/Spacelift)
- [env0](/Competitors/env0)
**Differentiator2x2**: zero-intervention by design and priced purely per successful state remediation

## Startup Solution Coordinate

**Solution**: [Radock Drift Resolver](/Services/Radock_Drift_Resolver)

## Startup Position2x2

```mermaid
quadrantChart
  x-axis "Manual / Workflow-Driven" --> "Zero-Intervention"
  y-axis "Seat / Run Pricing" --> "Priced per Remediation"
  quadrant-1 "Automated & Outcome-Priced"
  quadrant-2 "Manual & Outcome-Priced"
  quadrant-3 "Legacy Operations"
  quadrant-4 "Automated & Flat-Rate"
  Terraform Cloud: [0.3, 0.2]
  Manual State Reconciliation: [0.1, 0.1]
  Spacelift: [0.4, 0.25]
  env0: [0.45, 0.25]
  Radock: [0.85, 0.85]
```

## Startup Offer

**Proof**:
- Targeting 100% automated resolution of unintended infrastructure drift for mid-market DevOps teams.
- Aiming to reduce mean-time-to-recovery (MTTR) for unauthorized configuration changes to under 90 seconds.
- Designed to safely process thousands of concurrent state checks per minute across distributed cloud environments.
**Tiers**:
- Name: On-Demand Remediation · Price: ~$2.50–$5.00 per remediation · Inclusions: Continuous multi-cloud drift monitoring and unlimited state checks, billed strictly per successful automated reversion to your declared infrastructure baseline.
- Name: High-Velocity Blocks · Price: ~$0.75–$1.50 per remediation · Inclusions: Pre-purchased blocks starting at 5,000 automated remediation events per month, designed for highly dynamic environments with frequent unauthorized state mutations.
- Name: Enterprise Retainer · Price: ~$35k–$70k/yr · Inclusions: Unlimited automated remediations across up to 100 cloud accounts, intended to support self-hosted runners, custom RBAC integrations, and dedicated VPC deployments.
**Guarantee**: If an infrastructure state change is detected but fails to be successfully reverted to its declared code baseline, you are not charged for the attempt, and the event is immediately escalated to a dedicated support engineer for manual review.
**Business Function**: Maintain
**Objection Handlers**:
- Will this overwrite intentional emergency hotfixes?: Radock is designed to integrate with your change management tools to pause autonomous remediation during approved incident response windows.
- How is this different from Terraform Cloud or Spacelift?: Existing tools detect drift and notify your team; Radock is built to autonomously execute the fix without waiting for a developer to manually approve a pipeline run.
- Can we restrict its blast radius?: Yes, the system intends to enforce strict resource-tagging policies, allowing you to limit autonomous writes to specific staging environments or low-risk resource types.
- We cannot give write access to a third-party SaaS.: Radock plans to offer a 'dry-run only' mode that automatically generates the exact GitOps pull request required to fix the drift, leaving final merge control with your team.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Authoritative technical register with an uncompromising focus on structural integrity.
**Tagline**: Enforces multi-cloud state and continuously resolves infrastructure drift.
**Icon Concept**: ratchet
**Palette Intent**: electric-signal
**Visual Identity**: The visual identity relies on sharp neon green terminal accents against deep slate backgrounds, evoking automated command execution and strict alignment.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: B2B → Platform Engineering Leadership → Site Reliability Engineers
**Gtm Motion**: Acquires initial users via a self-serve tier for individual infrastructure engineers facing manual state reconciliation tasks. Expands organization-wide via a purely usage-based contract that bills solely per successful drift remediation across multi-cloud infrastructure.
**Agent Channel**: Designed to list in the LangChain tool registry and the GitHub Copilot Extensions catalog, exposing the drift remediation engine as a callable capability for autonomous DevOps agents.
**Primary Channel**: Intended placement in the HashiCorp Integration Directory and targeted search queries for 'automated Terraform state reconciliation' where practitioners seek alternatives to manual drift correction.

## Startup Customer Journey

```mermaid
flowchart LR; A[HashiCorp Directory] --> B[Self-Serve Workspace]; B --> C[State Reconciliation Task]; C --> D[Drift Remediation Engine]; D --> E[Usage-Based Contract]; E --> F[Multi-Cloud Infrastructure]; F --> G[LangChain Registry];
```

## Startup Proof Points

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Pilot Goals**:
- 14-day dry-run pilot scoped to a specific staging environment to prove Radock successfully generates accurate GitOps pull requests for 100% of injected infrastructure drift events.
- 30-day live autonomous pilot restricted via tagging to low-risk resource types, aiming to demonstrate sub-90-second MTTR for simulated state mutations with zero disruption to active deployments.
**Target Metrics**:
- Target: <90 seconds Mean-Time-To-Recovery (MTTR) for reverting unauthorized configuration changes.
- Aim: 100% automated resolution rate for unintended infrastructure drift without manual developer intervention.
- Target: Zero false-positive automated overwrites during designated emergency hotfix windows.
- Aim: 5,000+ automated remediation events processed successfully per month in highly dynamic cloud environments.
**Target Case Studies**:
- Mid-market SaaS platform (Platform Engineering Lead) validates Radock by fully automating drift remediation across 50+ cloud accounts, eliminating manual Terraform state reconciliations.
- Highly regulated FinTech scale-up (Cloud Security Architect) adopts Radock in 'dry-run only' mode, generating exact GitOps pull requests for 100% of detected unauthorized mutations without granting write access to a third-party SaaS.
- High-traffic E-commerce infrastructure (DevOps Manager) utilizes Radock's High-Velocity Blocks to handle frequent unauthorized state mutations across dynamic staging environments while safely pausing autonomous writes during approved incident response windows.
**Testimonial Targets**:
- VP of Platform Engineering highlighting the operational shift from receiving hundreds of unactionable drift alerts to experiencing silent, autonomous baseline restorations.
- Lead Site Reliability Engineer confirming the effectiveness and safety of Radock's blast-radius controls and strict resource-tagging policies.
- Cloud Operations Director validating the budget efficiency of a usage-metered model where they pay strictly per successful state reversion rather than a flat fee for static monitoring.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Zero-intervention auto-remediation applies incorrect state changes without human oversight and destroys production environments. · Mitigation Status: unmitigated
- Severity: high · Description: HashiCorp restricts API access or alters Terraform state file encryption to intentionally lock out third-party remediation engines. · Mitigation Status: in-progress
- Severity: moderate · Description: Pricing purely per successful remediation incentivizes customers to permanently fix root pipeline drift causes, steadily shrinking billable events. · Mitigation Status: unmitigated
- Severity: low · Description: DevOps teams resist initial adoption due to a cultural preference for manual approval gates before infrastructure state modifications occur. · Mitigation Status: in-progress

## Startup Competitors

- [Terraform Cloud](/Competitors/Terraform_Cloud) — Incumbent
- [Manual State Reconciliation](/Competitors/Manual_State_Reconciliation) — Status Quo
- [Spacelift](/Competitors/Spacelift) — IaC Platform
- [env0](/Competitors/env0) — IaC Platform
- [Scalr](/Competitors/Scalr) — IaC Platform

## Startup Solution Stack

- [Drift Resolution Service](/Services/Drift_Resolution_Service) — Service-as-Software
- [State Reconciliation Agent](/Agents/State_Reconciliation_Agent) — Agent
- [Cloud Authentication Worker](/Agents/Cloud_Authentication_Worker) — Agent
- [Drift Detection Engine](/Software/Drift_Detection_Engine) — Software
- [Infrastructure State API](/Software/Infrastructure_State_API) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the architect of systems that self-heal, not a firefighter chasing drift
- **Want**: to maintain a perfect alignment between Terraform code and live cloud infrastructure
- **Identity**: the DevOps lead at a mid-market multi-cloud organization
**Plan**:
- Step: Declare · Detail: Define your infrastructure baseline in your existing GitOps repository and set your enforcement boundaries.
- Step: Validate · Detail: Radock continuously scans live resources against your state files to detect every unauthorized configuration change.
- Step: Enforce · Detail: The system automatically triggers a remediation run to overwrite drift and restore your intended architecture.
**Guide**:
- **Empathy**: Does your deployment pipeline still stall because of unrecorded manual changes in the AWS console?
**Problem**:
- **Villain**: manual state reconciliation
- **External**: Infrastructure drift triggers constant PagerDuty alerts as AWS and Azure configurations diverge from the Terraform state
- **Internal**: You feel like a janitor cleaning up unauthorized cloud console clicks instead of building features
- **Philosophical**: Engineers deserve stable systems that enforce their own integrity — not a life of manual patch-work.
**Success**: Your infrastructure remains in a perpetual state of compliance, with drift resolved automatically before your team even sees an alert.
**One Liner**: Every hour, DevOps teams lose time to infrastructure drift. Radock autonomously remediates state mutations so cloud environments stay perfectly aligned with code.
**Positioning**:
- **So That**: unauthorized cloud changes are fixed without developer intervention
- **Unlike**: Terraform Cloud notifications
- **For Whom**: mid-market DevOps leads
- **Category**: Autonomous Infrastructure Remediation
**Call To Action**:
- **Direct**: Run a remediation
- **Transitional**: Download a drift report
**Failure Stakes**:
- Security vulnerabilities from open ports
- Cloud spend spikes from unmanaged resources
- Critical production downtime
**Transformation**:
- **To**: managing through autonomous system enforcement instead of manual drift hunting
- **From**: a DevOps engineer manually syncing Terraform files
**Controlling Idea**: Infrastructure code must be an enforced reality, not just a suggestion.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Every hour, DevOps teams lose time to infrastructure drift. Radock autonomously remediates state mutations so cloud environments stay perfectly aligned with code.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: a303c32357cabfdb

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Autonomous Infrastructure Remediation for mid-market DevOps leads. Unlike Terraform Cloud notifications — unauthorized cloud changes are fixed without developer intervention.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 9edc8d8058093084

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Infrastructure drift triggers constant PagerDuty alerts as AWS and Azure configurations diverge from the Terraform state
Solution: Every hour, DevOps teams lose time to infrastructure drift. Radock autonomously remediates state mutations so cloud environments stay perfectly aligned with code.
Customer: mid-market DevOps leads
Unlike: Terraform Cloud notifications
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 0631febedfd55911

## Startup Token M E D D P I C C

**Pain**: Infrastructure drift triggers constant PagerDuty alerts as AWS and Azure configurations diverge from the Terraform state
**Metrics**: Target: Your infrastructure remains in a perpetual state of compliance, with drift resolved automatically before your team even sees an alert.
**Rendered**: Pain: Infrastructure drift triggers constant PagerDuty alerts as AWS and Azure configurations diverge from the Terraform state
Economic buyer: Platform Engineering Leadership
Metrics: Target: Your infrastructure remains in a perpetual state of compliance, with drift resolved automatically before your team even sees an alert.
Competition: Terraform Cloud notifications
**Mechanism**: spine-derived-v1
**Competition**: Terraform Cloud notifications
**Economic Buyer**: Platform Engineering Leadership
**Vocab Fingerprint**: 6e981745aa01909b

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Autonomous Infrastructure Remediation for mid-market DevOps leads

mid-market DevOps leads — Infrastructure drift triggers constant PagerDuty alerts as AWS and Azure configurations diverge from the Terraform state Every hour, DevOps teams lose time to infrastructure drift. Radock autonomously remediates state mutations so cloud environments stay perfectly aligned with code.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 6e60b10c6fc34b6b

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Autonomous Infrastructure Remediation. Every hour, DevOps teams lose time to infrastructure drift. Radock autonomously remediates state mutations so cloud environments stay perfectly aligned with code. Serves mid-market DevOps leads.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: aea4003a887fc81f

## Neighborhood

### Candidate solutions

- [Grower Packout Settlement Disputes](/Problems/Grower_Packout_Settlement_Disputes) — candidate solution for · Problems

### What it offers

- [Radock Drift Resolver](/Services/Radock_Drift_Resolver) — offers · Services

### Composed of

- [State Reconciliation Agent](/Agents/State_Reconciliation_Agent) — composes · Agents
- [Drift Resolution Service](/Services/Drift_Resolution_Service) — composes · Services
- [Cloud Authentication Worker](/Agents/Cloud_Authentication_Worker) — composes · Agents
- [Drift Detection Engine](/Software/Drift_Detection_Engine) — composes · Software
- [Infrastructure State API](/Software/Infrastructure_State_API) — composes · Software

### Embodies

- [Service-as-Software](/Theses/Service-as-Software) — embodies · Theses

### Competitors

- [Manual State Reconciliation](/Competitors/Manual_State_Reconciliation) — competes with · Competitors
- [Scalr](/Competitors/Scalr) — competes with · Competitors
- [Terraform Cloud](/Competitors/Terraform_Cloud) — competes with · Competitors
- [Spacelift](/Competitors/Spacelift) — competes with · Competitors
- [env0](/Competitors/env0) — competes with · Competitors

### Similar Startups

- [Verton](/Startups/Verton) — similar · Startups
- [Beadfield](/Startups/Beadfield) — similar · Startups
- [Forgebluff](/Startups/Forgebluff) — similar · Startups
- [Engineharbor](/Startups/Engineharbor) — similar · Startups
- [Agentsarc](/Startups/Agentsarc) — similar · Startups
- [Architecturepace](/Startups/Architecturepace) — similar · Startups
- [Entropyguild](/Startups/Entropyguild) — similar · Startups
- [Codedrift](/Startups/Codedrift) — similar · Startups
- [Baseline](/Startups/Baseline) — similar · Startups
- [Cubeintractable](/Startups/Cubeintractable) — similar · Startups
- [Entropyship](/Startups/Entropyship) — similar · Startups
- [Lumechanic](/Startups/Lumechanic) — similar · Startups
- [Apexhammer](/Startups/Apexhammer) — similar · Startups
- [Pylonrange](/Startups/Pylonrange) — similar · Startups
- [Autellar](/Startups/Autellar) — similar · Startups
- [Voltoblem](/Startups/Voltoblem) — similar · Startups
- [Abash](/Startups/Abash) — similar · Startups
- [Baselinedepot](/Startups/Baselinedepot) — similar · Startups
- [Brookill](/Startups/Brookill) — similar · Startups
- [Astralmulti](/Startups/Astralmulti) — similar · Startups