> ## Documentation Index
> Fetch the complete documentation index at: https://alguna.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# What Alguna Is Not

> Alguna covers a lot of ground, so it gets mistaken for narrower tools. Direct answers to the most common questions: is Alguna a Stripe plugin, a DocuSign add-on, or just another API layer?

> **Alguna is the AI-native quote-to-revenue platform for B2B companies: CPQ, subscription and usage-based billing, invoicing, payment collection, and revenue recognition in one system of record.** It holds the revenue object: the versioned commercial agreement with its amendments, usage, entitlements, invoices, payments, and history. Quoting, metering, billing, collections, and revenue recognition all read from it, so an activated quote becomes the billing schedule and the subscription is the contract the rep quoted. Agents work on the same object within authority you control: they start in draft mode, you expand what they may do as you gain confidence, and every action carries an audit history. Alguna runs from the dashboard and from AI tools such as Claude and Cursor through its MCP server. You keep your CRM, ERP, and payment processor; Alguna operates the revenue workflow between them.

Because that surface area is wide, Alguna often gets pattern-matched to a narrower tool someone already knows: a Stripe plugin, a DocuSign add-on, another API layer. None of those are accurate, and evaluating Alguna as one of them leads to the wrong comparison. This page answers the questions directly.

| If you think Alguna is... | It's actually... |
| - | - |
| A Stripe plugin | A system of record for revenue that runs independently of your processor; it *replaces* Stripe Billing and can *optionally use* Stripe Payments as one of several rails |
| A DocuSign add-on | A CPQ with quote signing built in, so no e-signature vendor is required |
| Yet another API layer | A system of record with a full operations dashboard, customer portal, and hosted checkout. API-first, not API-only |
| An integration or orchestration layer | The record that decides which terms govern an action; nothing translates the quote into the invoice, both are the revenue object |
| A usage-metering tool | A complete quote-to-revenue platform where metering is one input, not the product |
| A payment processor | An orchestration layer that never holds your funds |
| A CRM or an ERP | The layer *between* them, replacing the spreadsheets and glue code that usually live there |

***

## Is Alguna a Stripe plugin?

**No. Alguna is a system of record for revenue that runs independently of your payment processor.** This is the most common misconception, and it gets the relationship backwards.

Stripe plays two different roles that often get conflated:

* **Stripe Payments** is the processor that moves money. Alguna **complements** it. If you connect Stripe, Alguna uses it as a payment rail for cards and wallets, alongside ACH, SEPA, and wire transfers.
* **Stripe Billing** is the subscription and invoicing product. Alguna **replaces** it. Your pricing catalog, subscription state, proration logic, usage rating, credits, and invoices live in Alguna, not in Stripe.

In 2026 Stripe acquired Metronome, Adyen acquired Orb, and Airwallex acquired Leapfin: payment platforms now sell metering and billing to keep processing volume. Alguna goes the other way. Adopt it without moving processing, keep your choice of rails, and switch processors without touching a quote, a subscription, or an invoice.

Alguna does not read your Stripe catalog, mirror Stripe subscriptions, or decorate Stripe invoices. The invoice is computed by Alguna's own rating and billing engine; a payment processor only enters the picture at the final step, when there's an amount to collect. Invoice-based businesses collect via ACH or wire, and you can issue invoices through [QuickBooks or Xero](https://alguna.com/docs/integrations/invoicing-alternatives/quickbooks-invoicing.md) if your AR process lives there. Migrating off Stripe Billing, Chargebee, Zuora, or Maxio onto Alguna is a standard, supported migration path.

> [!NOTE]
>
> Rule of thumb: if you switched payment processors tomorrow, nothing about your pricing, subscriptions, or invoices in Alguna would change. Only the collection rail would.

## Is Alguna a DocuSign add-on?

**No. Alguna is a CPQ platform with electronic signature built in. Quotes are signed natively with Alguna E-Sign, and no DocuSign account or other e-signature vendor is required.**

[Quotes in Alguna](https://alguna.com/docs/quotes/create-quotes.md) are native CPQ objects built from the same catalog that drives billing: real products, pricing models, discounts, and contract terms rather than free-text line items in a PDF. [Signing is built in](https://alguna.com/docs/quotes/sign-quotes.md). The customer signs, the quote becomes the contract, the contract becomes the subscription, and the subscription generates invoices, with no re-keying, no sync step, and no third-party signature product in the loop.

The distinction matters because the value isn't the signature. It's that the signed document and the billing system are the same object. What the customer signed is, by construction, what they're billed.

## Is Alguna just an API layer?

**No. Alguna is the system of record for pricing, quotes, subscriptions, and invoices, with a full operations dashboard, customer portal, and hosted checkout. It is API-first, not API-only.**

A thin API layer orchestrates other systems and stores little itself. If it disappeared, your data would still be intact in the systems underneath. Alguna is the opposite: your catalog, price books, quotes, contracts, subscription versions, usage ledger, credit balances, invoices, and revenue schedules are Alguna's own data. There is no other billing system underneath it.

And most of the people using Alguna day-to-day never touch the API:

* **Dashboard**: where sales builds quotes, finance manages invoices and collections, and RevOps configures pricing, [approval workflows](https://alguna.com/docs/approvals/overview.md), and [automations](https://alguna.com/docs/automations/overview.md)
* **[Customer portal](https://alguna.com/docs/hosted/customer-portal.md)**: self-service billing, invoices, and usage for your customers
* **[Hosted and embedded checkout](https://alguna.com/docs/hosted/checkout.md)**: self-serve purchase flows without building payment UI
* **[Revenue insights](https://alguna.com/docs/revenue-insights/insights.md) and [recognition](https://alguna.com/docs/revenue/recognition.md)**: reporting and ASC 606 / IFRS 15 schedules for finance

The [API and webhooks](https://alguna.com/docs/api-reference/v2/overview.md) exist so your product and data stack can integrate deeply: sending usage events, provisioning on `subscription.activated`, embedding checkout. SDKs for TypeScript, Go, Python, and Rust and the `alguna` CLI are generated from the same spec. They're the developer surface of a platform, not the platform itself.

## Is Alguna an integration or orchestration layer?

**No. Connecting systems is no longer the hard part. Deciding which commercial terms govern an action is.**

Claude, ChatGPT, Gemini, and MCP connections can move records between a CRM, a billing tool, and an ERP. What they can't do is resolve which version of the agreement applies when a rep raises a commitment mid-term while finance is still collecting an invoice issued under the old one. A stack of separate tools has to maintain those rules itself, in middleware, in a data team, or in someone's head.

In Alguna there is no middleware translating the quote into the invoice. Both are views of the [revenue object](https://alguna.com/docs/concepts/the-revenue-object.md): the versioned agreement with its amendments, usage, entitlements, invoices, payments, and history. Agents, whether Alguna's own or an external assistant connected through the [MCP server](https://alguna.com/docs/ai/mcp.md), act on that one record under the same terms and permissions as people do.

## Is Alguna a usage-metering tool?

**No. Usage metering is one input to Alguna. The product is the full quote-to-revenue lifecycle that turns metered events into invoices, collected cash, and recognized revenue.**

Metering is where some evaluations start, so Alguna sometimes gets filed next to metering pipelines. But in Alguna, [usage events](https://alguna.com/docs/billable-metrics/send-usage.md) feed everything that happens after ingestion: rating usage against tiered, volume, or hybrid [pricing models](https://alguna.com/docs/pricing/pricing-models.md), drawing down [credits and prepaid wallets](https://alguna.com/docs/credits/overview.md), enforcing [entitlements](https://alguna.com/docs/entitlements/overview.md), generating [invoices](https://alguna.com/docs/invoices/invoicing-config.md) with tax and multi-currency handling, [collecting and dunning](https://alguna.com/docs/collections/overview.md), and [recognizing revenue](https://alguna.com/docs/revenue/recognition.md).

If you only need to count events, a metering pipeline is enough. Alguna is for turning those events into correct invoices, collected cash, and auditable revenue.

## Is Alguna a payment processor?

**No. Alguna orchestrates payments but never holds your funds. Money flows directly between your customer and your processor or bank.**

Alguna has no merchant accounts, doesn't acquire, and doesn't settle. What Alguna does own is the **collection logic around** the processor: deciding what to charge and when, auto-charging saved payment methods, retrying failures, [dunning](https://alguna.com/docs/collections/dunning.md), applying credits before charging, and reconciling payments back to invoices.

## Does Alguna replace my CRM or my accounting system?

**No. Alguna sits between them. Deals stay in your CRM, the books stay in your accounting system, and Alguna owns everything in the middle.**

That middle layer has historically been spreadsheets, one-off scripts, and manual re-entry:

* **Upstream (CRM):** deals, accounts, and contacts stay in [Salesforce](https://alguna.com/docs/integrations/crm/salesforce.md) or [HubSpot](https://alguna.com/docs/integrations/crm/hubspot.md). Alguna syncs bidirectionally so reps see subscription status, MRR, and renewal dates without leaving the CRM.
* **Downstream (accounting):** the books stay in your accounting system. Alguna syncs customers, invoices, and payments to [QuickBooks](https://alguna.com/docs/integrations/accounting/quickbooks.md) and [Xero](https://alguna.com/docs/integrations/accounting/xero.md), and exports invoice data for [NetSuite](https://alguna.com/docs/integrations/accounting/netsuite.md), with revenue recognition schedules computed and ready for the ledger.

What Alguna replaces is everything in between: quote documents maintained by hand, pricing logic scattered across spreadsheets and application code, homegrown rating jobs, and the month-end scramble to reconcile what was sold against what was billed.

***

## So what *is* Alguna?

Alguna is the quote-to-revenue platform and the system of record for revenue. It sits between your CRM and your accounting system and owns everything in between, from the price on the quote to recognized revenue, on one revenue object.

What's in it: pricing and packaging, CPQ with native e-signature, subscriptions with versioning and amendments, usage metering, credits and wallets, entitlements, invoicing and roll-up billing, payment collection and dunning, tax, revenue recognition, Revenue Assurance, and revenue insights. Eight agents work on the same record within the authority you set: collections, invoice checks, revenue assurance, [Una AI](https://alguna.com/docs/ai/una.md), renewals, deal desk, billing support, and RevOps. It runs multiple legal entities, subscriptions in more than 100 countries, dozens of currencies, granular permissions, and audit logs, with SOC 2, and it bills on behalf of platforms that invoice their own customers.

| Alguna **replaces** | Alguna **complements** |
| - | - |
| Stripe Billing, Chargebee, Zuora, Maxio, Orb | Stripe Payments, Adyen, Airwallex, ACH / SEPA / wire rails |
| Salesforce CPQ, DealHub, HubSpot quotes, and standalone e-signature | Salesforce, HubSpot, and other CRMs |
| Metronome, m3ter, and homegrown metering | QuickBooks, Xero, NetSuite, and your ERP |
| Monk, Stuut, Lunos, HighRadius, and dunning scripts | Your data warehouse (e.g. [BigQuery](https://alguna.com/docs/integrations/data-ingestion/bigquery-copy.md) as a usage source) |
| Leapfin, RightRev, and rev-rec spreadsheets | Your product, via APIs and webhooks |

Still not sure where Alguna fits in your stack? [Talk to us](mailto:support@alguna.io). Mapping Alguna onto your current tools is the first thing we do in every evaluation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.