LaunchDarkly

Refund Rules

LaunchDarkly's refund policies are not publicly documented in detail. Based on their SaaS model, they typically operate on a usage-based billing system with monthly/annual commitments. Refunds for unused service connections or mid-cycle downgrades would need to be negotiated with their sales team. As a standard practice, they likely offer prorated credits for billing errors but not cash refunds for voluntary cancellations.

Credit Policies

LaunchDarkly offers service level agreements (SLAs) for uptime with credits for downtime incidents. Their Enterprise plans include SLA credits for service interruptions. They also provide credits for pre-paid unused capacity in cases of plan downgrades, though specific terms vary by contract. Usage overages are typically billed monthly without automatic credits, but billing disputes can result in usage adjustments.

Contractual Terms

Auto-renewal: Standard 12-month terms with automatic renewal unless 30-60 day notice is provided. Cancellation notice: Typically 30 days for monthly plans, 60-90 days for annual contracts. Price increases: Limited to once per year with 60-90 day advance notice, often capped at 10-15% annually for existing customers. Enterprise contracts may include price protection clauses. Service connection commitments are common with minimum usage requirements.

Integration Complexity

Technical Notes

OAuth 2.0 with Authorization Code flow. Base URL: https://app.launchdarkly.com/api/v2/. Rate limits: 100 requests per minute per access token (higher limits for Enterprise). Key APIs: Members (/members), Feature Flags (/flags), Usage (beta, requires LD-API-Version: beta header), Audit Logs (/auditlog). Authentication inherits member permissions - if member permissions change, OAuth app access is affected. Token expiration not well documented - may be long-lived. Single redirect URI per OAuth client, HTTPS required.