A useful no is part of discovery

Check the edges before the ambition.

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.

Do you want one dedicated environment for one organisation?

Yes

YumaOS is single-tenant. Every client receives a separate deployment.

Can you run a long-lived Docker Compose service?

Required

Scheduled work depends on one continuously running process. Serverless and scale-to-zero hosting are not supported.

Do your customers need to log in?

No

There is no customer portal. Customers are records and communication recipients, not product users.

Does the field team need a native or offline mobile app?

No

The product is responsive web only, with no native mobile app, offline mode or push path.

Should staff enter timesheets here?

No

There is no time capture. YumaOS imports hours from an existing tracker through a generic push or scheduled pull.

Is your accounting system Xero?

Yes

Xero is the only accounting connector. Invoices and payments are a read-only mirror.

Do admin and member cover your access model?

Required

There are exactly two roles and no custom role builder or per-record sharing.

Do you need a dispatch or scheduling board?

No

Purchase orders, inventory, field-service dispatch and a scheduling board are not present.

Depth limits worth discussing

Shipped does not mean unlimited.

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.

One scheduler process

Two ticking processes could double-deliver scheduled notifications.

Per-process rate limiting

A multi-instance deployment needs a shared limiter that is not present today.

No scale claim

No load or concurrency evidence supports a user or throughput figure.

Still looks aligned?

Bring the constraints to the first call.

Describe the operating problem, required integrations and infrastructure preference. Yuma IT can test the fit before scoping implementation.

Start a fit conversation