Security principles

betool is designed for regulated environments. Security is not a layer bolted on after the fact: it is the invariant that shapes every line of code, every migration, every module.

1. Strict multi-tenancy

Every organisation owns its own data, pipelines, secrets, files and LLM keys. Isolation is enforced:

• At the database level — every business table carries an indexed org_id column, and server-side queries always filter by the session organisation.
• At the filesystem level — each org has its own root under <data_root>/orgs/<org_id>/. No shared paths.
• At the cache level — per-org caches; no shared entry without an explicit is_shared = TRUE flag.
• At the secrets level — each org has its own vault, its own API keys, its own tokens. No global fallback.

2. Mandatory audit of cross-tenant access

Certain roles (typically platform-operator accounts on the vendor side) may need to access another organisation's content for support purposes. Such access is:

• Gated on an opt-in from the target organisation — revocable at any time from the admin panel.
• Logged on every access — dedicated audit table, scoped by target org, exposed to customers via a GET /api/admin/me/*-reads route.
• Denied if the audit write fails — no read without a trace.

See GDPR Audit.

3. Motivated refusal on destructive operations

Any operation that destroys or replaces another organisation's content (REPLACE-IN-PLACE of children, DELETE) is refused if the target org has not activated the read opt-in. Rationale: without visibility, the operator would be proposing a payload that could blindly overwrite existing content.

4. LLM model sovereignty

• Native BYOK — your OpenAI, Anthropic and Mistral keys are managed by your organisation. No cross-org leakage.
• Private models in Enterprise — Ollama, vLLM hosted on your own hardware or in your private cloud. Prompts and completions never leave your perimeter.
• No silent shared pool — if an org uses a shared model, that is an explicit decision with access control.

Engineering posture

Our standard is precision: maximum robustness, total observability, determinism, anti-hallucination, anti-regression, tests at every turn.

Concretely, at every architecture / code / prompt trade-off:

Mantra: "If someone finds a bug, it means we didn't have enough guardrails, not too many."

Further reading

• Strict multi-tenancy
• GDPR audit & access log
• Sovereign deployment