cameleer/cameleer-saas
1
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

Epic: Billing & Metering #4

New Issue
Open
opened 2026-03-29 23:16:55 +02:00 by claude · 0 comments
claude commented 2026-03-29 23:16:55 +02:00
Owner
Copy Link

Overview

Stripe-based billing with two pricing models: usage-based for shared tiers, committed resources for dedicated tiers.

Pricing Models

Usage-Based (Low/Mid Tiers)

  • Optional small base fee per month
  • Metered dimensions:
    • Data volume: bytes ingested (traces, payloads, metrics) into PostgreSQL + OpenSearch
    • CPU: compute consumed by tenant's cameleer3-server + deployed Camel apps
    • RAM: memory consumed by tenant's namespace workloads
  • Stripe metered subscriptions with periodic usage reporting
  • K8s resource metrics collection (likely Prometheus/metrics-server → platform aggregation)

Committed Resources (High/Business Tiers)

  • Fixed pricing based on reserved cluster capacity
  • Resource commitments (CPU cores, RAM, storage, node count)
  • Annual or multi-year contracts
  • Overage billing if usage exceeds commitment

Implementation

  • Stripe Subscriptions API for plan management
  • Stripe Usage Records API for metered billing
  • Metrics pipeline: K8s metrics → aggregation service → Stripe usage reporting
  • Customer billing portal (Stripe Customer Portal or custom)
  • Invoice generation and payment processing
  • Usage dashboards in the management platform

MOAT Feature Metering

  • Lineage events (premium data volume)
  • Debug session time
  • Per-tier feature limits enforced by license module
## Overview Stripe-based billing with two pricing models: usage-based for shared tiers, committed resources for dedicated tiers. ## Pricing Models ### Usage-Based (Low/Mid Tiers) - Optional small base fee per month - Metered dimensions: - **Data volume**: bytes ingested (traces, payloads, metrics) into PostgreSQL + OpenSearch - **CPU**: compute consumed by tenant's cameleer3-server + deployed Camel apps - **RAM**: memory consumed by tenant's namespace workloads - Stripe metered subscriptions with periodic usage reporting - K8s resource metrics collection (likely Prometheus/metrics-server → platform aggregation) ### Committed Resources (High/Business Tiers) - Fixed pricing based on reserved cluster capacity - Resource commitments (CPU cores, RAM, storage, node count) - Annual or multi-year contracts - Overage billing if usage exceeds commitment ## Implementation - Stripe Subscriptions API for plan management - Stripe Usage Records API for metered billing - Metrics pipeline: K8s metrics → aggregation service → Stripe usage reporting - Customer billing portal (Stripe Customer Portal or custom) - Invoice generation and payment processing - Usage dashboards in the management platform ## MOAT Feature Metering - Lineage events (premium data volume) - Debug session time - Per-tier feature limits enforced by license module
claude added the billingepic labels 2026-03-29 23:17:59 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auth
Identity, authentication, OIDC, RBAC
 billing
Billing, metering, and Stripe integration
 day-1
Required for initial launch
 epic
Top-level epic grouping related issues
 future
Planned for future release
 infra
Infrastructure, GitOps, K8s orchestration
 licensing
License module and feature gating
 networking
Network isolation, VPN, tenant separation
 observability
Observability integration (cameleer3-server)
 ops
Platform operations and self-monitoring
 phase-1
Phase 1: Foundation + Auth
 phase-2
Phase 2: Tenants + Licensing
 phase-3
Phase 3: Runtime Orchestration + Environments
 phase-4
Phase 4: Observability Pipeline + Inbound Routing
 phase-5
Phase 5: K8s Operational Layer
 phase-6
Phase 6: Billing + Metering
 phase-7
Phase 7: Billing + Metering
 phase-8
Phase 8: Security Hardening + Self-Monitoring
 phase-9
Phase 9: Frontend (React Shell)
 platform
SaaS management platform
 runtime
Camel application runtime
 secrets
Secrets management and vault integration
 security
Security, compliance, SOC 2, audit
 task
Implementation task within a phase
No Label billing epic
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cameleer/cameleer-saas#4
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?