Choose your path
Decide whether you want the hosted bot for fast evaluation or self-hosting for immediate infrastructure ownership.
Quickstart
Quickstart Sage in the path that matches your team.
Start with the hosted bot if you want the fastest evaluation, or move into the self-hosted setup flow if you already know you need infrastructure ownership.
Hosted path in plain language
Use the hosted path when your primary goal is to see Sage work inside Discord quickly. The website now routes you through the public product pages first, then into the repo only when deeper implementation detail is worth the extra complexity.
Self-hosted path in plain language
Use the self-hosted path when you already know your team wants:
- provider choice
- infrastructure control
- direct ownership of deployment and data handling
How it works
Use this page as the public entry point.
Read the matching setup guide
Use the website path pages and docs first so the deployment story is clear before you jump into repository detail.
Move into the repo only when needed
After the product fit is clear, use the repo guides for the deeper setup, architecture, and operational commands.
Next steps
Keep the next click intentional.
Discord AI bot guide
Start with the hosted bot path if you want the shortest route into evaluation.
Open hosted guideSelf-hosted Discord AI guide
Evaluate the self-hosted runtime story and deployment expectations.
Open self-hosted guideFull getting started guide
Continue into the full repository guide when you are ready for concrete installation and operations commands.
Open repo guide FAQ
Frequently asked questions
Should I start with hosted or self-hosted Sage?
Start with hosted Sage when you want the fastest evaluation. Choose self-hosting when infrastructure ownership and provider control matter from day one.
Does quickstart replace the repo docs?
No. Quickstart is the public first layer. The repository docs still hold the deeper step-by-step implementation details.
Is the hosted path a dead end?
No. The site is now structured so hosted evaluation and self-hosted adoption are part of one product journey rather than separate stories.