Agents do the work.
You keep control.

Yes. Agents run under the same roles and permissions model your team uses, scoped to role and workspace. They see only what they're cleared for; sensitive records and tools stay out of reach by default.

Risky or irreversible actions — sending, paying, deleting, and writes to external systems — pause for human sign-off before they run. Approvals happen in-flow, where the work is, not in a separate console.

In the region you choose at signup: US West or EU West. Your workspace's data lives there, in your own database, and that choice can't silently change.

No. Your business data is never used to train models.

Yes. Your data lives in your own database and can be exported anytime, and the audit history is exportable too. The apps and business logic Opser generates are open source, so you can read, modify, or fork them.

Access follows the same roles and permissions model as everything else in your workspace — the people you clear for it. Every entry traces an action to the user, the agent, the input, and the outcome.

Yes, architecturally. Each workspace runs on its own dedicated database, every user's agent runs in its own sandboxed runtime spawned on demand, and both are pinned to the region you chose at signup. There is no shared database and no shared execution environment.

Only the context the acting user's role is cleared for, for the task at hand. Permission checks happen before the agent reads or writes anything, and none of it is used to train models.

Yes. Every workspace's database is backed up automatically, and because the data is yours you can also export it anytime for your own copies.