> For the complete documentation index, see [llms.txt](https://myros.gitbook.io/bp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://myros.gitbook.io/bp/product-scope/premium.md).

# Scaling

Myros is built on an open foundation.

The core purpose of Myros is to help projects, builders, businesses, and communities launch real-time, knowledge-aware AI agents from their own curated sources. Builders should be able to self-host, modify, extend, and deploy their own intelligence layer without depending entirely on closed, centralized systems.

That foundation matters because project knowledge is not static anymore.

It lives across websites, documentation, announcements, support pages, community posts, internal notes, developer resources, files, and operational systems. As teams grow, their knowledge becomes harder to manage, harder to keep current, and harder for users to access.

Myros begins by making that knowledge conversational.

Over time, Myros can expand into a deeper knowledge infrastructure layer for teams that need more scale, more control, more source coverage, and more insight into how their communities interact with information.

**From Open Framework to Scalable Knowledge Layer**

The open-source foundation gives builders a practical way to launch and customize Myros agents.

Expanded capabilities are designed for projects and organizations that need to operate Myros at higher volume, across more sources, with stronger management tools and deeper visibility.

This allows Myros to remain accessible while creating room for advanced infrastructure, professional deployment support, and organization-grade knowledge systems.

#### Future Expanded Capabilities

<table><thead><tr><th width="267">Capability</th><th>Description</th></tr></thead><tbody><tr><td>Business and Enterprise Agent Tiers</td><td>Expanded Myros deployments for teams that need higher source capacity, larger usage limits, faster response cycles, and more scalable agent infrastructure.</td></tr><tr><td>Multi-Source Knowledge Ingestion</td><td>Support for additional knowledge formats beyond websites, including PDFs, TXT files, CSVs, DOCX documents, structured files, GitHub repositories, Notion pages, and other curated sources.</td></tr><tr><td>Advanced Retrieval Infrastructure</td><td>Vector embeddings, similarity search, crawler caching, source freshness logic, and optimized retrieval pipelines to improve speed, accuracy, and reliability.</td></tr><tr><td>Premium Admin Dashboard</td><td>A visual control layer for managing sources, monitoring agent activity, reviewing user questions, and improving the quality of the knowledge base over time.</td></tr><tr><td>Knowledge Analytics Suite</td><td>Insights into popular questions, unanswered topics, user engagement, source quality, and content gaps so teams can understand what their communities are trying to learn.</td></tr><tr><td>Custom Myros Agent Setup</td><td>Dedicated setup support for teams that want Myros configured around their brand identity, source structure, personality, community flow, and deployment needs.</td></tr><tr><td>Advanced Crawling and Source Refresh</td><td>Smart crawling schedules, change detection, freshness checks, and source update monitoring for projects with frequently changing information.</td></tr><tr><td>Team and Multi-Admin Controls</td><td>Role-based access, multi-admin management, team permissions, shared workflows, and internal controls for larger organizations.</td></tr><tr><td>Private and Internal Knowledge Agents</td><td>Closed knowledge environments for teams that want to use Myros for internal documentation, operations, onboarding, customer support, product knowledge, or company processes.</td></tr><tr><td>Multi-Platform Interfaces</td><td>Expansion beyond Telegram into Discord, web chat, API-based integrations, and other environments where communities and teams already work.</td></tr><tr><td>White-Label and Custom Deployments</td><td>Tailored Myros deployments for organizations that need branded agents, dedicated infrastructure, private hosting, custom integrations, or advanced support.</td></tr><tr><td>Plugin and Integration Modules</td><td>Future modules that allow builders to extend Myros with new tools, workflows, source connectors, agent behaviors, and community-built capabilities.</td></tr></tbody></table>

#### Growth Model

Myros is designed to grow without closing its foundation.

The open-source framework gives builders access to the core system. Advanced layers can support teams that need more capacity, deeper control, managed infrastructure, analytics, private deployments, or customized integrations.

Potential growth paths may include:

<table><thead><tr><th width="263">Model</th><th>Description</th></tr></thead><tbody><tr><td>Open-Core Access</td><td>The core Myros framework remains accessible for builders and communities, with expanded capabilities available for higher-scale use cases.</td></tr><tr><td>Usage-Based Agent Plans</td><td>Plans based on source volume, request usage, crawling frequency, storage, retrieval needs, or agent activity.</td></tr><tr><td>Business and Enterprise Subscriptions</td><td>Monthly or annual plans for organizations that need dashboards, analytics, team controls, higher limits, priority infrastructure, and advanced source management.</td></tr><tr><td>Managed Deployment Services</td><td>Optional implementation support for teams that want help deploying, configuring, branding, and maintaining their Myros agents.</td></tr><tr><td>Private and White-Label Licensing</td><td>Custom deployments for organizations that need private infrastructure, branded agents, dedicated environments, or deeper integration with internal systems.</td></tr><tr><td>Plugin and Module Ecosystem</td><td>Future paid or community-created modules for specialized integrations, workflows, data sources, and agent capabilities.</td></tr></tbody></table>

***

Knowledge is becoming one of the most important interfaces between projects and their users.

When project knowledge is scattered, users feel lost.\
When documentation is outdated, trust weakens.\
When teams answer the same questions repeatedly, communities slow down.\
When users can speak directly to trusted knowledge, the project feels more alive.

Myros is built to make that shift possible.

The first layer is an open-source framework for launching real-time knowledge agents.

The next layer is scalable knowledge infrastructure for teams, communities, and organizations that need living knowledge to operate reliably across more sources, more users, and more interfaces.

Every community should be able to access living knowledge.

Scaling teams should be able to expand it.


---

# 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:

```
GET https://myros.gitbook.io/bp/product-scope/premium.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.