Skip to content
These docs describe Tradr v0.17.0. Running an older release? Check the release notes for what changed.

Hosted vs self-hosted: what's different

Tradr is the same product whether you use the managed app or run your own instance. A small number of flows diverge, and this page is the map for them.

Rather than duplicating pages, the docs mark divergent flows inline with one of two callouts. Both are thin wrappers over Starlight’s <Aside>:

Use <HostedOnly> / <SelfHosted> from src/components/ in any .mdx page where a step only applies to one deployment.

Area Hosted (app.tradr.cloud) Self-hosted
Backups Managed, automatic You run and restore your own
LLM access Wallet credits (platform keys) Bring your own key (BYOK)
Billing Stripe wallet None
Feature gating On (plan limits apply) Off by default
Migrations Run for you Auto-run on API startup
  • Backups. A self-run instance owns its database, so you run and restore your own backups — see Back up and restore. The managed app runs them for you.
  • LLM access and the advisor. The AI advisor ships off on every instance, hosted or self-hosted — DISABLE_ADVISOR defaults to on. Turn it on for your own instance with DISABLE_ADVISOR=false. Once it is on, a self-run instance is bring-your-own-key — each user adds a provider key under Settings → Advisor — while the managed app meters platform keys against wallet credits. See Configure email, Stripe, and LLM keys for setup and the local-model option.
  • Billing. Wallet purchases and the Pro subscription stay off until configured: with the Stripe keys unset a self-run instance has no purchase UI at all. See Configure email, Stripe, and LLM keys.
  • Feature gating. Plan limits are off by default (FEATURE_GATING), so a self-run instance is unrestricted unless you turn gating on.
  • Migrations. A self-run instance applies schema migrations automatically when the api container starts; the managed app runs them for you. See Upgrade an instance.