Ask the question before the pitch.

YumaOS is a single-tenant operations platform for one contracting or engineering business. It connects delivery, commercial work, knowledge, communications and controlled AI agents in one dedicated deployment.

It is designed for operations managers, commercial leads, IT administrators, team members and integrators who need a shared operating picture without giving every role the same access.

Each client receives one Docker Compose deployment on customer-controlled hardware or a private server. The codebase does not contain a hosted multi-tenant offering.

Application records and agent history live in the customer's Postgres, while documents use local storage or the customer's configured R2, S3 or Azure Blob account. Data leaves only through configured connectors.

Agents use 89 registered tools across the real product surface. They can read operational context and prepare writes under the same actor enforcement and audit path used by the application.

No. There is no send tool in the registry. Customer, third-party and public actions stop for human approval, while other consequential writes can enter a queued approval path.

Xero is the only accounting connector. YumaOS can export quotes and mirror invoices and payments, but it does not create or edit invoices and has no MYOB, QuickBooks, Sage or Reckon connector.

No. There is no customer portal, native or offline mobile app, or timesheet entry. Time is imported from an existing tracker through a generic push or scheduled pull path.

YumaOS has two roles, admin and member, mapped to 35 named permissions. It does not currently have a custom role builder or per-record sharing.

There is no published package price, subscription billing or product entitlement system. Scope and commercial terms are established for each per-client implementation after fit and discovery.

The client owns the infrastructure and connected service accounts. Yuma IT provides handover and ongoing support under the agreed engagement, with responsibilities made explicit during implementation.

No certification artefact for SOC 2, ISO 27001 or IRAP exists in the product repository. The security controls described on this site are real product controls, not certification claims.