Stack & ethics
We are not trying to sound ethical. We are trying to make fewer compromises.
Odeva is booking software for European operators. That means the infrastructure choices matter: where data is processed, who can export it, which vendors sit between you and your guests, and whether the system can be understood without a compliance theatre production.
The short version: we prefer European infrastructure, open standards, privacy-preserving analytics, and boring data portability. We do not believe a booking system should quietly turn into ad-tech, a black-box dependency, or a hostage situation for your guest data.
That also affects integrations. We do not add a partner simply because there is demand or because a logo looks useful on a page. The question is whether the integration gives operators more control, whether the API is open enough to maintain responsibly, and whether the other company has incentives that align with the people using Odeva.
Some tools will be optional choices for operators rather than things Odeva is built on. Payment providers are a good example: customers should be able to use the route that fits their business, without us pretending the processor is part of our ethical foundation.
This is not a finished purity claim. The public website still uses Cloudflare for parts of hosting, security, and Turnstile. Google sign-in exists as a convenience layer. Pretending otherwise would be worse than saying nothing.
The direction is clear, though. Core booking workloads are being consolidated on European infrastructure, with Hetzner as the main hosting path. Codeberg, sovereign OIDC, EU edge providers, carbon measurement, and eventually open-source booking tools are all part of the work ahead.
We publish this because trust should not depend on vague words like secure, green, or GDPR-compliant. Operators should be able to see the tradeoffs and decide whether the direction matches their own obligations.
Current state
Last updated
- Booking core
- Moving toward Hetzner-hosted European infrastructure.
- Website
- Still uses Cloudflare components while hosting and security paths are evaluated.
- Integrations
- Chosen for operator control, open APIs, maintainability, and aligned incentives.
- Identity
- Google sign-in exists today. Sovereign OIDC is the target.
- Analytics
- Cookieless analytics. No ad-tech pixels by default.
- Data
- Exportability is a product requirement, not an enterprise add-on.
This page will change.
As dependencies move, this page should become shorter, not louder. The goal is not to collect badges. The goal is to remove things we need to explain.