Choose by data boundary
Start with the data and operating boundary, not a preferred infrastructure label. Identify which raw customer, document, transaction, screening, model, configuration, and audit data can leave the customer's environment.
Comparison
| Model | Processing location | Typical use | Customer responsibility |
|---|---|---|---|
| Cloud | UWAY-managed environment | Lightweight analytics, configuration, and approved workloads | Identity integration, data minimisation, policy ownership |
| Customer VPC | Customer-controlled cloud environment | Sensitive processing with customer network and key controls | Infrastructure, access, monitoring, and approved upgrades |
| Edge Agent | Customer VPC or on-premise | Local context resolution and controlled data movement | Runtime health, local secrets, logs, and capacity |
| Hybrid | Local sensitive processing plus approved cloud services | Configuration sync, analytics, and local decision context | Boundary definition and end-to-end operating model |
Architecture decision record
The deployment decision should record:
- Data classes and permitted flows.
- Processing and storage locations.
- Encryption and key ownership.
- Identity, role, and privileged access model.
- Logging, monitoring, retention, and deletion.
- Model, prompt, rule, and configuration update path.
- Incident, rollback, and support responsibilities.
- Evidence required for security and compliance review.
Edge Agent operating requirements
An Edge Agent deployment requires an owner for runtime health, secret rotation, configuration approval, upgrade windows, capacity, local logs, and incident response. Keeping data local does not remove operational responsibility.
Production readiness
- Approve the data flow and threat model.
- Validate network, identity, secret, and encryption controls.
- Test normal, degraded, disconnected, and recovery behaviour.
- Confirm configuration and software version evidence.
- Run representative workflow and jurisdiction tests.
- Agree support, incident, and change windows.
Private tenant configuration
Base URLs, credentials, network allowlists, customer-specific schemas, webhook secrets, and infrastructure parameters belong in the private implementation record, not in public documentation.