Identity
Authentication is selected per deployment.
Email and password, magic link, TOTP, Microsoft Entra ID OIDC, SCIM and actor-bound API keys are supported.
A reviewable technical model
Control starts with where the system lives.
YumaOS is single-tenant software deployed on customer-controlled infrastructure. Application records, agent history and uploaded files remain in that deployment, except where a configured connector needs data to do its job.
Inside the deployment
Your operating record
- Application and agent data in customer-controlled Postgres
- Agent memory isolated in its own protected database schema
- Documents on local volumes or the customer's R2, S3 or Azure Blob account
- Observability traces stored in the product database
Configured egress
Data leaves for a reason
Only services selected for the deployment receive relevant data:
Language model provider · Xero · Buffer · email or SMS provider · Slack or Teams · Microsoft Graph
Review every connectionAuthority
Authorisation covers people and agents.
Two roles map to 35 named permissions. Financial and consequential actions are admin-only. Agent writes fail closed without an actor and require write capability independently.
Secrets
Stored credentials are encrypted.
Integration secrets saved through the interface use AES-256-GCM with a deployment-held key. Production refuses to store them when that key is absent.
Egress
User-supplied URLs share one SSRF policy.
Webhooks, external OpenAPI specifications, MCP servers and competitor monitors reject private and link-local destinations through a shared policy.
Record
Writes remain attributable.
Each user and agent write records the actor, action, entity, summary and structured metadata in the audit log. Agent traces filter sensitive data at export.
Agent safety
Control is applied before consequence.
Consequential agent work enters a human approval queue. Customer, third-party and public actions stop and wait. Optional PII, injection and moderation guardrails can block, warn or filter, with violations audited.
Agent artefacts are schema-validated data rendered by trusted components.
Machine writes require explicit deployment opt-in.
Standing rules stay scoped to one action kind and connection.
Assurance boundary
Controls are not certifications.
The repository contains no SOC 2, ISO 27001, IRAP or GDPR certification artefact. It also has no dedicated subject-access workflow, data-retention policy or documented recovery objective.
Yuma IT's Supply Nation certification is a publisher credential. It is not a YumaOS security certification.
See implementation responsibilities