# From Products to Ecosystem

Vertical started as a product company. We built Vertical Stream for AI-powered content generation, Vertical Motion for video creation, Vertical Studio for no-code model customization, and Vertical Cloud for decentralized compute. All shipped. All gained traction.

Then we asked ourselves:

> What if these products weren't standalone? What if every product we build, every service we offer, and every project we onboard all strengthened the same ecosystem?

So we evolved.

| Before                     | Now                                       |
| -------------------------- | ----------------------------------------- |
| Standalone products        | Connected ecosystem                       |
| Product-specific utilities | Ecosystem-wide utility layer              |
| Fragmented revenue streams | Multiple products, shared token utility   |
| Value stays siloed         | Utilities and rewards flow through VERTAI |

#### **Today, Vertical operates as an ecosystem with two pillars:**

**1. Vertical Products** AI solutions with clear target users and direct revenue models.

**2. Vertical Services** Onboarding, execution, and advisory that bring external projects into the ecosystem.

Everything connects through **VERTAI** and the **Vertical Gateway**: the shared loyalty and utility layer that rewards long-term participation across all products and services.

> We don't restart every cycle. We compound.


---

# 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.verticalstudio.ai/introduction/from-products-to-ecosystem.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.