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

Phase 6: Billing (was Phase 7) #29

New Issue
Open
opened 2026-03-30 09:24:18 +02:00 by claude · 0 comments
claude commented 2026-03-30 09:24:18 +02:00
Owner
Copy Link

Overview

Stripe integration for subscriptions, tier enforcement, and usage tracking. Lago deferred until usage-based pricing launches.

Architecture decision (2026-04-04): Moved from Phase 7 to Phase 6. Start with Stripe Checkout for fixed-tier subscriptions. Lago (open-source usage-based billing, 8 containers) deferred — design event model with Lago's API shape in mind from day 1. See docs/superpowers/specs/2026-04-04-dual-deployment-architecture.md.

Depends On

  • Phase 5 (#25 — K8s Operational Layer)

Related Epics

  • #4 (Billing & Metering)

Key Deliverables

  • Stripe Checkout integration — subscription creation for each tier
  • Subscription lifecycle — create, upgrade, downgrade, cancel
  • Tier enforcement — feature gating based on active subscription
  • Usage tracking — in platform DB (prep for Lago integration later)
  • Webhook handling — Stripe payment events

Build-vs-Buy

Component Decision Tool
Subscriptions BUY Stripe Checkout/Billing
Usage metering BUY later Lago (when usage-based pricing launches)

PRD Reference

Section 12 (Billing & Metering)
Superseded by: docs/superpowers/specs/2026-04-04-dual-deployment-architecture.md

## Overview Stripe integration for subscriptions, tier enforcement, and usage tracking. Lago deferred until usage-based pricing launches. > **Architecture decision (2026-04-04):** Moved from Phase 7 to Phase 6. Start with Stripe Checkout for fixed-tier subscriptions. Lago (open-source usage-based billing, 8 containers) deferred — design event model with Lago's API shape in mind from day 1. See `docs/superpowers/specs/2026-04-04-dual-deployment-architecture.md`. ## Depends On - Phase 5 (#25 — K8s Operational Layer) ## Related Epics - #4 (Billing & Metering) ## Key Deliverables - **Stripe Checkout integration** — subscription creation for each tier - **Subscription lifecycle** — create, upgrade, downgrade, cancel - **Tier enforcement** — feature gating based on active subscription - **Usage tracking** — in platform DB (prep for Lago integration later) - **Webhook handling** — Stripe payment events ## Build-vs-Buy | Component | Decision | Tool | |-----------|----------|------| | Subscriptions | **BUY** | Stripe Checkout/Billing | | Usage metering | **BUY later** | Lago (when usage-based pricing launches) | ## PRD Reference Section 12 (Billing & Metering) Superseded by: `docs/superpowers/specs/2026-04-04-dual-deployment-architecture.md`
claude added the billingphase-7 labels 2026-03-30 09:24:48 +02:00
claude changed title from Phase 7: Billing & Metering to Phase 6: Billing (was Phase 7) 2026-04-04 14:40:26 +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 phase-7
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#29
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?