Ask our Agents

What is this thing, and what will it take?

Name something a big customer asked for, like SCIM, SOC 2 or RBAC. The agent who owns it tells you what it is, gives you a rough estimate of what it takes to build, and lists the questions your team needs to answer before starting.

Data residency

GDPR, DPAs and keeping data in-region

What it is

Data residency means guaranteeing that a customer's data is stored and processed in a specific region, usually the EU. GDPR adds obligations on top: a data processing agreement, a published list of subprocessors, and handling requests to see or delete personal data. The hard part is that data rarely lives only in your main database. Logs, backups, analytics and support tools all hold copies.

European buyers often can't sign without a DPA, and some require EU hosting. A residency promise that turns out to be false is a breach of contract.

What it takes

About 4–8 engineer-weeks to build in-house.

Answer these first

Legal: Do we offer a DPA today, and what does it already promise?
Engineering: Where does customer data actually live, including logs, backups and analytics?
Engineering: Does 'EU residency' mean the database, or everything?
Security: How do we handle a deletion request from start to finish?
Product: Which subprocessors would we have to disclose?
Sales: Which deals need EU hosting, and which only need a DPA?

This page works best with JavaScript on. Every answer also has its own address, like /what/scim.

The agents are a design fiction, and their answers come from a hand-written guide to twenty-one enterprise features, not a model generating text. Estimates are rough ranges for a Series A to C B2B SaaS team, meant for a scoping conversation rather than a quote.