How to delete your Fly.io (CLI managed) account

About deleting your Fly.io (CLI managed) account

Fly.io is a platform-as-a-service (PaaS) that allows developers to deploy applications close to their users by running containers across a global edge network. Because the service is heavily integrated with the Fly CLI (flyctl), much of the user state—including application configurations, secrets, and deployment history—is managed directly from your local terminal. Unlike traditional web-based platforms, Fly.io treats your infrastructure as code, making account cleanup a technical task rather than a simple dashboard click.

Users often seek to delete their Fly.io accounts for several distinct reasons related to the platform's specific architectural choices:

• Transitioning away from container-orchestrated edge computing.
• Consolidating development environments to reduce technical surface area.
• Avoiding the complexity of managing CLI-based billing profiles and infrastructure snapshots.
• Eliminating the risk of "zombie" containers that might incur costs if not destroyed properly.

What happens to your data

When you initiate the deletion process for your Fly.io account, the platform attempts to purge the resources linked to your organization ID. However, the nature of distributed systems means that while your visible application data is removed, certain logs and metadata may persist in accordance with their service level agreements.

• Container Images: These are deleted from the internal registry once the associated apps are destroyed via flyctl.
• Application Logs: Usually purged during account closure, though some audit logs related to billing transactions are retained to satisfy tax and financial compliance.
• Deployment Secrets: These are wiped from the key-value store immediately upon the deletion of the associated app.
• Billing Information: Contacting support is mandatory because Fly.io retains credit card tokens and invoice history for legal record-keeping requirements.

Privacy considerations

Fly.io collects telemetry data regarding CLI usage to improve the developer experience. While this data is not typically sold to third-party ad networks, it provides visibility into your deployment frequency and resource utilization patterns.

• Audit your CLI config: Before deleting your account, run flyctl auth logout to clear your local API tokens.
• Check for persistent storage: If you used Fly Volumes, ensure they are destroyed, as these may hold persistent database files that are not automatically wiped by simply deleting the app.
• Minimize data footprint: Avoid storing sensitive personal user data directly in your deployment configuration files or secrets, as these snapshots may exist in the system logs for a brief period during the migration or deletion phase.

Frequently Asked Questions

Is deleting an app the same as deleting a Fly.io account?

No. Deleting an app via flyctl only removes that specific instance. You must contact support to ensure the entire billing organization and user profile are removed.

Can I recover my data after deleting a Fly.io account?

Generally, no. Once the support team processes the account closure and purges the organization, the application state and deployment history are permanently unrecoverable.

Does Fly.io store my code?

Fly.io stores the container images you build and push to their registry. Deleting these images via the CLI is a critical step in the data removal process.

Why do I need to contact support to delete my account?

Because Fly.io billing handles recurring costs and infrastructure expenses, they require human verification to ensure all financial obligations are cleared before terminating the account.

What happens if I have pending invoices during deletion?

Support will not close your account until all outstanding invoices are settled. Ensure your billing dashboard is empty before requesting account deletion.

Does the CLI keep a history of my commands?

Yes, your local terminal shell history may contain command-line arguments used during deployment. You should clear your shell history file after account closure to maintain full privacy.