Description
I recently tried deploying the project myself and attempted an independent deployment on AWS, but the cost of deployment is too high for me at the moment. I would prefer to use the SaaS version in the early stages. However, my main challenge right now is that I need the sandbox to stay active for a longer period — or at least not count down the time when it's paused. It would be really helpful if the active duration could be extended, even something like 160 hours would be great.
I am simulating operations using Python, and I use it for a short time each day on a long-term basis. For a better user experience, I don't want users to log in every day. Therefore, I need to preserve the browser cache and also ensure that the sandbox can persist for a long time.
I hope the sandbox can be retained for a longer period. If it's difficult to make it permanent or to keep it active for a very long time, I'd like to extend the current 24-hour limit for Pro accounts — for example, how about increasing it to 160 hours? A single sandbox running for only 24 hours is too short for my use case.
I also reviewed the beta version of the SDK — if it can ensure that the time when the sandbox is stopped is not counted toward the usage limit, then I would need at least 48 hours of available sandbox time.
In this way, my use case would work as follows:
Start the sandbox
Provide Python code to the sandbox and execute it
Pause the sandbox after execution is complete
This approach allows me to precisely control the sandbox runtime. With a 48-hour limit, it should theoretically be enough for a single user to use it for about a month.