You pick a tool, but you also pick what runs behind it. Rarely explained. Here's our stack, in plain words.

A business tool isn't just the screen your team uses. It's what sits behind it: where the data lives, who watches it, how it's backed up, who can see what. Most of the time, that part stays invisible. It only becomes visible when it fails. At Yumea, we'd rather show it before.

Your data lives apart

Each client has their own database. Not a shared database with a filter "show only client X's data". A fully separate database. Why it changes everything: if a flaw touches one client, it can't spread to others. If a backup is corrupted, it affects a single scope. If an employee moves projects, they lose access to data outside their current scope. It's more costly to run, requires infrastructure discipline. We decided long ago: discipline beats risk.

Backed up, and actually tested

Your data is backed up nightly, encrypted, stored off the production server. That's market standard. What's less standard: we restore for real, regularly. A backup never restored is a hypothesis, not a backup. That's written black-and-white in our internal doctrine. We test restores on a defined schedule, document them, and if one fails, we fix it before the next backup.

Monitored

Every day, a security scan runs across the entire estate. It raises anomalies (overdue updates, services that stopped, unusual requests) before you see them. Concrete example: last September, a vulnerability hit a component we used across several sites. We patched the whole estate in under 24 hours, with no rollback, no visible disruption to clients. That kind of incident is handled by preparation, not panic.

Hosted in Europe

Your data is hosted in Europe. Not a marketing argument: a choice with consequences: European jurisdiction for legal requests, clear protection rules, no transfer to countries whose rules clash with ours. We refuse cheaper hosts whose jurisdiction would expose you to data requests you couldn't challenge.

Why we tell you this

Because rigor doesn't show while it's working. The day it fails, it's too late to ask for it. You buy a tool; you also buy how we run it. We'd rather you know in advance what you're buying.

What we've seen on the ground

The weekend of the September vulnerability, the team patched around twenty systems while keeping a rollback procedure ready at each step. No client had to call us: they learned about the flaw on Monday from the press, not from a glitch in their tool.

FAQ

Included in the price, or extra? Included. It's the price of a Yumea tool in production, not an option.

Can I see your procedures? Yes, on pre-contract request. We share an anonymised extract of the production doctrine.

Want to know precisely what runs behind your future tool? We'll show you. Before, not after. Let's talk →