# Zerobase

*/Startups/Zerobase*

## Startup Overview

Engineering and FinOps teams bleed cloud budget on idle resources because tracking them demands perfect tagging and exhaustive human audits. This enforcement layer directly intervenes in cloud environments to continuously terminate unattached compute instances and orphaned storage volumes. Instead of compiling lists of suspected waste, it actively prunes the infrastructure.

Traditional cost management tools like VMware Aria Cost, AWS Cost Explorer, and manual FinOps audits act as read-only reporting dashboards that require strict resource tagging protocols to flag bloat. By contrast, this execution engine operates completely independent of resource tags. It maps the actual dependency graph of cloud infrastructure to isolate dead assets, taking direct action to delete waste rather than passively generating alerts for human review.

## Startup Founding Hypothesis

**Approach**: that continuously terminates unattached compute and orphaned storage volumes
**Competitors**:
- [VMware Aria Cost](/Competitors/VMware_Aria_Cost)
- [AWS Cost Explorer](/Competitors/AWS_Cost_Explorer)
- [manual FinOps audits](/Competitors/manual_FinOps_audits)
**Differentiator2x2**: action-taking rather than read-only, and tag-independent rather than tag-reliant

## Startup Solution Coordinate

**Solution**: [Zerobase Resource Reaper](/Agents/Zerobase_Resource_Reaper)

## Startup Position2x2

```mermaid
quadrantChart
x-axis Tag-Reliant --> Tag-Independent
y-axis Read-Only --> Action-Taking
AWS Cost Explorer: [0.15, 0.15]
VMware Aria Cost: [0.25, 0.35]
Manual FinOps Audits: [0.45, 0.70]
Zerobase: [0.90, 0.85]
```

## Startup Brand

**Voice**: Authoritative technical register with a zero-tolerance attitude toward resource waste.
**Tagline**: Automatically terminate orphaned storage volumes and unattached compute resources.
**Icon Concept**: rack
**Palette Intent**: electric-signal
**Visual Identity**: The visual identity pairs harsh neon greens against deep terminal black to evoke automated script execution, utilizing monospaced typography to reflect server-level precision.
**Archetype Reference**: the-ruler

## Startup Customer Journey

```mermaid
flowchart LR; A[AWS Marketplace Listing] --> B[Read-Only Infrastructure Scanner]; B --> C[Unattached Resource Report]; C --> D[Usage-Metered Subscription]; D --> E[Enterprise Autonomous Platform]; E --> F[ServiceNow Approval Routing]; F --> G[FinOps Manager Champion];
```

## Startup Proof Points

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

**Pilot Goals**:
- Aim for a 30-day proof of value on a single non-production AWS account to identify and autonomously terminate enough orphaned resources to cover the usage-based fees by day 15.
- Aim for a 14-day shadow mode deployment to prove the IO and network traffic analysis correctly identifies 100 percent of unused resources without relying on the company's existing tagging taxonomy.
**Target Metrics**:
- Target: 20 percent reduction in monthly EC2 and EBS spend within the first 30 days
- Aim: 100 percent elimination of unattached, zero-IO staging environments continuously
- Target: 0 production disruptions caused by automated resource termination, validated by pre-deletion snapshots
- Aim: 0 hours spent by engineering teams manually reviewing read-only cloud cost reports
**Target Case Studies**:
- Target: A mid-market SaaS VP of Engineering who continuously eliminates 100 percent of orphaned staging environments without engineers spending hours manually hunting for unattached EBS volumes.
- Target: An Enterprise Cloud Operations Director who recoups 20 percent of monthly AWS spend by autonomously terminating zero-IO compute instances while maintaining strict ServiceNow approval workflows.
- Target: A high-growth Series B CTO who reclaims over $10,000 monthly in cloud waste within 30 days without ever implementing a complex resource tagging taxonomy.
**Testimonial Targets**:
- Target Role: VP of Cloud Infrastructure. Target Sentiment: Relief that they finally have a tool that actively cleans up cloud waste rather than just adding another dashboard of cost reports to their team's backlog.
- Target Role: Chief Technology Officer. Target Sentiment: Absolute confidence in the safety net of automated pre-deletion snapshots, making autonomous deletion an obvious operational choice.
- Target Role: Lead DevOps Engineer. Target Sentiment: Strong appreciation for escaping the administrative busywork of chasing down developers to figure out who owns an untagged compute instance.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: The engine falsely identifies and terminates a critical production resource causing a severe customer outage. · Mitigation Status: in-progress
- Severity: high · Description: Enterprise security teams refuse to grant the sweeping IAM delete permissions required for the product to automatically terminate resources. · Mitigation Status: unmitigated
- Severity: moderate · Description: Cloud providers introduce native tag-independent garbage collection for orphaned volumes eroding the core differentiator. · Mitigation Status: unmitigated
- Severity: low · Description: Undocumented changes to cloud provider resource APIs break the detection logic resulting in delayed terminations and missed savings. · Mitigation Status: mitigated

## Startup Competitors

- [VMware Aria Cost](/Competitors/VMware_Aria_Cost) — Incumbent
- [AWS Cost Explorer](/Competitors/AWS_Cost_Explorer) — Native Tool
- [Manual FinOps Audits](/Competitors/Manual_FinOps_Audits) — Status Quo
- [CloudZero](/Competitors/CloudZero) — Tag Reliant Tool
- [Spot By NetApp](/Competitors/Spot_By_NetApp) — Infrastructure Automation
- [ProsperOps](/Competitors/ProsperOps) — Automated FinOps

## Startup Story Brand

**Hero**:
- **Need**: to be the architect of a self-healing infrastructure, not a nagging cloud bill auditor
- **Want**: to stop paying for orphaned cloud resources without chasing engineers for manual deletions
- **Identity**: the FinOps lead or CTO at a high-growth SaaS company
**Plan**:
- Step: Deploy · Detail: Apply our least-privilege IAM role to your AWS or Azure accounts to begin resource scanning.
- Step: Approve · Detail: Set your automated termination thresholds or route high-risk deletions through Jira or ServiceNow for final sign-off.
- Step: Reclaim · Detail: Watch your cloud bill drop as the system terminates idle compute and snapshots orphaned storage automatically.
**Guide**:
- **Empathy**: You shouldn't still be hunting for orphaned volumes in spreadsheets. AWS Cost Explorer wasn't built to take the action of actually deleting the waste it finds.
**Problem**:
- **Villain**: Zombie infrastructure
- **External**: AWS Cost Explorer reports show thousands in waste, but unattached EBS volumes and idle EC2 instances remain running because tagging is incomplete.
- **Internal**: You feel like you are losing a battle of attrition against a messy, unmanaged cloud footprint.
- **Philosophical**: Why should engineering talent accept the drudgery of manual cleanup when compute waste is a solvable math problem?
**Success**: Your cloud environment stays lean and compliant automatically. Monthly savings exceed platform costs in the first week without requiring an engineering sprint.
**One Liner**: What if your cloud waste deleted itself? Zerobase monitors real-time I/O to automatically terminate orphaned compute and storage, slashing your AWS bill without manual tagging.
**Positioning**:
- **So That**: eliminate 100% of orphaned resources without human intervention
- **Unlike**: read-only AWS Cost Explorer reports
- **For Whom**: FinOps leads at mid-market SaaS companies
- **Category**: Autonomous cloud cost management
**Call To Action**:
- **Direct**: Run a savings scan
- **Transitional**: Review termination logic
**Failure Stakes**:
- Wasting 20% of your cloud budget on idle disks
- Endless back-and-forth between Finance and DevOps
- Security risks from unmanaged, unpatched staging instances
**Transformation**:
- **To**: free to scale infrastructure strategy, no longer cleaning up abandoned volumes
- **From**: a FinOps lead begging for tagging compliance
**Controlling Idea**: Cloud waste should be terminated automatically based on activity, not tracked manually with tags.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: What if your cloud waste deleted itself? Zerobase monitors real-time I/O to automatically terminate orphaned compute and storage, slashing your AWS bill without manual tagging.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 919400aee5bd9cbf

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Autonomous cloud cost management for FinOps leads at mid-market SaaS companies. Unlike read-only AWS Cost Explorer reports — eliminate 100% of orphaned resources without human intervention.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: bbd61da049391910

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: AWS Cost Explorer reports show thousands in waste, but unattached EBS volumes and idle EC2 instances remain running because tagging is incomplete.
Solution: What if your cloud waste deleted itself? Zerobase monitors real-time I/O to automatically terminate orphaned compute and storage, slashing your AWS bill without manual tagging.
Customer: FinOps leads at mid-market SaaS companies
Unlike: read-only AWS Cost Explorer reports
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 703e8333a7199f73

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

**Pain**: AWS Cost Explorer reports show thousands in waste, but unattached EBS volumes and idle EC2 instances remain running because tagging is incomplete.
**Metrics**: Target: Your cloud environment stays lean and compliant automatically. Monthly savings exceed platform costs in the first week without requiring an engineering sprint.
**Rendered**: Pain: AWS Cost Explorer reports show thousands in waste, but unattached EBS volumes and idle EC2 instances remain running because tagging is incomplete.
Economic buyer: Cloud Operations Engineer
Metrics: Target: Your cloud environment stays lean and compliant automatically. Monthly savings exceed platform costs in the first week without requiring an engineering sprint.
Competition: read-only AWS Cost Explorer reports
**Mechanism**: spine-derived-v1
**Competition**: read-only AWS Cost Explorer reports
**Economic Buyer**: Cloud Operations Engineer
**Vocab Fingerprint**: da2ffb13c7161723

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Autonomous cloud cost management for FinOps leads at mid-market SaaS companies

FinOps leads at mid-market SaaS companies — AWS Cost Explorer reports show thousands in waste, but unattached EBS volumes and idle EC2 instances remain running because tagging is incomplete. What if your cloud waste deleted itself? Zerobase monitors real-time I/O to automatically terminate orphaned compute and storage, slashing your AWS bill without manual tagging.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 4ba72f82c56f6e83

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Autonomous cloud cost management. What if your cloud waste deleted itself? Zerobase monitors real-time I/O to automatically terminate orphaned compute and storage, slashing your AWS bill without manual tagging. Serves FinOps leads at mid-market SaaS companies.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 0fe92df41c68c338

## Neighborhood

### Candidate solutions

- [Untangle Intercompany Eliminations](/Problems/Untangle_Intercompany_Eliminations) — candidate solution for · Problems

### What it offers

- [Ledger Offset](/Services/Ledger_Offset) — offers · Services
- [Zerobase Resource Reaper](/Agents/Zerobase_Resource_Reaper) — offers · Agents
- [Ledger Prism](/Agents/Ledger_Prism) — offers · Agents

### Competitors

- [CloudZero](/Competitors/CloudZero) — competes with · Competitors
- [VMware Aria Cost](/Competitors/VMware_Aria_Cost) — competes with · Competitors
- [ProsperOps](/Competitors/ProsperOps) — competes with · Competitors
- [Spot By NetApp](/Competitors/Spot_By_NetApp) — competes with · Competitors
- [Manual FinOps Audits](/Competitors/Manual_FinOps_Audits) — competes with · Competitors
- [AWS Cost Explorer](/Competitors/AWS_Cost_Explorer) — competes with · Competitors
- [Oracle NetSuite](/Competitors/Oracle_NetSuite) — competes with · Competitors
- [Manual Excel Spreadsheets](/Competitors/Manual_Excel_Spreadsheets) — competes with · Competitors
- [BlackLine](/Competitors/BlackLine) — competes with · Competitors
- [Manual Excel Diffs](/Competitors/Manual_Excel_Diffs) — competes with · Competitors
- [BlackLine Financial Close](/Competitors/BlackLine_Financial_Close) — competes with · Competitors
- [Excel VLOOKUPs](/Competitors/Excel_VLOOKUPs) — competes with · Competitors
- [manual spreadsheet diffs](/Competitors/manual_spreadsheet_diffs) — competes with · Competitors
- [Manual Excel VLOOKUPs](/Competitors/Manual_Excel_VLOOKUPs) — competes with · Competitors
- [Oracle NetSuite Consolidation](/Competitors/Oracle_NetSuite_Consolidation) — competes with · Competitors
- [NetSuite Consolidation](/Competitors/NetSuite_Consolidation) — competes with · Competitors
- [Manual VLOOKUP Diffs](/Competitors/Manual_VLOOKUP_Diffs) — competes with · Competitors
- [Manual Excel Diffing](/Competitors/Manual_Excel_Diffing) — competes with · Competitors
- [NetSuite consolidation modules](/Competitors/NetSuite_consolidation_modules) — competes with · Competitors

### Embodies

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

### Composed of

- [Currency Variance Worker](/Agents/Currency_Variance_Worker) — composes · Agents
- [Semantic Matching Agent](/Agents/Semantic_Matching_Agent) — composes · Agents
- [Unmapped Ledger Engine](/Agents/Unmapped_Ledger_Engine) — composes · Agents
- [Trial Balance API](/Agents/Trial_Balance_API) — composes · Agents
- [Elimination Schedule Service](/Services/Elimination_Schedule_Service) — composes · Services
- [Journal Writeback SDK](/Agents/Journal_Writeback_SDK) — composes · Agents
- [Semantic Mapping Agent](/Agents/Semantic_Mapping_Agent) — composes · Agents
- [Ledger Ingestion API](/Agents/Ledger_Ingestion_API) — composes · Agents

### Who it serves

- [Accounting Firm](/CompanyTypes/Accounting_Firm) — serves · CompanyTypes

### Similar Startups

- [Lunarwaste](/Startups/Lunarwaste) — similar · Startups
- [Wasteshade](/Startups/Wasteshade) — similar · Startups
- [Plateauedge](/Startups/Plateauedge) — similar · Startups
- [Problem](/Startups/Problem) — similar · Startups
- [Wasterpulse](/Startups/Wasterpulse) — similar · Startups
- [Bleed](/Startups/Bleed) — similar · Startups
- [Accumulationsoar](/Startups/Accumulationsoar) — similar · Startups
- [Stackearance](/Startups/Stackearance) — similar · Startups
- [Astralkerf](/Startups/Astralkerf) — similar · Startups
- [Hexcycle](/Startups/Hexcycle) — similar · Startups
- [Eonoof](/Startups/Eonoof) — similar · Startups
- [Aeroarc](/Startups/Aeroarc) — similar · Startups
- [Quintorg](/Startups/Quintorg) — similar · Startups
- [Wastint](/Startups/Wastint) — similar · Startups
- [Allocateloft](/Startups/Allocateloft) — similar · Startups
- [Crecess](/Startups/Crecess) — similar · Startups
- [Syspir](/Startups/Syspir) — similar · Startups
- [Abdicant](/Startups/Abdicant) — similar · Startups
- [Wasterealm](/Startups/Wasterealm) — similar · Startups
- [Maplesalvage](/Startups/Maplesalvage) — similar · Startups