Your revenue doesn't fail. Your system does.

Comorando analyzes payment events in real time, detects churn risk, and recommends and executes optimized actions to help reduce revenue loss risk — before the customer leaves.

Most SaaS lose 3–8% of revenue due to failed payments and poor recovery logic

See how it works

Used by SaaS companies and professionals managing multiple clients

No credit card required · Live in 5 minutes

Plans from $99/month for SaaS · Professional plans from $149/month

If you bill $10,000/month, you're losing between $300 and $800 monthly in unmanaged failed payments.

This is what Comorando would do in production

This is not a technical simulation. It's a decision that directly impacts your revenue.

See a real AI decision — no signup required

Takes 5 seconds · Powered by real Gemma AI

Simulate a real failed payment scenario:

Live system · Handling real payment decision logic

Live decision from Comorando's payment intelligence system

Intercepting event...

AI DECISION RESULT

Churn risk:

This happens silently in most SaaS businesses

Decision trace — how Comorando decided:
Free forever
Live in 5 minutes

Comorando does not process, store, or handle payment credentials. It operates as a decision and event-processing layer on top of existing payment systems.

What Comorando actually does

It acts as a decision layer between your payment system and your users — helping reduce the risk of failed payments becoming lost customers.

Every decision is logged. Every event is traceable. Full audit trail by default.

The problem is not that a payment fails. The problem is not knowing what to do next.

$15,000
Average monthly revenue lost to failed payments
For SaaS businesses with $50K+ MRR (source: industry average)
4.3%
of SaaS revenue lost to payment failures annually
A structural leak quietly compounding every billing cycle
73%
of failed payments never retried manually
Most teams never follow up — the revenue just disappears

In internal testing with simulated failed payment scenarios, Comorando successfully processed retry workflows and reduced manual intervention requirements.

Revenue Intelligence

Not all customers should be treated the same

Comorando evaluates each customer's value, history, and risk before acting. Depending on context, it decides between retry, grace period, or escalation. Not all payment events are treated equally \u2014 because not all customers are.

You're not optimizing payments. You're optimizing decisions about customers.

THE SILENT REVENUE LEAK

Broken events don't fail loudly.
They just disappear.

A payment fails at 2am. Your webhook fires. But the handler has a bug — or a timeout — or a race condition. The customer's plan doesn't downgrade. Your revenue count doesn't update. Three weeks later: surprise churn.

Comorando's decision layer intercepts every event, verifies it, recommends and executes optimized actions based on context, and runs idempotently — even if your handler fails.

BEFORE — fragile, silent failures
payment-webhook.js
// What could go wrong?
if (type === "PAYMENT.FAILED") {
  // ⚠ no idempotency check
  await db.update({ status: "dunning" });
  // ⚠ no retry logic
  await email.send("payment_failed");
  // ⚠ no AI severity check
  // ⚠ silent timeout = lost event
}
AFTER — intelligent, guaranteed
payment-webhook.js
// No npm install. No SDK. Just HTTP.
const res = await fetch('https://api.comorando.com/decisions', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'x-api-key': YOUR_API_KEY
  },
  body: JSON.stringify({ event_type, data: event })
});
// AI severity + retry + idempotency
// + state correction. All of it. ✓
Revenue Agent — Main Differentiator

Meet the AI that watches your
payment pipeline 24/7.

The Revenue Agent is a persistent AI process that monitors every payment event in real time. It classifies severity, scores churn risk, selects the optimal intervention, and executes it — before your customer even notices something went wrong.

It's not a dashboard. It's not a report. It's infrastructure that acts.

1
payment.failed fires
Your payment processor sends a webhook. Comorando intercepts it instantly.
2
Comorando reads customer history
Past failures, plan value, engagement score — all checked before any action is taken.
3
AI recommends the right strategy
Grace period, immediate retry, or escalation — based on context, not guesswork.
4
Action executed automatically
State updated, retry scheduled, notification sent — no manual work required.
5
You get notified. Customer keeps access.
You see exactly what happened and why. Your customer never knew there was a problem.
🧠

AI Severity Classification

Every event is scored by a local Gemma model for risk level, action priority, and churn probability. No external API calls — decisions happen in milliseconds.

🔁

Intelligent Retry Logic

Retries are not blind. The agent adapts timing based on failure type, customer LTV, and risk score. High-value accounts get immediate escalation.

📡

Real-Time Event Interception

Hooks into PayPal, Stripe, and custom webhooks. Intercepts events before your handler runs. Guarantees exactly-once execution via Redis idempotency.

📉

Churn Prediction Cron

Every 24 hours, the agent scans your org activity for churn signals: login gaps, usage drops, failed payments. Flags at-risk accounts before they cancel.

🗃️

Org Memory Layer

The agent remembers each organization's history: past failures, retry outcomes, LTV, engagement score. Decisions improve over time as context accumulates.

📊

Outcome Dashboard

Every AI decision is logged: severity, action taken, model used, risk score, result. Full audit trail. See exactly what happened and why.

From broken event to corrected state in <100ms.
1

Event fires

A payment failure, cancellation, or system event hits your webhook endpoint or is sent directly to Comorando's API.

2

AI decides

Gemma classifies severity and risk. The Revenue Agent selects the optimal action — retry, grace period, or escalation.

3

Executed once

Redis-backed idempotency guarantees the action runs exactly once. Duplicate webhooks are silently ignored.

4

State corrected

Your database is updated, emails are triggered, and the outcome is logged. No manual intervention. No missed events.

How it works in 60 seconds

One API call. That's the integration.

No SDK, no npm install. When a payment fails in PayPal, send the event to Comorando. Everything else — AI classification, retry scheduling, state correction — happens automatically.

REQUEST — send the failed payment event
curl
curl -X POST https://api.comorando.com/decisions \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: ck_your_key_here' \
  -d '{
    "event_type": "payment.failed",
    "event_id": "paypal-evt-abc123",
    "data": {
      "customer_email": "user@example.com",
      "amount": 79.00,
      "currency": "USD",
      "failure_reason": "insufficient_funds"
    }
  '}
RESPONSE — Comorando confirms and takes over
201 Created
{
  "status": "processed",
  "id": "bf56b6e4-20e0-4bce-...",
  "event_type": "payment.failed",
  "correlation_id": "9f4e2a1c-..."
}

// Comorando now handles:
// ✓ AI severity classification
// ✓ Retry schedule (1h → 24h → 72h)
// ✓ Grace period logic
// ✓ Idempotency (safe to retry)
// ✓ Full audit log

See the full API reference in Docs →

Comorando is a hosted SaaS. It runs on our infrastructure and receives events via API. No self-hosting required.

Or install via SDK
Coming soon

A typed SDK is in active development. For now, the API is available via fetch() — no install required.

Terminal / app.js
npm install @comorando/sdk

import { sendEvent } from "@comorando/sdk";

await sendEvent({
  apiKey: process.env.COMORANDO_KEY,
  eventType: "payment.failed",
  data: { amount: 79, failure_reason: "insufficient_funds" }
});

SDK in active development. API available now via fetch().

One detected churn event
can help cover the cost of your plan.

One retained customer can cover the full monthly plan cost. If Comorando prevents a single churn event, it has already generated a return.

$99
Starter plan cost
One retained customer on any paid plan covers this cost. The math works from your first preserved subscription.
<80ms
Average AI decision latency
Faster than your customer notices. The Revenue Agent acts before the failure propagates to your application state.
24/7
Continuous event monitoring
Payment failures don't respect business hours. Comorando watches your pipeline around the clock, every day.

Stop calculating the cost. Calculate the risk of not having it.

Every unmonitored payment failure is a silent exit. Comorando helps manage broken events through automated retries — measured, logged, and auditable.

Why Comorando
Built for production from day one.
🔁

Idempotent by design

Every event is processed exactly once. Duplicate webhooks are silently ignored — no double-charges, no double-downgrades.

Sub-second execution

Events are classified and acted on in under 100ms. Minimizes the impact of failed payments on customer experience — Comorando handles it before their next request.

+ Technical details
🔐

Webhook verification

All incoming webhooks are cryptographically verified. Forged or tampered events are rejected automatically before any logic runs.

🧠

Local AI inference

Gemma 4B runs on-premise. No event data leaves your infrastructure. AI decisions are private, fast, and never rate-limited by a third-party API.

🏢

Multi-tenant isolation

Strict organization-level separation. Each tenant's data, API keys, and memory context are fully isolated with row-level security.

🔑

API key management

Generate and revoke API keys per organization. Keys are hashed with SHA-256 and shown only once — never stored in plain text.

Early access open — first 10 clients get full access free for 30 days in exchange for honest feedback.

Integrations

All your revenue intelligence in one place

Compatible with payment providers via webhooks (including PayPal, Payway, Mercado Pago, and others) — unifying decision logic and eliminating fragmentation in your billing data.

PayPal Mercado Pago Payway

Comorando is an independent platform and is not affiliated with, associated with, authorized by, or endorsed by Mercado Pago, PayPal, or any other payment gateway mentioned on this site. All trademarks belong to their respective owners.

For Professionals & Firms

Offer payment monitoring as a service to your clients. You earn monthly fees, they pay better.

Offer your clients recovered revenue reports and increase your monthly fee.

FREE TRIAL
$0/mo
30-day trial
Try it with 3 real clients for 30 days
  • 3 clients
  • Basic monitoring
  • Email alerts
  • 30-day trial
PRO
$349/mo
billed monthly
For professionals with up to 20 SaaS clients
  • 20 clients
  • Everything in Starter
  • Exportable PDF reports
  • Priority support
SCALE
$799/mo
billed monthly
For agencies and large firms
  • 50 clients
  • Everything in Pro
  • White-label dashboard
  • Dedicated support
Results

You don't guess. You measure.

Comorando doesn't show events. It helps recover revenue that would otherwise be lost.

$47K
Revenue recovered
12K+
Events managed
340
Customers at risk

Estimates based on industry benchmarks and simulated scenarios. Not guaranteed results.

Every day without payment monitoring is revenue you're losing without noticing.

Infrastructure pricing. Not agency pricing.

Flat monthly rate. No setup fees. No annual lock-in.

Pricing designed for long-term stability. No aggressive discounts or unexpected changes.

SaaS companies lose 3-9% of MRR to failed payments every month. Most of it is recoverable.
FREE
$0/mo
forever free
250 events / month
  • Core event processing
  • Redis idempotency
  • 1 API key
  • Community support
STARTER
$99/mo
billed monthly
Cancel anytime · No lock-in
10,000 events / month
For SaaS already losing revenue to failed payments (even if you don't see it)
  • Everything in Free
  • PayPal webhook handling
  • Revenue Agent
  • AI retry management
  • Email support
  • No code changes required — works with your existing webhook

*At 3% failure rate on $5K MRR you lose ~$150/mo

SCALE
$599/mo
billed monthly
Cancel anytime · No lock-in
Unlimited events / month · Subject to fair use policy
Used by teams where payment failures impact revenue in real time
  • Everything in Pro
  • Memory layer (learns your customers)
  • Priority execution
  • Designed for high availability (target 99.9%)
  • Dedicated support
  • No code changes required — works with your existing webhook

*At 3% failure rate on $200K MRR you lose ~$6,000/mo

Comorando provides infrastructure tooling for payment event management. Results depend on user implementation and payment provider. We do not guarantee financial outcomes. Automated decisions are based on probabilistic models.

A single recovered event can cover your monthly cost.

Comorando is not a cost. It's revenue you were already losing.

👨‍💻

"Built by a developer who lost thousands to failed webhooks. I built Comorando because I needed it myself."

Federico Peña, Founder, Comorando  ·  @federicopenadev

FAQ
Common questions
What exactly is Comorando's decision layer?
It's Comorando's core processing layer that intercepts payment and subscription events, runs them through a local AI model (Gemma 4B) for severity and risk classification, applies intelligent retry logic, and executes the correct state correction — all idempotently. It's infrastructure, not a service: you own the decisions and the data.
What is the Revenue Agent?
The Revenue Agent is a persistent AI process available on Growth and above. It monitors payment events in real time, scores churn risk, adapts retry schedules based on customer context (LTV, engagement, history), flags at-risk accounts 24 hours before predicted churn, and logs every decision with full audit trail. It runs on your infrastructure — no data leaves your environment.
What is "intelligent retry logic"?
Rather than retrying at fixed intervals, Comorando's retry logic adapts based on the AI-classified failure type and customer risk score. A high-LTV customer with a first-time card decline gets an immediate grace period extension and a different retry schedule than a low-engagement account with repeated failures. Logic, not timers.
How does idempotency work?
Every event carries a unique ID. Comorando stores processed event IDs in Redis with a 1-hour TTL. If the same event arrives twice — from a retry, a duplicate webhook, or a network glitch — the duplicate is silently ignored without executing the action twice.
Does Comorando store sensitive payment data?
No. Comorando never processes card numbers, bank details, or full payment credentials. We receive event metadata from PayPal/Stripe (event type, subscription ID, amount, status) and act on that. All payment processing remains with your payment provider. See our Privacy Policy for full details.
Is pricing stable long-term?
Yes. Prices are flat monthly rates with no lock-in, no hidden fees, and no aggressive discounting. We don’t believe in bait-and-switch pricing. What you see is what you pay — month after month.
What happens if I exceed my event limit?
Events above your plan limit are billed as overage. Starter: $0.015/100 events. Growth: $0.01/100. Performance: $0.01/100. Pro: $0.006/100. Enterprise: custom. You will never be cut off without prior notification.
Is my data secure?
All API keys are hashed with SHA-256 and never stored in plain text. Webhook signatures are verified on every request. Data is stored in Supabase with row-level security. Org memory (AI context) is isolated per organization. All connections use TLS. The local AI model (Gemma) runs on-premise — event data never leaves your infrastructure.
How does Comorando handle retries?
Comorando implements retry logic following payment processor guidelines. Default intervals are 1h, 24h, and 72h. You can customize intervals within your processor's acceptable use policy. Comorando never processes payments directly.
How does Comorando handle duplicate events?
Event deduplication uses Redis atomic SETNX operations. Duplicate events arriving within 1 hour are rejected at the infrastructure level — not the application level. This means zero duplicate charges, zero double-activations, even under high load.

Stop watching revenue
leave through broken events.

Every billing cycle without monitoring is revenue that doesn't come back.

Start with 250 free events. No credit card required. One detected payment event can help cover your first month. See why founders switch in week one.

Talk to the founder

Doesn't replace your payment system. Makes it smarter.

Infrastructure

Production-ready infrastructure

Guaranteed idempotency Organization-level isolation Secure execution Does not access or process payments Never blocks or interferes with your payment flow Actions configurable within your rules

If Comorando is ever unreachable, your payment flow keeps working. We never sit in the critical path.

Privacy & Compliance

Data encrypted at rest and in transit (TLS 1.2+). We process event metadata, never payment credentials. Designed with GDPR principles. Data processing agreements available upon request.

Designed for high availability (target 99.9%) · Fail-safe mode: your payment flow is never blocked · Retry intervals: 1h → 24h → 72h max

Comorando makes your payment stack smarter. It does not replace it.