Deploy
Roll out software and model updates to every hardware platform in your fleet.
Poolboy manages the software releases that run on your fleet. Operators choose a release and its target devices, approve rollouts in stages, and track reports from individual devices. Teams can deliver application, model, and security updates without managing each device installation separately.
KEY FEATURES
- Signed release manifests for applications and models
- Deploy rollouts in waves, with fine-grained control over which devices receive each wave
- Custom test suites and operator approval workflows for each deployment
- Authenticated reports from individual devices
- Detailed device logs and metrics
Push a release to any hardware platform in the fleet
Poolboy is the control layer for software changes. Upload a release manifest, then select the devices that receive it.
Watch as the release propagates across the fleet, passing tests and sending health checks as GWOS runs the new update on the device's partition.
Test new releases in waves, starting with a canary group
Start your deployment with a small set of devices. Inspect their health and device reports, then approve the next deployment wave.
Operator gates give you control over your rollout expansion. If a release fails tests or causes issues, you can roll back the release on the affected devices.
View release reports and device logs to debug issues
Each device returns an authenticated report so operators can track progress and confirm the result.
Easily SSH into your hardware devices over the Poolnet mesh network to inspect logs and debug errors.
Use Cases
Procurement
Evaluate the release workflow against your approval process, target hardware, and network conditions. Review device status and recovery behavior as part of the same deployment exercise.
Scale
Start with a small test group, then expand to successive waves. Target devices deliberately and inspect the result before approving the next group.
Security
Signed release manifests identify the intended payload. Operator approval gates control rollout progression, and device reports provide a record of what landed.
Reliability
Inspect device health before releasing another wave. Stopping a rollout prevents further installs; GWOS handles local recovery when an operating system update fails.
Common questions
- How are releases defined?
- Poolboy manages software payloads using release manifests, which include application binaries, AI models, and operating system images.
- Can an operator stop a rollout?
- Operators can withhold approval for the next wave, or roll back a prior release.