8 articles tagged security.
Decouple the storefront from Odoo and you get a faster, safer, upgrade-proof shop. DragonflyDB caching, island architecture, GitHub version control, PR previews, VPN-isolated ERP, PWA mobile UX — everything we ship on every headless e-commerce project.
Making a human prove humanity is a UX tax, and the bots pay it more reliably than your customers do. The invisible gate on every form on this site: a honeypot field, a minimum fill time, and a fake success that teaches the bot nothing — three server-side checks, no third-party script.
Every image we deploy is built by CI, signed by cosign and checked by Kyverno at admission. Why we run the policy in audit mode first, and the PR-preview exception that makes it survivable.
Your storefront is public; your ERP doesn't have to be. WireGuard tunnels, private ingress, and the network layout that keeps Odoo reachable by the API gateway — and nobody else.
Hundreds of images, charts and npm packages age every week across our clusters. Renovate turns that into reviewed pull requests, and CI gates plus a minimum release age turn most of those into merges nobody has to click.
Secrets in .env files end up in repos; sealed secrets end up unrotatable. The Infisical → External Secrets Operator → pod pipeline that keeps credentials out of both git and CI logs.
Most Odoo installs run with everyone as admin until the first incident. How we design permission groups that mirror the org chart, record rules that hold up under audit, and logging that answers who changed what — before anyone has to ask.
Malicious package versions are usually caught within days. pnpm's minimumReleaseAge makes you structurally immune to the window where they do damage.