On-premise AI for institutions in Oman, scoped to the workload and deployed at the customer's site.
Selected open models can be evaluated, an air-gapped option is available, and Arabic and English requirements are documented before implementation.
These are workload categories, not customer references. No customer identities are published.
Three boundaries documented before implementation.
Customer-site deployment.
The location, network routes, storage, identity and administrative boundary are reviewed with the institution and recorded in the delivery scope.
Arabic and English evaluation.
Language behaviour is tested on representative, approved material before the model and acceptance criteria are confirmed.
Written delivery terms.
Commercial terms are written into the quotation and deployment contract. Optional maintenance and update support are scoped separately.
A clear data boundary begins with a written scope.
Arabic and English requirements are reviewed as part of discovery.
Five planning layers. One written scope.
Three starting points. Every scope confirmed by quotation.
- ArchitectureSingle appliance
- ScopeDepartment-level starting point
- ModelSelected after workload testing
- CapacityConfirmed from measured demand
- DeliveryWritten scope and acceptance criteria
- ArchitectureMulti-node deployment
- ScopeSeveral teams or shared workloads
- ModelsSelected after workload testing
- CapacityConfirmed from concurrency tests
- DeliveryWritten scope and acceptance criteria
- ArchitectureRack-scale GPU infrastructure
- ScopeInstitution-wide workloads
- ModelsSelected after workload testing
- FacilityReviewed before architecture
- DeliveryWritten scope and acceptance criteria
Full specification, fit and installation detail for each: Hosn Kernel, Hosn Tower, Hosn Rack, or the three compared side by side. Use the TCO planning guide to define a comparable cost boundary.
Sovereign AI Readiness Assessment
The assessment documents the workload, users, corpus, data boundary, integrations, facility constraints and acceptance method. Its output is a written scope that the institution's technical and procurement teams can review before a quotation is prepared.
What institutional teams can ask Hosn.
Longer form on each of these workloads, and on archives, correspondence and records, on the use cases page and in the field notes cluster.
Institutions whose duty of care does not end at the firewall.
Public institutions
Regulated enterprises
Healthcare, research and professional services
Hosted AI or on-premise AI?
Provider-managed infrastructure.
A network-connected service can simplify infrastructure management. Its data boundary, administration, logs and available models depend on the provider's documented terms.
Customer-controlled infrastructure.
Hosn is deployed at the customer's site. Network isolation, local roles, logging and model selection are defined during discovery and recorded in the delivery scope.
The right boundary depends on the workload, the institution's policy and the delivery requirements. Hosn documents the selected boundary before implementation.
What institutions ask before the first meeting.
What is Hosn?
Hosn provides scope-driven on-premise AI planning and deployment for institutions in Oman. The model, infrastructure, integrations and acceptance criteria are confirmed through discovery.
Does Hosn require an internet connection?
An air-gapped deployment option can be scoped. The final network boundary, required routes and update procedure are documented for the delivery.
How is Hosn different from hosted AI?
Hosted AI runs in provider-managed infrastructure. Hosn is deployed at the customer's site, and its network and administrative boundary are documented for the delivery.
What does Hosn cost?
Pricing is by quotation because hardware, integration, deployment boundaries and support are scoped to the institution. The public site does not publish fixed prices.
Which AI models does Hosn run?
Selected open model families, including Gemma and Qwen, can be evaluated. The exact variant, runtime and context setting are confirmed after workload testing.
Does Hosn handle Arabic well?
Arabic and English requirements are tested against representative, approved material. The model and language acceptance criteria are confirmed before implementation.
How long does deployment take?
The deployment schedule depends on procurement, hardware delivery, site readiness, integration scope and acceptance testing. A delivery plan is included with the quotation.
What defines the software and model rights?
Software rights, upstream model terms, support and update responsibilities are stated in the written quotation and contract. No right is inferred from a public page.
Who is Hosn built for?
Hosn is intended for institutions in Oman that are evaluating an on-premise AI workload and need documented data, integration and acceptance boundaries.
Who builds and supports Hosn?
Hosn operates from Muscat, Oman. Public enquiries are handled through info@hosn.om and +968 9889 9100.