Runtime schedule
Providers decide when Common Compute can run.
Security
Security and verification built into every job.
Provider controls, execution verification, and runtime limits are built into the platform from the start.
Provider safety
Providers control the runtime.
CPU usage
Explicit caps keep the Mac responsive.
Memory usage
Providers control how much memory the app may use.
Network usage
Execution stays inside approved limits.
Tasks run only inside approved execution environments.
Customer safety
Jobs include verification checks and fallback routing.
Verification checks
Results are validated before completion.
Retry routing
Failed work can move to another provider.
Re-execution fallback
Work can be rerun if verification fails.
Completion tracking
Customers can see what finished and when.
Platform safety
Common Compute prevents unauthorized workloads, persistent background execution outside limits, and access to personal files.
Approved workloads only
Execution is limited to expected job types.
No persistent background execution outside limits
The app stops when the provider says it should stop.
No access to personal files
The platform does not inspect user documents.