> For the complete documentation index, see [llms.txt](https://docs.odyssey.stream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.odyssey.stream/faq/concurrent-user-limits.md).

# Concurrent user limits

Odyssey is built for dynamic scaling of Unreal pixel streaming sessions, where **1000+ concurrent users** could join your session in an instant.

## Expecting more than 1000+ CCU? 

If you have an event or experience planned, from which you expect greater than one thousand concurrent users, please be in touch via [Discord](https://discord.com/channels/926957916089634836/1093581069116244071).

## Space Limits & Sharding

Spaces, by default, are limited to 35 concurrent users.

If you want to increase this, you can enable the *Allow Sharding* space setting. This removes any limit on how many concurrent users your space can support.

### What is a *shard*?

A shard is like a sub-space for multiplayer projects. Shards have their own game-servers but share space settings (like configuration, permissions, and Dolby.io streams). 

Users on one shard will only be able to interact other users on the same shard, but will see any updates pushed to the space - like configuration updates.


---

# 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.odyssey.stream/faq/concurrent-user-limits.md?ask=<question>&goal=<endgoal>
```

`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.