Hosted vs self-hosted
Chronicler is open core. Run the source-available core yourself, or use Chronicler hosted. This guide shows what each path gives you.
Both paths run the same core, so your world and your data have the same shape either way. The difference is who runs the infrastructure, and which extra features are available.
Self-host the core
You run it. You own the data end to end.
Chronicler hosted
We run it. You get hosted-only features.
Self-host the core
The Chronicler core is source-available. You can read the source, run it on your own infrastructure, and keep full control of your data.
- Run the core wherever you want.
- Own your data end to end.
- Follow the Self-hosting guide to deploy it.
Same world, either way
A world you build on the core imports into hosted, and back out again. You are never locked in.
Chronicler hosted
Chronicler hosted runs the core for you, always up to date and backed up. It also adds features that only the hosted version carries.
- Managed and current — no servers to run, and no upgrades to apply.
- Live collaboration — build together, in real time.
- Integrations — connect Discord and more.
- Asset library at scale — generous storage for portraits, maps, and scenes.
- Webhooks and automations — react to changes from your own tools.
- Priority support — talk to us when you need a hand.
At a glance
| Capability | Self-hosted core | Chronicler hosted |
|---|---|---|
| Worldbuilding, chronology, campaigns | Yes | Yes |
| Your own kinds, schemas, relationships | Yes | Yes |
| The full API | Yes | Yes |
| Own your data end to end | Yes | Import and export |
| Managed hosting and backups | You run it | Yes |
| Live collaboration | — | Yes |
| Integrations | — | Yes |
| Priority support | Community | Yes |
Start either way
Try the hosted version to get going fast, or self-host from day one. Your world moves between them, so the choice is not final.