Superkabe Documentation
Production-hardened monitoring and protection for modern outbound infrastructure.
What is Superkabe?
Superkabe is a control layer for multi-domain, multi-mailbox outbound email infrastructure. We don't optimize volume— we prevent irreversible damage.
Modern outbound teams run:
- 3–10 domains
- 3+ mailboxes per domain
- 20–30 emails per mailbox per day
- Structured ICP-based campaign routing
Superkabe monitors bounce rates, failure patterns, and domain health to protect your infrastructure before reputation damage becomes irreversible.
Getting Started
Quick Start Guide
Set up your account, connect platforms, and start protecting infrastructure
Configuration
Threshold tuning, system modes, and integration setup
Infrastructure Assessment
Automated health check on onboarding — DNS, bounce rate, connection validation
Deployment Checklist
Production deployment steps and verification procedures
Core Systems
Monitoring System
60-second health checks, tiered thresholds, sliding windows, and auto-pause logic
Execution Gate
GREEN/YELLOW/RED lead classification and pre-send validation
Risk Scoring
Bounce rate, engagement, and infrastructure signals combined into risk scores
State Machine
Entity lifecycle states and valid transitions for mailboxes, domains, and leads
Warmup & Recovery
5-phase healing pipeline and automated mailbox rehabilitation
Platform Rules
System modes (observe/suggest/enforce), thresholds, and enforcement mechanisms
Technical Architecture
System design, data flow, and infrastructure overview
Data Sync Coverage
What data syncs from each platform and what starts at zero
Integrations
Smartlead Integration
API key setup, webhook config, campaign sync, and bounce monitoring
Instantly Integration
API v2 sync, campaign management, and per-mailbox analytics
EmailBison Integration
Campaign sync, sender-email management, and warmup control
Clay Integration
Webhook ingestion for enriched leads with automatic validation and routing
Slack Integration
Real-time infrastructure alerts delivered to your Slack workspace
API Integration
REST API reference for programmatic lead ingestion and platform access
Multi-Platform Sync
How Superkabe syncs across Smartlead, Instantly, and EmailBison simultaneously
Help Center
Email Validation
How the hybrid validation layer works — internal checks + MillionVerifier API
Auto-Healing Pipeline
5-phase recovery: pause → quarantine → restricted → warm → healthy
Why Is My Mailbox In Quarantine?
DNS health check phase — what keeps you stuck and how to fix it
Mailbox Rotation
Automatic standby mailbox swapping when a sender is paused
Status Labels Explained
Every status across mailboxes, domains, campaigns, and leads
Bounce Classification
Hard, soft, and transient bounces — what each means for your reputation
Load Balancing
Effective load calculation and mailbox distribution
Optimization Suggestions
What/Why/How recommendations for rebalancing infrastructure
Why Is My Campaign Paused?
Auto-pause when all mailboxes are unhealthy — how to resume
Connection Errors
Troubleshoot SMTP/IMAP failures, OAuth expiry, and disconnects
Infrastructure Score
How the composite health score is calculated from DNS, bounces, and engagement
24/7 Monitoring
Automated background syncing and continuous health checks
Notifications
Alert types, severity levels, and configuration
Audit Logs
Full action history — pauses, resumes, rotations, and automated decisions
Analytics
Open rate, click rate, reply rate, bounce rate trends
Billing
Manage your plan, billing, and subscription
Account Management
Account settings, team, and organization
Core Principles
1. Protection Over Volume
We prioritize infrastructure safety over send volume. A burned domain costs more than missed opportunities.
2. Tiered Escalation
Early warnings (3 bounces) before hard stops (5 bounces) give operators time to react.
3. Ratio-Based Scaling
Domain health uses percentages (30% warning, 50% pause) to scale with infrastructure size.
4. Signal Separation
Hard signals (bounces) trigger blocks. Soft signals (velocity) only log. Clean mailboxes stay active.