Skip to content

Log Streaming & Billing Integration

§16.6 Log Streaming

Depot's log retention is plan-tier bound (7 days Developer, 30 days Startup, custom on Business). Rather than depend on Depot's retention policy for customer-visible logs, Starforge streams build logs from Depot's API to ClickHouse as they arrive. This gives Starform:

  • Independent retention control (matches Starform's own plan tiers: 7 / 30 / 90 days)
  • Single source of truth for customer log viewing (build logs + runtime logs in one place)
  • No customer dependency on Depot's dashboard or Share URLs

The Starform dashboard reads build logs exclusively from ClickHouse. Depot is an invisible upstream.

§16.7 Billing Integration

Build time is metered and billed at $0.05/minute against the customer's monthly credit (see Financial Model for bundling details). Depot's public overage rate is $0.04/minute, yielding ~20% gross margin on build minutes at list pricing. Business-plan negotiated rates are expected to improve this materially — Depot's platform-customer pricing is custom, and Starform will engage Depot sales ahead of launch to negotiate a volume rate.

  • Starbase Worker records build start and end timestamps per build
  • Nightly cron aggregates build minutes per workspace per day into the usage_events table
  • Monthly billing roll-up includes build minutes alongside compute, egress, and storage as line items consumed from the plan credit
  • Cache storage overage on Depot ($0.20/GB/mo beyond plan allocation) is tracked as infrastructure overhead, not passed through to customers — included in plan pricing

Cross-references

The flow where the Worker streams logs Depot → ClickHouse → §16.2 · the Worker binary that records timestamps and runs the nightly cron → Starbase §14 · the monthly roll-up that consumes usage_events → Billing §36 · cache storage overhead as a known limitation → §16.8.