# Platform Overview Virusis is built around a guided investigation experience rather than a collection of disconnected tools. ## The core product journey * a user submits a file, URL, or IP * the platform evaluates the item through multiple analysis layers * findings are organized into one readable result view * teams share, export, or act on the report ## Product building blocks * guided submission experience * layered analysis and classification * threat and context enrichment * file-level inspection where relevant * reporting and collaboration * access controls for different user journeys ## Why the product feels unified Virusis is designed to keep users in one investigation surface instead of sending them across multiple disconnected views. * different input types follow one familiar journey * result pages are structured for fast reading * reports can be shared with other stakeholders * explainers and policy pages sit next to product guidance instead of outside it ## What external readers should take away * Virusis is built to help teams review suspicious inputs quickly. * The experience is layered, not flat: submissions, findings, context, and reports all work together. * The public documentation should focus on those outcomes rather than on internal implementation details. --- # Agent Instructions: 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: ``` GET https://docs.virusis.com/getting-started/architecture.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.