Skip to content
Developer previewBack to Kernall
Browse documentation
DocumentationReference

Reference

Availability & roadmap

A map of the current preview and the features that still need implementation.

Implemented in the source

  • HTTP action evaluation with three verdicts.
  • Project bootstrap, hashed keys, and rotation.
  • Domain, data-category, and action-name rules.
  • Check logs and owner-resolved confirmations.
  • Check rate limits and idempotent retries.
  • A synchronous source-distributed Python client.

Incomplete experiences

The dashboard and confirmation page still use browser demo storage. They need the existing project, policy, key, log, and review APIs connected before becoming a reliable owner control surface.

These docs use the local API path. Complete hosted onboarding and authenticated external-agent access need verification for the intended deployment.

Planned capabilities

AreaStill to build
ExecutionDisposable environments, lifecycle controls, file/network enforcement, task-scoped credentials.
Desktop and CLISigned applications, packaged tools, distribution, updates, compatibility testing.
MCPServer, tools, authentication, setup, and enforcement gateway.
ObservatoryExecution traces, replay, evaluation tooling, and verifiable execution evidence.
Connected accountsGitHub and Drive authorization, selected-resource imports, approved exports.
Compute and modelsRuntime adapters, CPU/GPU controls, model endpoints, metering, budgets.
TeamsShared projects, roles, teammate review, and collaboration.

Release details

There is no committed release schedule, paid plan, service-level agreement, or production support matrix here. Planned items are not available features or delivery promises.

Each release should ship its setup steps, supported versions, permissions, migration guidance, and troubleshooting. These docs will grow alongside implemented behavior.

Help shape the next workflow

Tell us what you want to build: which agent, what operation needs control, who reviews it, and where it runs. Concrete workflows help define useful release scope.