Three ways to run it
Sovereign, hosted and hybrid are different splits of the same primitives across the boundary you control. Which one you choose depends on your regulatory requirements, existing infrastructure, and where you want your data to live.
Customer-controlled inference and execution boundaries.
How KSA and GCC enterprises decide
Banks, government agencies, and regulated enterprises choose a deployment model based on these criteria:
| Concern | Sovereign | Hosted | Hybrid |
|---|---|---|---|
| Data sovereignty | Data flows depend on the selected model, dependencies and support design. | Data lives in a hosted multi-tenant control plane. | Agree local execution and model location; hosted management may receive evidence. |
| NCA ECC / PDPL compliance | Map processing locations and controls to applicable requirements; validate the deployment. | Depends on whether the hosted region is acceptable under your interpretation. | Sensitive execution stays inside; management plane may be hosted in an approved region. |
| SAMA CSF (banks) | Confirm local inference and every data destination with the bank. | May not meet SAMA requirements for customer data handling. | Validate prompts, evidence, metadata and model routes individually. |
| Operational overhead | You run the control plane, database, and upgrades. | Vendor manages infrastructure and upgrades. | Shared: you run inference, vendor manages control plane. |
| Air-gapped / isolated networks | Requires a fully local design and disconnected acceptance testing. | Requires connectivity to the hosted control plane. | Requires connectivity to the hosted control plane. |
| Cost model | Annual licence, predictable. Your own infrastructure. | Usage-based or seat-based, depending on contract. | Licence for local execution, hosted control plane fee. |
| Where does the control plane run? | On infrastructure you control. | On AcTree’s hosted service in Riyadh (stc cloud). | Hosted control plane; execution on your hosts. |
| Where does inference happen? | A model you run locally, or a provider you choose. | The metered hosted model (prompts go to its provider), or a model you bring. | Your model, inside your network. |
| Where are conversations and evidence stored? | Your database. | AcTree’s database in Riyadh. | The hosted database; command output passes through the control plane. |
| What leaves our environment? | Nothing, unless you choose an external model or service. | Prompts, command output and attached documents: to the control plane and to the model provider. | Prompts, command output and evidence to the control plane; model traffic stays local. |
| Who can authorize changes? | Read-only by default. Your workspace administrators set host policy; commands may be allowed, denied or referred for human review. | The same: read-only by default; execution follows the configured host policy. | The same: read-only by default; execution follows the configured host policy. |
Sovereign — customer-hosted platform
A customer-hosted design places the control plane and selected components on infrastructure you control. Confirm the release, model endpoint, dependencies and data flows during technical acceptance.
Customer-hosted deployments use packaged deployment configuration. An offline deployment requires an accepted bundle, local model and disconnected installation tests.
Customer environment
Hosted — multi-tenant, operated by AcTree
In this model the control plane is hosted, serving every tenant from shared infrastructure rather than from your own. Faster to start, lower operational overhead, but data sovereignty depends on where the hosted region is and whether that meets your requirements.
Your platform
Hybrid — hosted control, local execution
A hybrid design combines a hosted control plane with local execution or inference. Agree which prompts, command output, evidence and metadata cross the boundary; local execution alone does not establish local processing.
Three ways to run it