diff --git a/docs/presto/faq-Avoiding Vendor Lock-In.mdx b/docs/presto/faq-Avoiding Vendor Lock-In.mdx index 335959e..f406a77 100644 --- a/docs/presto/faq-Avoiding Vendor Lock-In.mdx +++ b/docs/presto/faq-Avoiding Vendor Lock-In.mdx @@ -165,6 +165,7 @@ However, **planning and preparation** (runbooks, approvals, security checks, reh
How long do you retain data after shutdown? + A common baseline is: - **Up to 1 month after stopping the network**, if requested by the customer in the termination notice. @@ -177,6 +178,7 @@ Longer retention windows are typically negotiable (storage footprint, compliance
What happens if Gateway stops operating the infrastructure? + If Gateway-operated infrastructure goes offline: - the network **stops producing new blocks** until the infrastructure is restored or replaced. @@ -190,6 +192,7 @@ If all resources (servers and data volumes) were deleted without appropriate han
Is there a recovery process for the network and assets? + Yes. A typical recovery approach relies on redundancy: - multiple nodes maintain replicas of the sequencer/node data, @@ -202,6 +205,7 @@ Yes. A typical recovery approach relies on redundancy:
Can we recover and operate independently without Gateway support? + In many cases, yes—provided the customer has the necessary data and operational access. **Optional resiliency path (if enabled): Blob-DA add-on** @@ -214,13 +218,13 @@ If the customer operates their own nodes and/or a Blob-DA + database backup setu Gateway support is **not strictly required**, but often preferred for faster turnaround and reduced operational risk. -
---
Summary + ## Summary: what “no vendor lock-in” means with Gateway RaaS - **Your rollup’s core stack is transferable** (open-source + portable state/config).