One package, two connected responsibilities
Retvest Deploy is the business offering for AI on your company’s own servers. RIL stands for Retvest Intelligence Layer and is included as the system of record for AI work. Plan the environment and the record together: where work happens, who can use it and what needs to be retained.
The full Deploy environment
The product scope brings together Retvest Chat, Work and Code; Chrome and Office integrations; computer use and software teaching; internal and customer-facing agents; permission-aware company knowledge; administration; and RIL records. These are parts of one Deploy offering, with availability and integration boundaries agreed for each pilot.
Read the full platform overview and the integration boundaries before choosing a workflow. Generated files, browser automation and standalone Sidekick teaching do not establish live Office, Chrome or corporate integration availability.
Choose how your team connects
The web workspace is the shared graphical interface for employees and authorised administration. The Retvest terminal supports command-line work against the company server. Python and TypeScript clients connect your own applications. These are different ways into the same company environment, with access controlled by the server.
RIL sits inside this package. The model supplies intelligence; the Retvest Intelligence Layer provides the record of the work and its review. Define both the task and the record requirements when planning an integration.
Start with one workflow
Choose a task your team can evaluate, such as asking questions about an approved collection of documents. Identify the users, the source material and the person responsible for reviewing the outcome.
- Describe the task and the result the team needs.
- Select a small set of approved sample material.
- Identify the company server and model endpoint.
- Agree who can access the environment and its records.
- Define the evidence needed to decide whether to expand the pilot.
Map where the information goes
For a document-question workflow, identify the approved source collection, the application storing it and the model endpoint receiving the task context. Include optional tools in that map: a web request or external service can introduce a separate data destination. Company ownership of the application server does not automatically describe every connected service.
For the pilot, record the intended task, input material, expected answer quality, required human review and evidence to retain. This gives the business owner a concrete basis for deciding whether the workflow is useful.
Bring the right people into the conversation
The business owner defines the workflow. The infrastructure owner provides the server and model path. The information owner agrees access and retention. The developer connects any application or automation in scope.
What to prepare for a walkthrough
Bring a short description of the workflow, your intended infrastructure and the records you need. Do not send credentials or private documents with the initial enquiry. Installation scope, versions, access and operating responsibilities are agreed for the pilot.