Per-organization isolation
Each organization runs in a dedicated, isolated environment. Identities, data stores, and secrets are strictly separated. No organization can ever access another's data.
Security and trust
Security you can verify.
How Felesh isolates each organization, records every change, and handles current certifications. We state what we guarantee, not the machinery behind it. When something is not yet in place, we say so plainly.
Security posture
Continuity by default
Data is replicated and failover is automatic. A single failure will not disrupt your operation. We run Felesh itself on this same foundation.
Auditable, reversible change
Every change to a live system is recorded and reversible. Blueprints carry an immutable version history, so you always know what changed, when, and who changed it.
Full operational visibility
Every action an agent takes leaves a receipt: the reasoning, the action, the source, and the timestamp. Nothing happens in the system that you cannot trace.
Data handling
Your data remains yours. Each organization operates in a dedicated environment, with sensitive fields encrypted at rest. Before new data reaches the layer where agents reason, it passes an operator-review gate. Only verified information is admitted; unchecked inputs do not drive decisions. Every model call is mediated by Felesh and scoped to your requests. We do not use your data to train shared models, and it never crosses organization boundaries.
Certifications
We hold no third-party security certifications today. Rather than point to a badge, we demonstrate how the system works against a live environment: per-organization isolation, encryption at rest, and a receipt for every action. When formal certification is underway, we will update this page with specific dates.