Apps
Owner context, current stage, live availability, latest activity, and whether a draft or failure needs attention.
Fleet visibility
See the app that needs attention first.
Garden's current pilot gives an operations manager a customer-hosted, read-oriented console for the app fleet. It answers what exists, what coworkers use now, what is changing, and which owner must take the next action.
Operator surface: customer-hosted consoleMutation surface: owner workbenchUpdated: August 4, 2026
A shared inventory with operational states
The fleet is ordered around owner-readable stages rather than a raw infrastructure list. A live app may also have a newer private draft or a failed release, so “what is live?” and “what needs attention?” remain separate questions.
| Visible state | Meaning | Typical next action |
|---|---|---|
| Waiting | Garden knows the app, but it has not entered the managed release path. | Bring it into Garden or confirm that it should remain tracked only. |
| Unreleased | Managed source exists, but no private draft is ready. | Repair the app or create its first draft. |
| Draft ready | A private draft can be inspected. A prior live release may still be serving coworkers. | Test the draft, review remaining exposures, then publish or revise it. |
| Live | A release is currently serving coworkers. | Monitor it, review activity, or begin a separate draft for the next change. |
| Needs attention | A release or platform action failed or requires an owner decision. | Inspect the failure, retry safely, revise source, or roll back. |
What the operator can inspect
Releases
The current live release, private drafts, failures, source lineage, and prior releases available for a code rollback decision.
Connections
Company-owned credentials and resources, health, which apps use them, and the blast radius before rotation or revocation.
Audit
Attributed platform and app-management actions with actor, action, target, time, and bounded event details.
Data and resources
Attached resource identity and limited operational evidence such as table names or counts where the current managed database seam supports it.
Platform
Installed platform identity and health so operators can distinguish an application problem from an installation problem.
Read centrally, change through the owner
The console is deliberately not a second application-control plane. It reads platform state and deep-links an operator to the responsible owner's workbench for publish, rollback, retry, access, configuration, connection, archive, and deletion actions. Those actions use the same Garden command boundary as the agent and append an attributed audit event.
Fleet consoleFind and inspect
→
Owner workbenchReview and confirm
→
Garden CLIOne mutation seam
→
Platform recordRelease and audit evidence
Controls are concrete, not a governance label
- Every app has a source and release identity rather than an untracked laptop process.
- A private draft is distinct from the release coworkers use.
- Google access changes, configuration changes, connection rotation, rollback, archive, and unarchive pass through release-shaped actions.
- Company connections expose ownership, health, app bindings, and revocation impact without putting Garden in every external request.
- Failure remains visible alongside the prior live state instead of replacing it with a generic “deployed” badge.
Current governance limits
Not established by this pilot
- General teams, role-based administration, delegated approvals, and separation-of-duties workflows are outside the current scope.
- The console does not mutate apps directly; action handoff depends on the responsible workbench and owner.
- Inventory does not prove that every shadow application in the company has been discovered.
- Connection visibility does not provide per-call policy enforcement or an audit of every request an app sends to an external service.
- Operational visibility does not replace application-specific authorization, security review, backup, restore, or incident response.
Related Garden evidence
This page describes the current design-partner pilot, not a general enterprise-governance certification. Send product questions or corrections to hello@gardenai.ai.