Leaving does not mean exporting the site out of Everbase. The site was never locked to an Everbase account. It is on The Everbase Stack, in hosting, GitHub, and Sanity accounts your organization owns.

The site stays yours

Remove Everbase from those accounts when you want the access gone. The handover accounts list is the checklist: owner, current access, and when to remove it. Do that in the provider's own settings. Do not send passwords in chat to speed it up.

The live site keeps serving from your Cloudflare account. Editors keep using your Sanity project. The code stays in your GitHub organization. None of those shut off because Everbase lost access.

Continuous development

Continuous development has no minimum term. Pause or cancel any month. Pausing it stops new code requests. It does not unpublish the site, and it does not remove your editors.

Included hypercare is the 30 days after launch. It covers migration defects and the agreed launch checks. It is not a subscription you cancel. New pages, redesigns, and later requests are separate from those 30 days.

What you should take with you

Before you remove access, keep the handover doc, the recordings, and the accounts list. Confirm a person on your team can publish to production. Confirm the repository is in your organization, not only shared with you. Then remove the access you no longer want.