Add billing using paddle (done) and crypto support (backlog) #5

Closed
opened 2025-12-04 06:18:23 +00:00 by anton · 3 comments
anton commented 2025-12-04 06:18:23 +00:00 (Migrated from codeberg.org)
  • Track resource usage in our own DB - cloud billing APIs lag 24-48hrs and we need real-time data for user dashboards
  • Write start/stop events when enclaves launch/terminate, including cloud resource ID so we can reconcile later
  • Hourly cron aggregates running time per user into billing summaries
  • We set our own pricing tiers - cloud costs are our problem, customers pay our rates
  • Use Paddle as payment processor (Stripe unavailable in Cayman Islands) - they handle tax compliance as Merchant of Record
  • Report metered usage to Paddle monthly, they invoice customers
  • Cloud provider APIs (AWS Cost Explorer etc) only used for monthly sanity checks - verify we didn't miss any stop events or have orphaned resources
  • Abstract cloud-specific stuff behind a trait so billing logic doesn't care which provider
  • Billing runs as separate service/worker - isolated from main API
* Track resource usage in our own DB - cloud billing APIs lag 24-48hrs and we need real-time data for user dashboards * Write start/stop events when enclaves launch/terminate, including cloud resource ID so we can reconcile later * Hourly cron aggregates running time per user into billing summaries * We set our own pricing tiers - cloud costs are our problem, customers pay our rates * Use Paddle as payment processor (Stripe unavailable in Cayman Islands) - they handle tax compliance as Merchant of Record * Report metered usage to Paddle monthly, they invoice customers * Cloud provider APIs (AWS Cost Explorer etc) only used for monthly sanity checks - verify we didn't miss any stop events or have orphaned resources * Abstract cloud-specific stuff behind a trait so billing logic doesn't care which provider * Billing runs as separate service/worker - isolated from main API
anton commented 2026-01-30 23:45:54 +00:00 (Migrated from codeberg.org)

working on finalizing ToS and Privacy Policy as that's required for cc processing via Paddle

working on finalizing ToS and Privacy Policy as that's required for cc processing via Paddle
anton commented 2026-01-30 23:46:39 +00:00 (Migrated from codeberg.org)

separately i came across https://shkeeper.io/ for crypto payment processing

separately i came across https://shkeeper.io/ for crypto payment processing
anton commented 2026-04-06 16:54:01 +00:00 (Migrated from codeberg.org)

Paddle integration is done!

Paddle integration is done!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
public/platform#5
No description provided.