Operate

Service limits

Check supported capabilities, startup windows, and execution limits.

Supported runners

Sprintbox currently documents managed Linux GitHub Actions runners. Supported labels must also be enabled in the service configuration. A label's presence in source code does not mean capacity has been enabled for every workspace.

Duration and concurrency

The current managed service allows up to 20 minutes for startup. Once the underlying runner starts, its 90-minute limit includes preparing and running your job. A separate 95-minute allocation limit also includes queueing. The earlier applicable limit ends the run, so these values do not guarantee 90 minutes of job execution. Set an appropriate timeout-minutes in your workflow and contact support before relying on long-running jobs.

Concurrency is limited by your workspace and by available runner capacity. Large bursts can wait. GitHub workflow scheduling and API limits also apply; contact Sprintbox before planning a major concurrency increase.

Service scope

The current service does not offer Sprintbox-managed cache or a persistent runner filesystem. Private networking, SSH debugging, and special placement policies are not included in the documented service.

Use GitHub's controls for repository access, workflow permissions, environment approvals, and secrets. Only install the app on repositories you intend Sprintbox to run, and review workflow changes that execute code with access to sensitive data.