Overview
A Service Policy is a control layer that defines which services are available to specific teams during instance creation. It acts as the gateway between services and user access, ensuring that only designated services are visible and deployable for a given team.
Key Functions of a Service Policy
Grants access to Services: If a service is included in a policy, then any team assigned to that policy can see and use it
Simplifies permissions: Rather than configuring service access per team or user, you attach teams to policies, and policies manage service visibility
Enables multi-tenant setups: You can define different sets of services for different customer types, environments, or product tiers
Team Assignment Rules
A team can belong to only one Service Policy at a time
Multiple teams can be assigned to the same policy (e.g., all enterprise customers could share a policy)
Why It Matters
Imagine you have:
A customer using hosted.ai for AI workloads, such as:
Stable Diffusion (image generation)
LLM inference with Hugging Face models
Ollama for lightweight, GPU-accelerated local LLMs
Fine-tuning or benchmarking custom models
Another customer using hosted.ai for traditional hosting, such as:
Deploying cPanel or Plesk servers
WordPress hosting
LAMP/LEMP stacks
You’d:
Create an “AI Services” policy and assign it to the first customer’s team
Create a “Web Hosting Services” policy for the second customer
Each team would only see relevant options, with no clutter or risk of misconfiguring incompatible services.
Relationship to Service Scenarios
Service Scenarios contain one or more Services
If a team has access to at least one service within a scenario (via a Service Policy), the entire scenario becomes visible to them during instance creation
There are no separate Scenario Policies since scenario visibility is fully determined by Service access via Service Policies.