Capability matrix
What's real, on the record.
Every capability we talk about publicly is listed here with an explicit status and its evidence. A finished ticket doesn't make something available — shipped artifacts, passing tests, and an operating surface do. This same registry gates our plans and enterprise pages at build time.
Implemented, tested, and generally supported today.
An implemented path for selected users — external deployment or operational evidence is still incomplete.
A roadmap commitment. No supported implementation in the current build.
Delivered by people under an explicit agreement, not an in-product control.
Community loop
Local autonomous loop (plan → code → test → build → verify → ship → monitor)
The full state machine runs on your own machine: fresh-context phases, durable checkpoints, bounded retries, cancellation and resume.
Evidence: Aion v0.2.0 — aion/loop/, tests/test_orchestrator.py
Human merge & deploy gates + local cycle trail
Merge and deploy default to a human decision; every phase transition is recorded in a local, inspectable cycle trail.
Evidence: Aion v0.2.0 — orchestrator gate tests
The local trail is plain files on your disk — auditable, but not the signed evidence envelope planned for the enterprise pilot.
Bundled integrations, skills, local dashboard, bring-your-own-brain
All bundled integrations and skills, the loopback-only local dashboard, and your choice of reasoning model stay free in Community.
Evidence: Aion v0.2.0 — aion/integrations/, aion/skills.py, aion/ui/
Service connections use the CLI logins and environment you already have; managed key storage in the OS keychain covers AI providers.
Registered repositories & explicit automation consent
Aion only works inside repositories you explicitly register, and automation levels are opt-in per repository.
Evidence: Aion v0.2.0 — workspace registration flow
Platforms
Standalone CLI — macOS & Linux (arm64, x86-64)
The aion CLI supports macOS and Linux on arm64 and x86-64. There is no Microsoft desktop-OS support.
Evidence: Aion v0.2.0 · builds publish to github.com/trimdev/aion-cli/releases
Desktop app — macOS (Apple silicon)
A macOS arm64 desktop app exists for selected users.
Evidence: Aion desktop 0.2.0 — no public download artifact is published yet; the CLI is the supported install today.
Models & providers
Claude (default), Codex, custom providers
Claude is the default reasoning engine; Codex is supported; custom providers can be configured. Capabilities differ by provider.
Evidence: Aion v0.2.0 — provider abstraction
Integrations & auth
GitHub.com through your own login
Branches, commits and pull requests through the gh login and credentials you already hold — Aion never brings its own standing access.
Evidence: Aion v0.2.0 — GitHub integration tests
GitHub Enterprise via customer-installed GitHub App
App-only authentication against GitHub Enterprise, installed and owned by the customer.
Evidence: Roadmap only — application DEVA-161
Finding intake
SARIF 2.1.0 / CodeQL finding intake
Canonical intake for approved scanner findings with eligibility checks and a tracked remediation lifecycle.
Evidence: Roadmap only — application DEVA-163
Governed execution
Signed bounded task contract
One human-authorized, immutable authorization envelope per task — scope, repository, commit, policy and permitted outputs fixed up front.
Evidence: Roadmap only — application DEVA-157
Customer-controlled disposable runner
Execution inside a disposable, isolated runner operated in the customer environment, with controlled egress and destruction proof.
Evidence: Roadmap only — application DEVA-158 / DEVA-159
Current local execution and the cloud command prefix are Community behavior, not this runner.
Fail-closed enterprise execution profile
Missing or invalid authorization, policy, runner, commit binding, model or evidence sink stops work before it starts — with a machine-readable denial.
Evidence: Roadmap only — application DEVA-156
Exact-SHA CI & scanner verification
Tests, required checks and the scanner re-run are bound to the exact head commit — not "latest", not a branch name.
Evidence: Roadmap only — application DEVA-162
PR-only remediation output
The enterprise pilot terminates at a draft pull request plus evidence. It has no merge or deploy capability — there is no setting to enable one.
Evidence: Roadmap only — application DEVA-164
Evidence
Signed, commit-bound evidence envelope
Independently verifiable evidence binding the finding, policy, runner image, commits, CI and scanner results, and the human decision.
Evidence: Roadmap only — application DEVA-160
Distinct from the existing Team event feed: that is a server-side hash chain, not source-signed evidence.
Team service
Hash-chained Team event feed & export
The existing Team service records org events in a tamper-evident server-side hash chain with CSV/JSONL export and offline chain verification.
Evidence: Live on this site — /team/audit, /api/org/events
Events are hash-chained by the server, not signed at the source. This is the current Team service, not the planned enterprise evidence envelope.
Agent → Team dashboard sync (outbox upload)
Opt-in per workspace, the agent uploads cycle events to the org dashboard through an outbox.
Evidence: Application preview — aion/sync/, tests/test_team_sync.py; general operational evidence incomplete.
Signed org policies & gate rules
An org publishes a signed, tighten-only policy bundle; agents verify and record the governing version at cycle start.
Evidence: Application preview — aion/policy.py; external publisher/rotation not yet proven as a generally supported service.
Shared org skill library
Skills pushed and pulled through the org registry; policy-pinned skills auto-install at loop start.
Evidence: Application preview — aion/sync/skills_sync.py; depends on the org registry service.
Domain-capture auto-join (Team sign-in)
An org admin claims a company e-mail domain; verified sign-ins on that domain auto-join the org, seat pool permitting.
Evidence: Live on this site — /team settings
A sign-in convenience — not IdP-managed enterprise identity. Full enterprise identity is a separate planned capability.
Data protection
Local secret-shape scrubbing
Phase output is scrubbed for common secret shapes (tokens, keys, JWTs) before it is stored or served locally.
Evidence: Aion v0.2.0 — output scrubbing tests
A Community convenience — not the enterprise DLP boundary below.
Enterprise DLP & context minimization
Policy-driven data minimization and named, controlled output channels for everything that leaves the runner.
Evidence: Roadmap only — application DEVA-165 / DEVA-166
Identity & access
IdP single sign-on, provisioning, enterprise RBAC & dual control
Full enterprise identity: IdP-managed sign-in and user provisioning, role-based access, and dual-control approvals.
Evidence: Roadmap only — application DEVA-168 (post-pilot)
Exports & adapters
ServiceNow & security-tooling export adapters
Pushing remediation records and evidence into enterprise ticketing and security monitoring tools.
Evidence: Roadmap only — application DEVA-169 (post-pilot)
Secret-broker integration
Short-lived credentials leased from the customer's secret broker instead of stored secrets.
Evidence: Roadmap only — application DEVA-169 (post-pilot)
Deployment
Customer-operated data plane & signed updates
The coordinator and runner backend run in the customer environment with signed, pinned artifacts and no standing vendor access.
Evidence: Roadmap only — application DEVA-167
The Docker packaging of this website is the existing Team service, not this data plane.
Disconnected (offline) deployment & compliance certifications
A generally available disconnected package and formal compliance certifications. Neither is offered today, and no certification is claimed.
Evidence: Roadmap only — no supported package or certification exists
Support
Priority / SLA support & operational assurance
Response-time commitments and operational assurance exist only under an explicit signed agreement — the product implies no active SLA.
Evidence: Contractual delivery only — per executed customer agreement
Statuses advance only with code, automated tests, and real deployment or operation evidence, per the application product contract. Questions about a specific row? Ask us — or see how the enterprise controls compose on the remediation page.