Self-hosted resume builder

You can run Reactive Resume on your own infrastructure instead of using the hosted instance.

When self-hosting is a good fit

Self-hosting helps when you need control over the deployment, domain, database, storage, email delivery, authentication providers, and operational policy. The Docker guide is the main setup path for most deployments.

Start here:

• Self-hosting with Docker
• Self-hosting examples
• Single sign-on
• Migration guide

Core deployment pieces

A typical self-hosted deployment uses:

• Reactive Resume application container.
• PostgreSQL database.
• SMTP configuration for account emails, or console-logged emails in simple development setups.
• Optional S3-compatible storage for uploads.
• Optional SSO or custom OAuth configuration.

The Docker guide has the environment variable reference and a Compose example.

Feature considerations

Some features need extra configuration. Saved AI providers need server-side encryption configured, and the AI Agent workspace uses Redis. Self-hosted deployments can also expose API and MCP endpoints from their own domain.

For automation setup on a self-hosted instance, see Using the API and Using the MCP server.

<Tip> Replace hosted URLs such as <code>https://rxresu.me</code> with your own instance URL when following API, MCP, or sharing examples. </Tip>