How to Cancel Typesense Cloud (Terminate a Cluster)

How to fix it

Try these in order — the most common fix is first.

1. 1. Export your data first

   Copy steps
   1. Export documents from each collection (GET /collections/<name>/documents/export)
   2. Keep your schema JSON so you can recreate collections elsewhere
   Did this fix it? Yes No

2. 2. Terminate via the Cloud Management API

   Copy steps
   1. Create a management API key with the clusters:terminate capability
   2. POST https://cloud.typesense.org/api/v1/clusters/<ClusterID>/lifecycle with {"lifecycle_action": "terminate"}
   3. Set delete_backups to true if you also want kept backups removed (default false keeps them until they expire)
   4. The cluster moves from deprovisioning to terminated
   Did this fix it? Yes No

3. 3. Check billing afterwards

   Copy steps
   1. Confirm the cluster shows terminated
   2. Docs say kept backups are billed for storage until they expire, so delete them if you do not need them
   3. For refund or billing questions, contact Typesense support
   Did this fix it? Yes No

4. 4. Self-hosted

   1. Nothing to cancel: stop the server and delete the data directory when you no longer need it
   Did this fix it? Yes No

Symptoms

You want to stop paying for Typesense Cloud or delete a cluster you no longer need.

Why it happens

• Cloud clusters are billed per cluster configuration, not by a separate subscription
• Terminating destroys the data and cannot be undone
• Kept backups can still be billed for storage until they expire

This guide also covers

• cancel typesense cloud
• typesense terminate cluster
• delete typesense cluster
• typesense refund

The same problem in other apps

All billing, cancellation & refunds guides →

• How to Cancel Meilisearch Cloud (Delete Project) (Meilisearch)
• How to Cancel Algolia Subscription (Algolia)
• How to Cancel Elastic Cloud and Stop Billing (Elasticsearch)
• How to Cancel Qdrant Cloud and Delete a Cluster (Qdrant)

Other Typesense errors

• Typesense 503 Not Ready or Lagging Error
• Typesense Out of Memory (OOM) and RAM Sizing
• Typesense Import Error: Field Type Mismatch
• Typesense Schema Update Without Deleting the Collection
• Typesense Search Returning No Results or Missing Typos
• Typesense API Key 401 / 403 Forbidden and Scoped Keys
• Typesense Cluster Upgrade Problems and Downtime
• Why Is Typesense Slow? High Latency Fixes