# When a subscription lapses

> A declined card or a cancelled plan closes the door, and nothing else. The agents keep running, nothing is deleted, and the machine is still yours.

A machine checks in with us every five minutes and gets back a signed note
saying it is paid for. That note is good for a day, so an ordinary bad
afternoon — a closed laptop, a moved office, a problem at our end — is
invisible. There are 288 chances to renew before anything is felt.

## What happens when it does lapse

**The door closes.** You cannot open the machine's panel any more.

**The agents do not stop.** Processes keep running, work that was happening
keeps happening, and nothing on the machine is deleted, touched or shut down.
What is closed is the way in, not the machine.

**Nothing is taken.** Your code, your chats, your logs, your variables
and your git history are exactly where they were.

## Two different sentences, on purpose

A machine that has lost us cannot tell the difference between "the cabinet said
no" and "somebody put a firewall in the way". So it does not guess:

- **It heard a refusal**: *this machine's seat is gone — the workspace it
  answers to is not paying for it.*
- **It heard nothing**: *this machine has not been able to reach its cabinet —
  it starts again on its own as soon as it can.*

## What still works on a refused machine

The agents, `beafk status`, `beafk doctor`, and uninstall. Updates wait until
you are paying again. The **Updates** screen still lists the machines, with a
bar that says billing needs sorting out.

## Getting it back

Pay again. The machine notices within a few minutes and the door opens. There
is nothing to reinstall.

If what lapsed was a card that was declined, you have two days before any of
this happens at all — see
[if a payment fails](https://beafk.app/docs/changing-your-plan.md#if-a-payment-fails).

## If you are done with us

The machine is yours. `sudo beafk cloud forget` stops it answering to any
cabinet, and `sudo beafk uninstall` takes beafk off it entirely. Your projects,
your git history and your agents' own sign-ins are not ours and are not touched
by either.

---

beafk documentation · Plans and billing · https://beafk.app/docs/when-a-subscription-lapses

In this section:
- Plans — https://beafk.app/docs/plans.md
- Changing your plan — https://beafk.app/docs/changing-your-plan.md
- When a subscription lapses — https://beafk.app/docs/when-a-subscription-lapses.md (this page)

Every page, one line each: https://beafk.app/docs/llms.txt
All of it in one file: https://beafk.app/docs/llms-full.txt