Hosted Runners
Understand Kubiya-provided hosted runners for simplified deployment
Hosted Runners
Hosted runners are fully-managed execution environments provided by Kubiya. They require no installation or maintenance and are automatically provisioned when you sign up for the platform.
What Are Hosted Runners?
Hosted runners are deployed and maintained by Kubiya in secure, isolated cloud environments. They provide:
- Zero-setup execution environments for agent tools
- Automatic scaling to meet demand
- Regular security and performance updates
- Simplified onboarding experience
A hosted runner is automatically created for every Kubiya customer during the onboarding process, allowing you to start using agents immediately.
Provisioning Process
When you sign up for Kubiya, a hosted runner is automatically provisioned for your account. The process involves:
- Initialization: The system begins creating your runner environment
- Configuration: Runner resources are allocated and configured for your account
- Connection: The runner establishes a secure connection to the Kubiya platform
- Verification: System checks ensure the runner is functioning properly
- Activation: The runner is made available for your agents to use
During this process, you'll receive status notifications in the platform:
- Provisioning in progress: Your runner is being set up
- Provisioning successful: Your runner is ready to use
- Provisioning failed: There was an issue setting up your runner (with troubleshooting steps)
Capabilities and Limitations
Hosted runners provide a convenient starting point but have some limitations compared to local runners:
Capabilities
- Execute standard agent tools
- Access public internet resources
- Integrate with publicly accessible APIs
- Run containerized workloads
Limitations
- Cannot directly access your internal network resources
- Limited ability to customize the execution environment
- Fixed resource allocations
- No ability to apply custom security policies
Use Cases
Hosted runners are ideal for:
- Evaluation and testing: Quickly try Kubiya without infrastructure setup
- Simple integrations: Workflows that only need publicly accessible services
- Development environments: Non-production deployments for building and testing agents
- Public cloud management: Managing resources in public cloud providers via their APIs
Security Considerations
Hosted runners operate with the following security measures:
- Isolated execution environments for each customer
- Tool execution in ephemeral containers
- Encryption for data in transit and at rest
- Regular security patching and updates
- Limited permission scope
While hosted runners are secure, they are not suitable for sensitive workloads that require operation within your private network or have strict data residency requirements.
Runner Status
You can check the status of your hosted runner in the Kubiya platform:
- Navigate to the Runners section
- Look for the "Hosted Runner" entry
- Check its current status (Connected, Disconnected, or Error)
If you encounter any issues with your hosted runner, contact Kubiya support for assistance.
When to Switch to Local Runners
Consider moving to local runners when:
- You need to access resources in your private network
- You have strict security or compliance requirements
- You're deploying to production environments
- You need greater control over resource allocation and scaling
- You're implementing advanced security policies and controls
Next Steps
- Learn about local runners for advanced deployment options
- Configure your first agent to use the hosted runner
- Understand runner architecture and how it fits into the Kubiya platform