> For the complete documentation index, see [llms.txt](https://docs.layerlens.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.layerlens.ai/more-in-this-section/brand-assets.md). # Brand assets Use this page to reference LayerLens Stratix correctly in partner materials, press, conference programs, and integrations. For anything not on this page — extended logo lockups, motion assets, talking points for a specific announcement — email . ## Product naming Use the name that matches the level of context the reader already has. | Form | When to use | | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **LayerLens Stratix** | First mention in any document, headline, press release, or partner page. | | **Stratix** | Second and subsequent mentions inside the same document. Also fine in product UI and conversational copy where the LayerLens parent brand is already established. | | **Stratix Public**, **Stratix Premium**, **Stratix SDK** | When the specific experience matters — public catalog, logged-in workspace, or Python client. | Do **not** refer to the product as "LayerLens" on its own when the context is the evaluation platform. LayerLens is the parent brand; Stratix is the product. Calling the product "LayerLens" creates ambiguity for partners and analysts. Also avoid the legacy internal codename ATEAM in customer-facing materials. ## Logos and isotype The canonical logo files live in the `docs/logos/` directory of this repository. | Asset | File | | ----------------------- | -------------------------------- | | Wordmark, color | `docs/logos/LL-logo.svg` | | Wordmark, light-on-dark | `docs/logos/LL-logo-white.svg` | | Isotype (symbol only) | `docs/logos/isotype.png` | | Isotype, 512x512 PNG | `docs/logos/isotype-512x512.png` | For social avatars, favicons, and small-format placements, use the isotype. For everywhere else, use the wordmark. Keep at least the height of the "L" as clear space on every side. For high-resolution vector assets, EPS, or extended lockups, contact . ## Color palette These are placeholder reference values for documentation. The authoritative palette — including AA / AAA contrast pairings, dark-mode tokens, and gradient stops — is owned by the design team and ships with the design system. Confirm any production use with before publishing. | Role | Token | Hex | | --------------- | ----------------------- | --------- | | Primary | `stratix.primary` | `#5046E5` | | Secondary | `stratix.secondary` | `#1A1A2E` | | Accent | `stratix.accent` | `#22D3EE` | | Surface — light | `stratix.surface.light` | `#FFFFFF` | | Surface — dark | `stratix.surface.dark` | `#0B0B1A` | | Text — primary | `stratix.text.primary` | `#0F172A` | | Text — muted | `stratix.text.muted` | `#475569` | ## Voice The Stratix voice is declarative and technical. We respect the reader's time and assume they are smart, busy, and skeptical of marketing claims. * **Declarative, not hyped.** State what the product does. Skip the adjectives. * **No exclamation marks.** None. * **No superlatives** ("the best", "world-class", "revolutionary", "game-changing"). Replace with what the product actually does. * **Specific over vague.** "175+ models, 52+ benchmarks" beats "comprehensive coverage." * **Honest about scope.** If a capability is on the roadmap, say "on the roadmap." Do not imply it ships today. * **Active voice.** "Stratix scores your traces" not "Your traces are scored by Stratix." * **Sentence case** for headings. When in doubt, lean toward the tone of a senior engineer explaining the system to a peer. ## Boilerplate — one paragraph > LayerLens Stratix is an AI evaluation platform built for teams shipping AI to customers. The public catalog scores 175+ models against 52+ benchmarks and is refreshed quarterly, so anyone evaluating a model can answer "which is actually best at my task" in minutes — no signup required. The workspace lets teams run private evaluations on their own data, build LLM judges that capture their team's quality bar, ingest live traces, and wire all of it into CI/CD. Stratix is delivered as three experiences — a free public catalog, a logged-in workspace with pay-as-you-go compute, and a Python SDK — sharing one catalog, one judge engine, and one trace pipeline. ## Boilerplate — one sentence > LayerLens Stratix is the AI evaluation platform that lets teams pick the right model, score it on their own data, and govern its quality in production. ## Press kit For the full press kit — extended copy, headshots, screenshots, customer quotes (where permitted), and the latest fact sheet — contact . ## Where to next * [What is LayerLens Stratix?](/1.-introduction/what-is-layerlens-stratix.md) * [Trust and security](/more-in-this-section/trust.md) * [Schedule a demo](/more-in-this-section/schedule-a-demo.md) * [How Stratix compares](/1.-introduction/how-stratix-compares.md) --- # 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.layerlens.ai/more-in-this-section/brand-assets.md?ask=&goal= ``` `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.