a month ago
Hi everyone,
I currently have a Hobby workspace with an existing project. I’m considering a separate Pro workspace for a short pilot using PostgreSQL and a small web application, without changing my existing workspace.
Before subscribing, I’d appreciate clarification on a few things:
Can I schedule cancellation/nonrenewal for a future date while keeping deployments running until then? The FAQ says cancelling stops deployments immediately. If scheduling isn’t supported, what’s the recommended approach?
Where can I confirm the billing-cycle end date and that the subscription won’t renew?
After stopping deployments and cancelling, do volumes, backups or restore-created resources continue accruing charges? What needs to be deleted to stop further charges?
Would the new Pro workspace have independent billing and usage limits, leaving my existing Hobby workspace unchanged?
I haven’t created the new workspace yet—just looking to understand the setup and cleanup process.
Thanks!
1 Reply
a month ago
Cancelling takes effect when you click it: deployments in that workspace stop right away to prevent further charges, and the plan stays active until the end of the billing cycle. For a seven-day pilot, the simplest approach is to keep it running for as long as you need, then cancel from the Active Plan section of the new workspace's Billing page when you're done. The billing cycle is anchored to the date you subscribe, and that billing page is where you manage the plan.
Stopping deployments ends compute charges, but stored data doesn't become free. Volumes and their backups keep accruing storage charges, even when detached, until they're deleted. After you delete them, there's a recovery window of about 48 hours, and storage keeps billing during that window too. Deleting the pilot project removes its databases, volumes and any restore-created resources together, after the same 48-hour recovery window. Usage is billed in arrears, so expect one final invoice for usage up to cancellation.
Each workspace has its own subscription, billing cycle and usage limits, so a new Pro workspace won't change your existing Hobby workspace.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved kirbs7 • about 1 month ago