Current

Running your own production

What the Doxa codebase includes, what it leaves out, and where to run docs on Doxa today

Doxa is a hosted service

Doxa runs documentation sites, the dashboard, the REST API, and the MCP server as one hosted service. You do not install or operate those parts yourself. You sign in, connect a GitHub repository, and Doxa generates, hosts, and publishes your docs site at <slug>.doxa.page or on a custom domain.

Self-hosting is not a supported public path. The Doxa codebase does not give you a production setup that you can run on your own infrastructure.

What the code does not include

The public code is not a complete deployment kit. It does not include:

Cloud account identifiers, resource IDs, or environment-specific settings.
Infrastructure state, variable files, or backend configuration.
Deployment pipelines, secrets, or operator runbooks.

Doxa operates its own production environment separately from the code. Those operational details are not part of the public documentation, and you do not need them to publish a docs site.

What you can do instead

Goal	Where to go
Generate and publish a docs site	Read the Doxa Platform Overview and How It Works.
Serve docs on your own domain	Attach a domain from the dashboard. See Custom Domains.
Let an AI agent manage your docs	Connect a client with Connect an AI Agent with MCP.
Call Doxa from your own tools	Use the REST API with a signed-in account.