Docs menu

Operate

Deleting projects and accounts

Delete a whole project (with a 7-day window to restore it) or your whole account, from the dashboard or the API, and what CLI keeps afterwards.

Explain it

You can delete a whole project or your whole account. Either goes to the trash first, and you have 7 days to change your mind before it's gone for good.

How to do it: a project's owner deletes it at the bottom of the project's Settings. To delete your account, go to Account settings, then Delete your account. You'll be asked to confirm, and with a second sign-in step if you have one.

Some records (like the payment ledger) are kept afterwards where the law requires it.

You can delete a single service, an environment, a whole project or your whole account. This page covers the last two: who can do it, what happens straight away, the 7-day window to change your mind, and what CLI keeps afterwards. Deleting one service or database is covered in Scaling and running.

Delete a whole project

Deleting a project stops everything in it and moves it to the trash for 7 days. Until then an owner can restore it. After 7 days it's gone for good.

Who can do it: an owner of the project, signed in as a person. Admins and API keys get FORBIDDEN, so an agent can't delete a project, even with a key that has every scope. If you have a second factor, CLI asks you to confirm with it first (STEP_UP_REQUIRED, see /docs/teams-and-security).

Before you start: withdraw any earnings the project has. While there are earnings to withdraw, deleting answers CONFLICT with details.available. Credit left on the project is lost when it's deleted; it can't be moved or refunded this way.

In the dashboard

  1. Open the project's Settings. Owners of a project (not of an environment) see a Delete project panel.
  2. Click Delete this project…. CLI shows what will go: the services, how many environments, any credit that will be lost, and the date until which you can restore it. If there are earnings to withdraw, it says so and won't let you continue.
  3. Type the project's name and click Delete the project.

With the API

Ask for the plan first with a dry run. Nothing changes:

API
DELETE /v1/projects/:id?dryRun=true
JSON
{
  "dryRun": true,
  "plan": {
    "deletes": "the whole project shop",
    "services": ["web", "db"],
    "environments": 1,
    "creditForfeited": 4200000,
    "earningsToWithdraw": 0,
    "restorableUntil": 1767830400000,
    "kept": "the ledger, payments and statements (financial records)"
  }
}

Money is in micro-USDC. Then delete it for real:

API
DELETE /v1/projects/:id
JSON
{ "deleted": true, "restorableUntil": 1767830400000, "restore": "POST /v1/projects/:id/restore" }

The same route on an environment (a project with a parent) deletes just that environment, at once and with its data. That needs an admin, not an owner, and has no trash period.

What happens straight away

  • Every service in the project and in its environments stops and goes to the trash, with its data marked for deletion. Public database ports close.
  • Every API key of the project and its environments is revoked.
  • The project disappears from everyone's project lists. Requests for it answer NOT_FOUND, with details.restorableUntil and details.restore.

Restore it within 7 days

In the dashboard: your Account page lists Recently deleted projects with the date each will be gone for good. Click Restore.

With the API:

API
GET /v1/me/deleted-projects
POST /v1/projects/:id/restore

GET /v1/me/deleted-projects lists the projects you own that can still be restored: id, name, deletedAt and restorableUntil. Restoring needs an owner, signed in as a person, and answers with the services that came back:

JSON
{ "restored": true, "services": ["web", "db"] }

Services come back stopped, with their data. Deploy them again to start them. The API keys revoked when you deleted the project stay revoked, so make new ones for your agents. Restoring after the 7 days answers CONFLICT.

After 7 days

The usual trash purge deletes the services' data and their backups. Then CLI removes the project's members, keys, shared variables, schedules, notification channels, tunnels, share links and security settings, and renames it "deleted project".

CLI keeps the project's ledger, payments and statements. They're financial records the law asks a business to keep. Copies of deleted data in CLI's own backups age out with those backups (14 days).

Delete your account

You can delete your account once you own no live projects. Delete each project you own, or make someone else its owner, first. Projects in the trash don't block you, but deleting your account removes your ownership of them, so you can no longer restore them.

Who can do it: you, signed in as a person. API keys get FORBIDDEN. If you have a second factor, CLI asks you to confirm with it first.

In the dashboard

On your Account page, under Delete your account, click Delete my account…. If you still own projects, CLI lists them. Otherwise type DELETE and click Delete my account. You're signed out.

With the API

See what's in the way first:

API
GET /v1/me/delete
JSON
{ "ownedProjects": [{ "id": "prj_…", "name": "shop" }], "memberships": 3 }

When ownedProjects is empty, delete the account:

API
DELETE /v1/me

It answers 204. While you still own projects it answers CONFLICT, with the projects in details.projects.

What goes and what stays

Deleting your account removes:

  • your memberships in every project,
  • every session (you're signed out everywhere),
  • your authenticator app, passkeys and any pending second-factor challenges,
  • your linked GitHub and chat accounts,
  • your push notification subscriptions, inbox read markers and identity-check outcomes.

CLI keeps a one-way hash of your sign-in (your email, GitHub id or wallet) in place of it on your welcome credit, so the same sign-in can't claim free credit again. A record that an account was deleted, with that hash and the time, goes into the operators' compliance evidence.

Entries that name you in project audit logs and the sign-in log aren't rewritten. They're removed with the rest of the log when the server's retention period ends (90 days unless the operator keeps them longer, see /docs/self-hosting).

For operators

Deletions appear in the evidence export's deletions section: each project deleted in the period (in the trash or purged) and who deleted it, and each account deleted (by its hash). See SOC 2 readiness.