Skip to content
CIQRA
All postsEngineering

Security as a feature, not a checkbox

The CIQRA teamJul 1, 20264 min read

On a platform that hosts many stores, security isn't a feature you add — it's the foundation everything else stands on. If isolation fails, nothing else matters.

Enforce, don't hope

CIQRA scopes every tenant table with PostgreSQL row-level security, keyed to the resolved tenant. The database refuses to return another store's rows, even if application code slips.

Prove it continuously

A cross-tenant leak-test suite runs on every change and blocks any merge that could break isolation. We treat "your data can't reach another store" as something to verify, not assume.

Trust you can point to

EU data residency, field-level encryption and a published subprocessor list round it out. Security shouldn't be a paid tier — it should be the default. See Security.

Start building on CIQRA

Spin up a store in minutes. Bring your own gateway or turn on CIQRA Pay — your data stays in the EU.