Papercups · FinOps Profile

Papercups Finops

FinOps view of Papercups spend. As open-source (MIT) self-hostable software, Papercups has no per-call API charges from the project; the dominant cost is the infrastructure required to operate it (compute, database, storage, bandwidth) plus engineering time to deploy and maintain it. There is no vendor invoice in the self-hosted model, so FinOps focus shifts to internal cloud-resource cost allocation rather than provider metering. Any hosted SaaS spend is unconfirmed given the project's maintenance-mode status.

Papercups Finops is the FinOps profile for Papercups on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 4 billable meters, billed in USD, on a monthly cycle, and pricing category open source (self-hosted).

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Customer Messaging, Live Chat, Open Source, Support, and Intercom Alternative.

Category: Customer Engagement and Support Pricing: Open Source (Self-Hosted) Billing: Monthly FOCUS v1.3
Customer MessagingLive ChatOpen SourceSupportIntercom AlternativeFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchase

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
Self-Hosted Infrastructure Provider
PricingCategory
Open Source (Self-Hosted)
ProviderName
Papercups
PublisherName
Papercups
ServiceCategory
Customer Engagement and Support
ServiceName
Papercups

Meters

compute_hours
Unit: hours
Hours of compute running the Elixir/Phoenix application server and BEAM VM.
database_storage
Unit: gigabytes
PostgreSQL storage for conversations, messages, and customers.
bandwidth
Unit: gigabytes
Egress bandwidth for the chat widget, REST API, and WebSocket traffic.
websocket_connections
Unit: connections
Concurrent Phoenix Channels WebSocket connections, a driver of memory and compute sizing.

Sources