# Thermus pricing and hosting

Updated: 2026-10-16

Run it yourself for free, or use free Hosted early access.

|  | Self-hosted | Hosted early access |
| ----- | ----- | ----- |
| Price | $0 | $0. Free early access, no card and no automatic charges. |
| Who runs it | You. A downloadable file, self-hosted on your machine. | Thermus. Managed for you. |
| Access | The gateway on your machine | An isolated personal User workspace for a new eligible person |
| Get started | Join the download waitlist at https://thermus.ai. | Start subscription at https://app.thermus.ai/signup. Availability shown at signup. |

The server decides whether new Hosted activation is available. The Start subscription label leads to signup, without starting a paid plan. Existing users can sign in at https://app.thermus.ai/login. Download buttons still open the self-hosted email waitlist; they do not start a download.

## Who can activate Hosted access?

Any WorkOS identity with a verified email can qualify, using a personal or company email address. The current public sign-in option is Google through WorkOS. The person must be an adult and agree to the terms for business use, including authority to agree for an organization when applicable. Email verification does not verify age, employment, or that authority.

A new eligible person receives an isolated personal User workspace. Activation gives User access only, without Admin or Super Admin roles. This early-access offer does not provide teammate management, shared team policies, or customer audit-log access or export. Existing users with product access can continue to their workspace without creating another one. An incomplete or inconsistent activation needs support.

## What is needed to get started?

When signup is available, read the hosted notice, sign in, review the complete hosted terms and notice, and select the agreement checkbox before activating. Then choose an authorized workspace and return to the portal. Add `https://app.thermus.ai/mcp` as a remote MCP server in your native client, complete its authorization flow, and choose the actual workspace for that connection. Reauthorize the native client to change its workspace. Browser workspace selection is separate and does not change an existing MCP token's workspace.

See the [deployment guide](https://thermus.ai/guide/deployment.md) for the steps and platform boundaries. Self-hosted installation instructions, endpoint, and authentication depend on your deployment; obtain them from the Thermus team.

## Where does our data go?

With self-hosted Thermus, the gateway runs on your own machine or server. With Hosted, Thermus runs it for you. Read the hosted notice and terms presented at signup before activation. The marketing website's current legal pages describe the website and waitlist.

Ask the Thermus team through https://thermus.ai for details not supplied by those documents, including deployment-specific residency, retention, certifications, or an uptime SLA. The Cloudflare token-saving example in the prompt-injection guide is an example from another provider, not a measured Thermus benchmark or guaranteed saving.

## Related topics

- [Deployment prerequisites and rollout](https://thermus.ai/guide/deployment.md)
- [Request logs and access limits](https://thermus.ai/guide/audit-logs.md)