Website docs

Public docs for getting started with Sage without your first click going to GitHub.

Use these website docs for quickstart, self-hosting, FAQ, and security. Once the product fit is clear, jump into the full engineering and operations reference in the repo.

What changed in the docs strategy

The public website docs are now responsible for the first explanation layer. That means:

  • less GitHub blob-first navigation
  • better search landing pages
  • a clearer split between product docs and engineering reference
Next steps

Keep the next click intentional.

Start here

Quickstart

The shortest path into hosted evaluation or early self-hosted testing.

Open quickstart
Deployment

Self-hosting guide

Learn the runtime story, setup flow, and where the repo docs take over.

Open self-hosting guide
Common questions

FAQ

Read the high-signal answers before you go deeper into engineering details.

Open FAQ
Trust

Security and privacy

Review data handling, approvals, and operator controls.

Open security guide
Decision point

Start here for product fit, then move into the repo for engineering depth.

The website docs now absorb the first public click for setup and trust content.

FAQ

Frequently asked questions

Why are there website docs and repo docs?

The website docs are the public product surface for faster evaluation. The repo docs remain the detailed engineering and operations reference.

Where should non-technical users start?

Non-technical evaluators should start with quickstart and FAQ on the website before visiting the deeper engineering docs.

Where should technical teams go after this?

Once the product fit is clear, technical teams can continue into the repository documentation for architecture, configuration, and operations detail.