Cloud
For permitted workloads that can use an agreed hosted environment.
AGREE DURING SCOPING
Data residency, identity, integrations and recovery.
DEPLOYMENT & CONTROL
The same operating idea.
Your data boundary.
Choose where records are processed, how systems connect and which actions require a person. Agree the boundary before connecting the first workflow.
On premises
For workflows that need local records, models or processing.
AGREE DURING SCOPING
Hardware, model resources, support access and updates.
Hybrid
For operations that keep selected sensing or processing on site while connecting permitted services.
AGREE DURING SCOPING
Sync boundaries, offline behaviour and ownership of each record.
Air-gapped
For a deployment scoped around local components and no external cloud dependency.
AGREE DURING SCOPING
Model and software transfer, local services and controlled maintenance.
THE CONTROL MODEL
Before the action,
resolve the authority.
Identity
Who is asking, and on behalf of which team?
Scope
Which records and locations can that person access?
Permission
Can they inspect, prepare, approve or execute this action?
Evidence
What instruction, approval and outcome should the record retain?
CONNECTIONS WITH A CLEAR JOB
Every integration
has a boundary.
| Connection | Records to agree | Actions to scope |
|---|---|---|
| Business systems | ERP, CRM, HR and finance records | Permitted reads, writes, reconciliation and recovery. |
| Documents | Approved SOPs, playbooks and supporting files | Access, versions, retrieval and retention. |
| Communication | Web, email and permitted messaging channels | Identity, drafts, approvals and delivery status. |
| Physical signals | Cameras, sensors and equipment events | Device compatibility, event quality and local controls. |
| Execution endpoints | Work orders and developing robot integrations | Allowed commands, local safety checks and completion feedback. |
This page describes deployment choices to scope. It does not assert a certification or universal integration compatibility.
ENGINEERED BY UBIQ / THE TEAM BEHIND DAFFYOS
If the work needs a device,
we can engineer it.
We don’t stop at software. Alongside DaffyOS, we engineer custom and special-purpose devices, configure cameras and camera bots, and take on drone-based projects.
Custom & special-purpose devices
When the workflow needs hardware built for a specific job, we engineer it around the task and the environment it works in.
Cameras & camera bots
We configure cameras and camera bots around what your operation needs to observe, inspect or capture, and how that evidence should enter the workflow.
Drone-based projects
Have a use case that needs a drone? Bring it to us. We take on drone-based engineering and integration projects, scoped around the job you need done.
FROM SOP TO A WORKING SCOPE
Start small.
Connect what comes next.
Agree the first useful outcome, then add workspaces and handoffs as the operating process grows.
Map
Choose the recurring process, the trigger and the exception it must handle.
Connect
Agree the source records, systems, data boundary and permissions.
Rehearse
Run representative cases, missing data, rejected approvals and recovery steps.
Operate
Confirm acceptance, monitor the work and agree the next useful connection.
START WITH ONE WORKFLOW
Bring the SOP.
Let’s map the first step.
The trigger, the people, the systems and the decisions that matter.