Do you want one dedicated environment for one organisation?
Yes
YumaOS is single-tenant. Every client receives a separate deployment.
A useful no is part of discovery
YumaOS is a strong fit when a business wants connected operations and controlled agents in a dedicated environment. It is not the right current product when a portal, native mobile, time capture or a non-Xero accounting path is essential.
Yes
YumaOS is single-tenant. Every client receives a separate deployment.
Required
Scheduled work depends on one continuously running process. Serverless and scale-to-zero hosting are not supported.
No
There is no customer portal. Customers are records and communication recipients, not product users.
No
The product is responsive web only, with no native mobile app, offline mode or push path.
No
There is no time capture. YumaOS imports hours from an existing tracker through a generic push or scheduled pull.
Yes
Xero is the only accounting connector. Invoices and payments are a read-only mirror.
Required
There are exactly two roles and no custom role builder or per-record sharing.
No
Purchase orders, inventory, field-service dispatch and a scheduling board are not present.
Depth limits worth discussing
Estimating supports time and materials, global search covers four core entity types, and semantic search needs an OpenAI platform key. Named time trackers require integration work rather than a ready-made connector.
Two ticking processes could double-deliver scheduled notifications.
A multi-instance deployment needs a shared limiter that is not present today.
No load or concurrency evidence supports a user or throughput figure.
Still looks aligned?
Describe the operating problem, required integrations and infrastructure preference. Yuma IT can test the fit before scoping implementation.
Start a fit conversation