# Public vs Premium

The architectural relationship between the two web surfaces.

## Same catalog, different surfaces

Both Stratix Public and Stratix Premium read the same global catalog: 175+ models, 52+ benchmarks, 2,000+ public evaluations, public spaces. Premium augments that catalog with **org-scoped private items**: private models (BYOK), private benchmarks, private evaluations, judges, scorers, traces, spaces.

## What changes between them

| Aspect      | Public           | Premium             |
| ----------- | ---------------- | ------------------- |
| Catalog     | global           | global + your org's |
| Authoring   | none             | full                |
| Persistence | none (anonymous) | full                |
| Compute     | none (no runs)   | ECU PAYG            |
| Data scope  | global           | org-scoped          |

## Switch toggle

When logged in, the **Switch toggle** flips Premium's catalog views between Public-only and Premium-augmented. Use Public-only mode to see exactly what an anonymous visitor sees.

## Why the split exists

* **Public** is for browse, research, citation. Optimized for low-friction discovery.
* **Premium** is for build, evaluate, govern. Optimized for team workflow.

Splitting them lets the public surface stay fast and anonymous while the workspace stays deep.

## Where to next

* [Stratix Public](https://github.com/LayerLens/gitbook-full/blob/main/05-select/catalog/README.md)
* [Stratix Premium](https://github.com/LayerLens/gitbook-full/blob/main/05-select/catalog/premium-workspace-overview.md)
* [Switch toggle](/11.-admin/switch-toggle.md)
* [Public-vs-Premium feature matrix](/5.-select-pick-the-model/public-vs-premium-1.md)


---

# 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.layerlens.ai/5.-select-pick-the-model/public-vs-premium-1.md?ask=<question>
```

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.