# VirtusLab — Agent / LLM site guide **Canonical origin:** `https://virtuslab.com` (and may also respond on `https://www.virtuslab.com` depending on redirect configuration). This file is a **machine-oriented map** of the public marketing site: what the organization is, what each major area is for, and stable entry URLs. It is **not** API documentation. The site is **static content** (pages, articles, case studies, news). ## Agent Content API All public pages are available as **Markdown** via the `/api/agents/` endpoint: - **Index (all available pages):** [`/api/agents/`](https://virtuslab.com/api/agents/) - **Homepage:** [`/api/agents/homepage`](https://virtuslab.com/api/agents/homepage) - **Pages:** `/api/agents/pages/{slug}` — e.g. `/api/agents/pages/about-us` - **Blog articles:** `/api/agents/blog/{slug}` — e.g. `/api/agents/blog/some-article` - **Company news:** `/api/agents/company-news/{slug}` - **Success stories:** `/api/agents/success-stories/{slug}` - **Landing pages:** `/api/agents/lp/{slug}` All responses use `Content-Type: text/markdown` with YAML frontmatter (title, url, description, date, authors, tags). --- ## Site overview **What this organization is.** VirtusLab is an enterprise-focused software engineering consultancy with long tenure in **JVM developer tooling** and related ecosystems (especially **Scala**). It presents itself as part of **VirtusLab Group**—a consortium of companies combined to deliver broader software services. **Primary audience.** Technical leaders and engineering teams at large organizations who need **modernization**, **performance** (for example build pipelines and IDE/tooling responsiveness), **platform work** (data, cloud-native, frontends, reactive backends), and **AI-era delivery** practices—not generic consumer traffic. **Core narrative (homepage and related copy).** The site emphasizes **developer productivity** and **IT systems adapted for AI-heavy engineering**: practical experience with what fails under load, what scales, and what ships when deadlines matter. **VISDOM** is the named offering tied to **AI-operable software delivery** at enterprise scale (positioning, not API spec here). **Theme clusters visitors will see repeated across pages:** - **Tooling and velocity:** Build-system work (including **Bazel**), JVM/IDE performance claims, migration and version-upgrade programs (**Scala 3**, language/runtime moves). - **AI and agents:** Human-in-the-loop adoption framing, data platforms as a precursor for insurers and similar sectors, **MCP** and **agentic AI** on the JVM as editorial/positioning topics. - **Delivery breadth:** **Expertise** and **services** describe *what* the firm does; **capabilities** organize it into **data**, **cloud-native**, **frontend**, and **backend** pillars; **solutions** package outcomes; **sectors** maps offerings to industries. - **Trust and depth:** **Success stories** supply engagement narratives; **blog** carries technical depth; **company news** covers organizational updates. - **Values and talent:** **About** covers culture (ownership, empathy, impact, pragmatic technical choices, long-term partnerships), innovation/open source, community, and programs (**internships**, **PhD** collaboration, internal learning **Virtusity**). **How to use this site as an information source.** For *positioning and services*, start with **Home**, **Expertise**, **Services**, **Capabilities**, **Solutions**, and **Sectors**. For *evidence and opinion*, use **Success stories** and **Blog**. For *organizational facts and announcements*, use **Company news** and **About**. For *ecosystem stance*, use **Community**. --- ## Page index (URLs and what each contains) ### Institutional and home - **https://virtuslab.com/** — Primary landing: value proposition for **AI-era developer productivity**, JVM tooling credibility, enterprise consulting, **VISDOM**, and thematic hooks (performance metrics in marketing copy, AI adoption, MCP/agentic AI topics as surfaced on the page). - **https://virtuslab.com/about-us** — Mission, culture, **VirtusLab Group** structure, operating principles (partnership vs transactional work), innovation/open source, community role, team values, and people programs (**internship**, **PhD**, **Virtusity**). ### Commercial structure (what they sell and how it is organized) - **https://virtuslab.com/expertise** — Consolidated view of technical domains and engagement types (examples referenced sitewide: AI foundations for developers, Scala education/migration, large codebase migration, Bazel, Strapi-related consulting/plugins/migrations, rapid POC “vibe engineering,” etc.—exact list may evolve with CMS). - **https://virtuslab.com/services** — How **end-to-end software engineering services** are described across the lifecycle for client delivery. - **https://virtuslab.com/capabilities** — Pillar breakdown: **data** (analytics maturity/self-serve patterns), **cloud-native** (efficiency, speed, cost control), **frontend** (advanced web and mobile UI engineering), **backend** (high-performance reactive backends, modernization framing). - **https://virtuslab.com/solutions** — Outcome-oriented views that tie problems to VirtusLab’s implementation and consulting patterns (paired with sector and capability content). - **https://virtuslab.com/sectors** — Vertical/industry angles for the same service stack (site materials reference manufacturing and mobile contexts among others). ### Editorial, proof, and news - **https://virtuslab.com/blog** — Technical articles and commentary: engineering practice, JVM/Scala ecosystem, tooling, platforms, delivery, AI/agent topics as published. - **https://virtuslab.com/success-stories** — Client narratives: context, work performed, and results as presented for marketing credibility. - **https://virtuslab.com/company-news** — Corporate announcements: milestones, partnerships, hiring, events, and initiative updates. ### Ecosystem - **https://virtuslab.com/community** — Community participation narrative: events, collaboration, open-source involvement as part of brand and recruiting. --- ## Retrieval note for agents Prefer **this index** plus **direct page fetches** over undirected crawling when the goal is factual grounding about VirtusLab’s public positioning. For a **complete, current inventory of public URLs** (including individual blog posts, success-story pages, news items, and other routes not listed above), use the published sitemap index: **https://virtuslab.com/sitemap-index.xml**. It is a standard XML document that references one or more child sitemaps; those list loc paths, and may include `lastmod` hints. Fetch and parse when you need exhaustive discovery; use this `llms.txt` when you need **prioritized context** about what each major section is for.