Transparency

Transparency Report

Real numbers from a one-time test run. We don't invent metrics or use unqualified marketing language.

Point-in-time snapshot. This is not a live dashboard. These numbers represent a single test pass executed on September 4, 2026 against our production infrastructure running on the Supabase Free Tier.
Note on Database Limitations: The throughput ceilings shown below are explicitly bound by the Supabase Free Tier limits (maximum 60 concurrent database connections, restricted token buckets). If Spineforge were deployed on a paid or dedicated tier, these throughput thresholds would scale significantly higher.

System Limits & Throughput

Max Sustained QPS (Free Tier Bound)

100 req/sec

Measured via: Constant-arrival-rate test against /health and telemetry endpoints. At 100 RPS, p95 latency was 157ms with 0 errors. Further ramping hits the Supabase Free Tier API constraints. (As of September 4, 2026)

DB Capacity (Free Tier Bound)

~60 Concurrent Connections

Measured via: Concurrent connection stress-test via asyncpg. The Supabase Free Tier restricts direct PostgreSQL connections to 60. (As of September 4, 2026)

Batch Upload Throughput

1,931 actions/sec

Measured via: One high-volume synthetic SDK batch run (payload processing time 0.03s for 50 events). (As of September 4, 2026)

Reliability & Data Loss

Data Loss (Fault Injection)

0%

Measured via: Killing the backend mid-batch from the SDK. Verified that the FileSink local fallback catches all failed emits, and 207 HTTP partial-success responses are handled without silent drops. (As of September 4, 2026)

Uptime

Not currently tracked

Measured via: We do not have a public monitor configured at this time. (As of September 4, 2026)

Latency Percentiles

API Latency (at 100 RPS)

p50: 88.98ms  |  p95: 157.48ms  |  p99: 169.90ms

Measured via: Ramp load test at increasing RPS steps up to 100 RPS before hitting free tier capacity bounds. (As of September 4, 2026)

API Latency (at 60 RPS)

p50: 58.03ms  |  p95: 99.60ms  |  p99: 101.61ms

Measured via: Constant-arrival load testing. (As of September 4, 2026)

Accuracy

Cost Calculation Accuracy

100%

Measured via: Table-driven correctness test comparing computed cost against rate_cards expected values. (As of September 4, 2026)

Audit Log Completeness

100%

Measured via: Spot-checking audit log records against a known action count. (As of September 4, 2026)