Site: self-hosted vs. evanto-hosted
AdminThe Site edition (up to 100 users, team features) can be run two ways: in your own environment (API self-hosted) or as a stack operated by evanto (Managed operation). The feature set is the same; what differs is operations and responsibilities.
Side by side
Section titled “Side by side”| Aspect | Self-hosted | evanto-hosted (Managed operation) |
|---|---|---|
| Operations | you (containers/updates/backup) | evanto; backups from tier M |
| Infrastructure | your environment | EU (R-KOM, Regensburg) |
| Qdrant/Presidio | you operate them | evanto, dedicated from tier L |
| evanto’s GDPR role | not a processor (except for Managed AI) | processor (DPA, Art. 28) |
| Updates/monitoring | in your hands | included |
| Model access | own key (BYO) or Managed AI | own key (BYO) or Managed AI |
| User limit | up to 100 | up to 100 |
When to choose what
Section titled “When to choose what”- Self-hosted if you want/need full control over the infrastructure and the operational expertise is available.
- Managed operation if you want EU hosting and the full feature set without running operations yourself — with a DPA for the outsourced processing.
In both cases you remain the controller under data protection law. → GDPR/DPA