Aether Actions
The repository execution plane.
It handles GitHub access, compatibility, authorization, hosted execution, billing boundaries, and delivery of results.
Aether Actions · Production
Select a connected GitHub repository. Aether resolves its default-branch head to an exact commit, shows the maximum UVT cost, and runs authorized checks on Aether infrastructure. Results return as an integrity-checked Aether report and a GitHub Check.
commit c694c88The product relationship
One hosted execution layer, one locked security operation, and one result bound to the commit Aether resolved.
The repository execution plane.
It handles GitHub access, compatibility, authorization, hosted execution, billing boundaries, and delivery of results.
A security check that runs on Actions.
Its assurance profile fixes the routes, commands, environment, verdict rules, and runner class outside the repository being tested.
Local software analysis. It is not the hosted check and does not produce the same hosted evidence.
Human-run, scoped, and scheduled. It is not an automated UVT product.
From commit to result
Compatibility comes before cost. Cost comes before authorization. Execution starts only after both are clear.
Choose a connected repository. Aether resolves its default-branch head to one exact commit.
Aether checks support before quoting. This costs 0 UVT.
See the estimated price and the hard maximum before anything runs.
Execution and UVT reservation begin only after explicit authorization.
Get the integrity-checked report and GitHub Check for that exact commit.
In a manual browser run, a changed assurance profile or a newly required maximum above the approved ceiling is refused and sent back for a fresh quote.
Predator Security
The production profile replays registered security routes against one exact commit, with the operation controlled outside the repository under test.
aethercloud/[email protected]The repository cannot choose the verifier image, commands, route catalog, verdict reducer, or price—and repository code cannot write its own successful verdict.
The registered routes completed against the identified commit. It does not claim the repository is vulnerability-free, and it does not apply to later commits.
UVT billing and authorization
Repository access and spend authorization are separate decisions. The quote makes the boundary visible before Aether reserves or executes anything.
Current production example: a 300-second estimate with a 900-second execution ceiling. No account balance is shown.
Human-readable outcomes
Infrastructure trouble is not labeled as a vulnerability, and a clean run is scoped to the registered routes and exact commit.
Registered routes completed without a finding for this exact commit.
Predator produced a security result about the code.
One or more routes could not complete. This is not presented as a code vulnerability.
Nothing executed and nothing was verified.
The immutable receipt remains the historical record; the current interface is a human-readable projection of that record, not a rewrite of it.
Repository coverage
Aether checks repository coverage before presenting a Predator quote. When you authorize, it validates the resolved commit before reserving UVT.
An approved profile covers this repository.
Run action availableNo approved profile covers this repository yet.
Request an assurance profile · 0 UVTThe repository cannot be verified by a current Predator profile.
Request an assurance profile · 0 UVTThe profile exists, but hosted capacity or another dependency is unavailable.
Follow the in-product recovery step · 0 UVTProduction coverage currently consists of aethercloud/[email protected]. Customer assurance profiles are Aether-authored, private preview, and not self-service. No turnaround time is promised.
Hosted Build & Test is separate. It runs a repository’s configured checks through Actions and does not depend on Predator profile coverage where the production deployment has enabled that repository.
Product status
Production, preview, unsupported, and in-development capabilities are kept distinct so you can plan against what actually exists.
| Capability | Status | Detail |
|---|---|---|
| Aether Actions hosted execution | Production | Quote, authorization, and exact-commit execution on Aether infrastructure for repositories enabled in the production deployment. |
| AetherCloud Core Predator profile | Production | aethercloud/[email protected] — 5 routes, 54 checks, on the AetherCloud backend surface. |
| Approved customer assurance profiles | Private preview | Profiles are Aether-authored per repository. There is no self-serve path and no committed turnaround time. |
| Predator scanning for repositories without a profile | Unsupported | The current verifier is AetherCloud-specific. A repository with no approved profile is refused before any UVT is reserved. |
| Hosted Build & Test | Production | Runs a repository's configured checks independently of Predator profiles. Repository availability remains deployment-controlled. |
| Pull-request and push automation | Production | Off until the owner saves Actions settings with an explicit maximum UVT per run. Connecting GitHub never authorizes spend, and repository availability remains deployment-controlled. |
| Public certificate share and verification | Production | Eligible verified runs can issue, publish, verify, and revoke a signed certificate. Public verification is currently a safe JSON response rather than a branded page. |
| Aether Code remediation handoff | In development | A safe intake link exists, but the receiving side does not yet open the repository at the exact verified commit. |
Only if an approved Aether assurance profile covers it. The current verifier is specific to the AetherCloud backend surface, so most repositories answer "onboarding required" today. Aether checks before you are quoted, so finding out costs nothing and reserves nothing.
Technical detail
The product page stays focused. The full mechanics, qualification evidence, and operational limits live here.