Amplitude
AI & ML · 100% complete
Stage Checklist
- ✓ Research (.md file)
- ✓ POC App
- ✓ POC UI (templates)
- ✓ Microservice
- ✓ Containerized (Dockerfile)
- ✓ Helm Chart
- ✓ CI/CD Pipeline
- ✓ Frontend Page
AI Research
Refund Rules
Amplitude typically operates on annual contracts with no standard refund policy for unused capacity or mid-cycle cancellations. Refunds are generally not available for downgraded MTU limits or unused event volumes. However, billing error corrections are handled on a case-by-case basis. Enterprise customers may negotiate specific refund terms during contract negotiations.
Credit Policies
Amplitude provides service credits for significant platform downtime per their SLA (99.9% uptime guarantee). Credits are typically calculated as a percentage of monthly fees proportional to downtime duration. No standard credits are offered for unused MTU capacity or event volumes, as these are monthly allowances rather than consumed resources. Enterprise plans may include negotiated credit terms for service issues.
Contractual Terms
Annual contracts with auto-renewal clauses are standard. Price increases are typically capped at 5-10% annually with 30-60 days notice. Cancellation requires 30 days written notice before renewal. Enterprise contracts may have longer cancellation notice periods (60-90 days). Contract terms often include minimum commitment periods and penalties for early termination. Volume discounts are available for high MTU usage.
Integration Complexity
Technical Notes
No OAuth2 support - requires manual API key/secret sharing from customers. Uses Basic Auth with base64(api-key:secret-key) format. Multiple API types: project-level keys for analytics, org-level keys for cross-project data (must contact support for rotation), SCIM tokens for Enterprise user management. Rate limits are complex - cost-based system for Dashboard API (1000 points/5min, 108K/hour). Export API limited to 365 days and 4GB. EU region requires different endpoints. Key rotation can break integration until customer provides new credentials. No native multi-tenant support - requires storing per-customer credentials.