Browser & Vercel
The web interface provides access to the test environment. Its server-side intermediary forwards requests to the backend service; technical access keys remain on the server.
For a single negotiation or a complex deal: how is context processed? How can preparation continue later? Explore the roles of the technology behind Vanellence.
Inside the pilot environment. These views show the local session prototype and the protected web test environment using test data. Product access is not yet open for public sign-up or purchase.
The interface, sign-in, processing and storage have different roles. This separation makes it easier to understand how a briefing takes shape and which components work together.
The web interface provides access to the test environment. Its server-side intermediary forwards requests to the backend service; technical access keys remain on the server.
Sign-in in the test environment uses a dedicated identity service. It associates users with their sessions, while the application handles the actual processing.
The backend service runs in a Docker container in Frankfurt. Its defined runtime helps the team operate and assess a specific application version consistently.
The local bridge prototype keeps its conversation context in working memory and has no conversation database for that context. This describes the local prototype’s storage path.
A saved test briefing can be reopened after reloading the page or restarting the service. This allows continued work to be explored using a specific test case.
Versioned source and checks make the changes in an application version traceable. They give development and review a shared reference point.
This overview explains technical responsibilities and data paths. Vanellence’s domain methodology remains protected.