> For the complete documentation index, see [llms.txt](https://docs.visdom.virtuslab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visdom.virtuslab.com/built-by-virtuslab.md).

# Built by VirtusLab

VirtusLab's engineers have spent over a decade helping organisations solve software delivery and developer productivity problems at scale. We maintain core open-source infrastructure (the Scala toolchain, Metals, Scala CLI), contribute to the JVM ecosystem, and build production-grade tooling for environments where the cost of getting it wrong is high.

Visdom is designed by practitioners: it runs our own delivery before it runs anyone else's, and every mechanism described in this documentation is one the team uses daily.

|                 |                   |
| --------------- | ----------------- |
| **15+**         | years on market   |
| **500**         | engineers         |
| **Open Source** | in our DNA        |
| **Scala & JVM** | core contributors |

## What that has produced elsewhere

| Result                  | Change  | Where                                                                                      |
| ----------------------- | ------- | ------------------------------------------------------------------------------------------ |
| Build time              | −88%    | Global logistics, Scala monorepo, sbt to Bazel: 40–60 minutes down to 5                    |
| Pull request merge time | −43%    | Investment bank, Scala monorepo, managed IntelliJ IDEA                                     |
| Agent iteration speed   | \~50/hr | The target cadence for coding agents, and the speed today's pipelines have to keep up with |

Client names are under NDA; full write-ups are on the VirtusLab success stories page.


---

# 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.visdom.virtuslab.com/built-by-virtuslab.md?ask=<question>&goal=<endgoal>
```

`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.