Skip to content

rfc: pilot offboarding via credible exit #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
parkan wants to merge 1 commit into
base: main
Choose a base branch
from
Open

rfc: pilot offboarding via credible exit #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion rfcs/2026-09-forge-instances.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,10 @@ production nodes as much as possible.
Typically, we will need to quickly stand up a new pilot region within 72 hours, keep it running &
meeting SLAs for 90 days, and decommission it after that.

We will _not_ offer data migration from pilot regions to production.
We will _not_ offer data migration from pilot regions to production. Customers who want to keep
their data can use the [credible exit export](2026-08-credible-exit-under-encryption.md): a
key-manifest CAR produced before decommission remains decryptable with the customer's key after the
pilot instance is gone.

- **Update frequency:** Manually triggered updates. Typically once before the pilot starts and then
when the customer requests new features or we need to fix bugs.
Expand Down
Loading