> For the complete documentation index, see [llms.txt](https://docs.replicacyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.replicacyber.com/faqs/virtual-environment-lifetime-and-best-practices.md).
# Virtual Environment Lifetime and Best Practices
### How long can I use a VE before it is deleted?
There is no fixed expiration date on a Replica VE. VEs are designed to have flexible lifespans, ranging from minutes to months. Your company's business policies generally dictate if or how often a VE should be deleted. Our recommendation is to delete the VE when the activity you created the VE for is completed. These activities are usually discussed during intake as we help you become productive in Replica quickly. However, if you find yourself doing new activities that may benefit from a discussion with our product team, please send a request to
### Why should I delete a VE after I use it?
Replica Cyber was founded with the mission to protect life online and we take this mission seriously. The longer a VE lives (with internet connectivity) the more things need to be considered including security and functionality updates. Deleting a VE after use reduces risk to users and organizations. If you have a use case that would benefit from a discussion with our product team, please send a request to
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.replicacyber.com/faqs/virtual-environment-lifetime-and-best-practices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.