Deleting an environment immediately removes the services and volume instances inside it, with no grace period and no restore path. The volume data for Postgres-CjaQ was destroyed along with the environment, and we're not able to recover data lost through user-initiated deletions. For context, the 48-hour restore window applies only to project-level deletions from the dashboard, not to environment or service deletions.

Thanks — I understand the volume itself is gone. But my question is

specifically about the scheduled volume BACKUPS, which are separate

snapshot artifacts, not the volume.

Your billing shows BACKUP_USAGE_GB for this exact volume right up to

the deletion:

August 2026: 1130.6 GB-minutes (avg 0.0253 GB)

Sept 1-7, 2026: 78.3 GB-minutes (avg 0.0078 GB)

So backup snapshots for this volume existed and were being billed to me

days before the deletion. Your API exposes volumeInstanceBackupList and

volumeInstanceBackupRestore for exactly this.

Volume: 2ef8d558-5d01-4044-80ed-3ec86f3314cf (postgres-cjaq-volume)

         the volume record itself still exists in my project

Service: 99d32888-c33d-4360-830e-88a839aa8166 (Postgres-CjaQ)

         deletedAt 2026-09-08T12:12:04.826Z

Environment: e21f830b-c782-4e0a-9c0a-c947c840100f (ValiBook)

         deletedAt 2026-09-08T12:12:09.991Z

Project: bd274e4c-12a7-45a3-af9d-1ee9989342ac

Please check whether snapshots for this volume still exist in your

storage layer, even if they are not exposed to me. This database was

the production DB for two live services and there is no other copy.

Thanks a lot

Volume backup creation, restoration, and scheduling are Pro-plan features, and this workspace is on Hobby, so no user-configured scheduled snapshots would have existed for this volume. The BACKUP_USAGE_GB billing you see reflects incremental storage from any platform-created snapshots (such as pre-patch or pre-resize snapshots) that were present while the volume instance was alive. Those snapshots are stored on the volume instance itself, not in a separate store, so when the environment deletion destroyed the volume instance, the snapshot data went with it. We aren't able to restore data lost through user-initiated deletions, including from backup artifacts that were tied to the deleted volume.

Yes, I understand, thank you :( Please, is there anyone on your team who might be able to recover and export at least some data from the deleted database? Any help would be greatly appreciated. Thank you!

We understand how important this data is, and we're sorry for the situation. Unfortunately we aren't able to recover or export data from a deleted environment, and there isn't a path for our team to do so on your behalf either. We truly wish we had a better answer here.