Stage Checklist

  • ✓ Research (.md file)
  • ✓ POC App
  • ✓ POC UI (templates)
  • ✗ Microservice
  • ✗ Containerized (Dockerfile)
  • ✗ Helm Chart
  • ✗ CI/CD Pipeline
  • ✗ Frontend Page
Download Research Download Implementation Guide

AI Research

Last researched: 2026-03-05

Refund Rules

Kandji typically follows standard SaaS practices with no refunds for mid-cycle cancellations or unused devices. However, they may offer prorated refunds for billing errors or duplicate charges. For unused seats discovered during contract period, customers usually cannot get immediate refunds but can right-size at renewal. Refund policies vary by contract size and are often negotiated as part of enterprise agreements.

Credit Policies

Kandji offers service credits for documented downtime that exceeds their SLA commitments (typically 99.9% uptime). Credits are generally 5-25% of monthly fees depending on outage duration and impact. They may also provide credits for duplicate device enrollments or billing errors once verified. Pre-paid unused capacity credits are rare but may be negotiated for significant over-licensing situations discovered mid-contract.

Contractual Terms

Auto-renewal clauses are standard (typically 12 months). Cancellation requires 30-60 days written notice before renewal. Price increases are usually limited to 5-15% annually with 60+ days notice required. Enterprise contracts often include volume discounts with commitment tiers. Key terms include device count minimums, overage pricing for exceeding licensed devices, and data retention periods post-cancellation (typically 30 days).

Integration Complexity

★★☆☆☆

Technical Notes

Kandji provides well-documented REST APIs with Bearer token authentication. Rate limits are generous (1000 requests/hour typical). Key considerations: API tokens require specific permissions (Devices: Read, Blueprints: Read, etc.), pagination is required for large device counts (500+ devices), and device check-in timestamps are in UTC. The API is stable with good error handling and comprehensive device metadata including last check-in, compliance status, and blueprint assignments.