Tools are not authority.
A connected API, MCP server, browser page, or local command does not automatically become executable authority. Cuttlefish classifies capabilities before they become available to work.
Governed environment runtime for AI work
Turn real environments into governed AI work surfaces.
Cuttlefish connects approved business systems, helps independent assistants work within organization permissions, and keeps work results and action evidence available for review. Repeated work can become a reusable application or working view.
Choose supported models while your account and organization retain saved work, approvals, and results. Model choice does not replace your organization’s authority over connected systems.
The missing layer
Connect systems. Keep control of the work.
MCP servers, sandboxes, browser sessions, APIs, files, and shell commands are not enough. Once AI touches real environments, the hard questions change.
What is the agent allowed to see? What can it prepare but not execute? What requires approval? What must be blocked? What evidence proves the result? What becomes durable state after the action?
Cuttlefish is built for that custody layer.
Execution is not proof.
Tool output is not enough. Cuttlefish captures evidence, verification state, receipts, approvals, denials, and run history so action can be inspected later.
Models are not the durable layer.
Use supported hosted, on-device, and private model endpoints according to your organization’s policy and provider entitlement. Saved conversations, work, approvals, and results remain in Cuttlefish across approved model choices.
Operating architecture
Persistent enterprise agents with independent runtime ownership.
Home supervises a governed environment of independently operating agents. Each runtime keeps its own identity, model assignment, task and conversation state, saved context, event history, connector authority, lifecycle, and Companion surface. Human and organization identity define the outer boundary; delegated authority narrows what each agent may do inside it.
Independent runtimes
Companions retain separate execution state and model routes while Home assigns, observes, steers, pauses, and resumes work across the environment.
Agent collaboration
Addressed agents can delegate bounded tasks, exchange permitted context and artifact references, and return results with distinct identity and provenance intact.
Governed capability execution
Every connector and native operation is checked against identity, policy, and approval before it runs, and leaves evidence after.
Provider continuity
Cuttlefish keeps saved work, approvals, results, and action evidence above local, hosted, and private model routes.
Durable work and signed evidence
Workspace Canvas preserves inspectable artifacts. Current governance receipts use Ed25519 signatures to bind captured actions to attribution and integrity of the captured governance record.
Enterprise administration
Organizations manage membership, runtime and connector scope, provider policy, approvals, evidence access, and cloud or hybrid operating routes.
How Cuttlefish works
From environment to governed action.
Connect approved systems, review allowed operations, prepare changes, and obtain additional approval when required. Inspect available results and supporting evidence, then reuse the work through applications and working views.
Connect or invoke
Register an enterprise environment, connect a local source, speak a command, invoke Ambient, or start from Home.
Resolve context
Cuttlefish identifies the environment, source, surface, model route, current state, and authority boundary.
Review allowed operations
Available systems become governed capabilities - not raw unrestricted tools.
Prepare safely
Cuttlefish can inspect, draft, summarize, plan, and prepare reversible work without crossing execution boundaries.
Approve and execute
Consequential actions route through policy, approval, grants, and runtime execution.
Prove and reconcile
Saved work, approvals, action records, and supporting evidence let authorized people review what happened and continue the task.
The result is not an agent transcript. It is operational state.
Enterprise Environment Connector Runtime
Connect an environment, not a raw toolbox.
Connect an approved environment and review the systems and operations your organization allows. Assistants receive permitted access rather than unrestricted control. Required approvals and available action evidence support review of the work.
Discover
Review the approved connection.
Review the environment connection and supported operations in your organization’s setup flow. Connection checks do not grant unrestricted access.
Manifest URLContract validationOrigin and health checks
Compile
Build the capability map.
The operations, web targets, and connector actions an environment exposes become named, scoped capabilities.
Capability compilationContext and evidence routesRegistered browser targets
Classify
Assign authority boundaries.
Every capability receives a state before use, so the model sees governed affordances instead of raw tools.
Read-onlyPrepare-onlyApproval-required or blocked
Operate
Execute only through the runtime.
Approved work routes through governance, captures proof, and becomes durable operational state.
Governed executionEvidence + receiptRun history + reusable surface
Discovery and compilation do not execute work. Execution starts only after the capability state, approval boundary, and runtime route are known.
Discover without granting control
Cuttlefish can inspect what an environment exposes without treating every endpoint, browser target, or tool as executable authority.
Define permitted operations
What an environment exposes becomes a set of named, governed capabilities, each with its own risk level and policy.
Fail closed by default
Unknown authority, missing credentials, incomplete metadata, unregistered targets, unsafe routes, or blocked risk classes prevent execution.
Audit the work
Cuttlefish records what was approved, denied, executed, verified, and receipted so operators can inspect the full trail.
First beachhead
Built for the people responsible for real environments.
Cuttlefish is broad because real work spans apps, files, browsers, systems, devices, models, automations, and teams. But the first wedge is precise: IT operators, MSPs, platform engineers, DevOps and GitOps leads, security-minded infrastructure teams, and technical service firms.
These teams already manage systems, permissions, approvals, client boundaries, change control, and evidence. Cuttlefish gives them a governed way to bring AI into that work without giving models unrestricted access.
MSP and Managed IT
Operate across client environments with organization access controls, evidence packs, approval paths, and reusable operator workflows.
Platform Engineering
Expose internal systems through governed capability maps instead of raw model tools.
DevOps and GitOps
Use approved environment configuration, approval gates, evidence, and receipt trails around operational change.
Enterprise AI Operations
Deploy AI work execution with tenant policy, role surfaces, audit trails, and model-independent continuity.
5-surface shell
Simple surface. Deep runtime underneath.
Home, Workspace, Browser, Apps, and Settings are the main navigation. Independent Companions, Living Surfaces, Desktop Presence, Working Groups, and Stage keep assigned work alongside it. Home provides supervision without becoming a required relay for every assistant’s task.
Home
Home
Conversation, current work, approvals, results, Ambient handoffs, recent evidence, and the left-side outcome drawer.
Workspace
Workspace
Create, inspect, validate, version, and promote generated artifacts, workflows, and installable workspace apps.
Browser
Browser
Operate and verify web apps, pages, generated surfaces, localhost projects, and browser-bound workflows with evidence.
Apps
Apps
Open installed workspace apps, connected apps, generated operator surfaces, companion windows, app permissions, and app health.
Settings
Settings
Manage connections, governance, privacy, model routes, Ambient controls, Bridge grants, memory policy, enterprise settings, and advanced diagnostics.
Independent work appears in Companion windows, working views, approvals, and results where it is useful. Authorized assistants can continue their assigned work while you switch views.
Ambient + Speak
Invoke Cuttlefish where the work is.
Cuttlefish Ambient lets users invoke Cuttlefish from selected text, files, folders, browser pages, screen regions, hotkeys, command palette actions, result cards, and mobile continuation surfaces.
Cuttlefish Speak turns voice into governed work: dictation, implementation prompts, runtime commands, workspace artifacts, app creation, memory proposals, browser verification, and approval-routed actions.
Explicit invocation
Ambient is not silent monitoring. The user invokes Cuttlefish at the point of work.
Local-first capture
Context is minimized, previewed, redacted, and routed through the right runtime boundary.
Voice-to-work
Speak can draft, command, build, route, verify, or prepare work without bypassing approval.
No shortcut around governance
Consequential work still routes through policy, approval, evidence, and receipts.
Workspace App Foundry
Turn repeated work into governed apps and surfaces.
When a workflow repeats, Workspace can turn it into an application or working view with the access your organization permits. Review and verify the resulting work before using it for consequential operations.
Define
Describe the repeatable work.
The user names the workflow, expected outcome, inputs, and where the finished surface should live.
Describe workflowIdentify operator roleSet success criteria
Generate
Create the surface and bind data.
Workspace generates the UI, wires state, and binds it to approved runtime objects instead of placeholder data.
Generate surfaceBind runtime dataConnect evidence and artifacts
Govern
Declare permissions and verify behavior.
Review the application’s required access and available checks before installation. Its operations remain subject to organization permissions and required approvals.
Declare permissionsVerify behaviorCheck policy fit
Install
Install the reviewed application.
Useful surfaces become installed apps, companion windows, role surfaces, or enterprise pack projections.
Install into AppsOpen in Home, Browser, or WorkspaceLaunch as Companion Window
Generated surfaces are not granted raw host power. They request Cuttlefish-mediated actions, and consequential work still routes through policy, evidence, and receipts.
Runtime-bound, not fake data
Applications and working views can present approved system information, work results, and available evidence without receiving unrestricted access.
Organization permissions
Apps declare what they need. Host actions are mediated by Cuttlefish, not granted directly to generated UI.
Verified before install
Surfaces can be checked for render behavior, action wiring, accessibility, security posture, and policy fit.
Apps, not throwaway artifacts
Useful surfaces can become installed apps, companion windows, role surfaces, or enterprise pack projections.
Browser Runtime
Operate and verify web work with evidence.
Cuttlefish includes a governed browser runtime for web workflows, generated app previews, localhost verification, browser targets from enterprise environment manifests, and evidence capture. It can inspect page structure, execute approved actions, verify outcomes, and preserve artifacts for review.
Web and app verification
Open web targets, generated apps, and local builds in the same governed verification surface.
Page-aware operation
Use page structure, accessibility, DOM signals, screenshots, and runtime evidence where available.
Operator handoff
Pause automation, hand the session to the operator, and resume without losing run state.
Enterprise browser targets
Choose approved browser destinations and permitted operations for connected enterprise systems. Browser work remains subject to organization access controls.
Evidence capture
Screenshots, page state, artifacts, and outcome checks can attach to Runs and receipts.
My Environment
Your own setup, governed.
Manage approved apps, folders, browser pages, local services, model endpoints, and repeated workflows for your work. Connecting a resource does not grant unrestricted access. Local and remote requests follow their respective permissions and data-processing routes.
Apps and folders
Point Cuttlefish at approved files, folders, and app contexts without turning the whole machine into open access.
Local services and models
Register local endpoints, private models, and local services with health, privacy, and routing metadata.
Devices and workflows
Discover useful environment signals while keeping control, approval, and revocation visible.
Your own apps
Turn repeated workflows into installed Cuttlefish apps with permissions and receipts.
Governance and proof
Policy before action. Evidence after. No raw authority.
Cuttlefish does not rely on a model promising to behave. Actions route through capability classification, policy checks, consent, approval, runtime execution boundaries, evidence capture, and receipts.
Unknown capabilities fail closed. Generated UI is never sovereign. Prepared work is not execution. Connected systems do not become unrestricted tools.
Capability classificationEvery capability is classified by risk before it can be used.
Approval where it mattersRead-only work, drafting, preparation, external commits, privileged actions, and destructive work are treated differently.
Evidence-backed outcomesCuttlefish records what was used, what changed, what was denied, and what proved the result.
Receipts and RunsConsequential work links to receipts, run history, approval state, evidence, and verification records.
RevocationGrants, connections, bridge permissions, and environment capabilities can be revoked.
No generated-UI authorityGenerated apps request host-mediated actions. They do not receive raw shell, file, browser, desktop, memory, graph, or governance power.
Model-independent intelligence
Models reason. Cuttlefish owns the work.
Use approved provider APIs or compatible on-device, network, and private-cloud endpoints. Provider availability depends on your account, endpoint, and organization policy. Cuttlefish retains saved work, approvals, and results independently of the selected model; the Privacy Policy describes hosted history and memories.
Replace the model without losing the work
Switch between approved models while keeping your saved conversation, work, approvals, and results available.
Local and private models are first-class
Use local, LAN, private-cloud, sovereign-cloud, or external providers according to user or tenant policy.
Providers contribute cognition, not authority
A model can reason, draft, verify, critique, and propose. Cuttlefish decides what is exposed, executable, remembered, or receipted.
Enterprise
One runtime. Tenant-controlled environments. Role-native surfaces.
Organizations configure membership, approved environments and models, required approvals, and review access. Work views can reflect the organization’s roles and permitted systems.
Approved environments
Connect approved systems and browser destinations with access limited to the operations your organization permits.
Surface Packs
Project the same runtime as role-native experiences for IT, support, compliance, platform, operations, and executive teams.
Private and hybrid model modes
Use approved on-device, network, private-cloud, or hosted model endpoints. Discuss complete private-hosting and service-data requirements with our team; model location alone does not make the whole service private.
Audit and control
Approvals, receipts, runs, evidence, revocation, and tenant boundaries remain first-class.
Start now
Start with the environment you already operate.
Install Cuttlefish for your team, or start an environment pilot for IT, MSP, platform, and enterprise teams that need AI to operate safely across real systems.
Desktop
Install Cuttlefish.
Install Cuttlefish, connect approved models, and build your own governed environment with local-first controls, Ambient invocation, Workspace apps, Browser verification, and receipts.
Operator Pilot
Map one environment.
Connect one approved environment, verify its permissions and required approvals, and review action evidence. Then turn a repeated workflow into a reusable application or working view.
Enterprise
Bring it under tenant control.
Bring Cuttlefish under your organization’s membership, system access, model policy, required approvals, and data-processing arrangement.
