Cuttlefish
Request a pilot Download
Governed AI work environment

Put AI to workon the systemsyou already run.

Bring your own AI. Cuttlefish puts it to work across your systems, with authority your organization sets and reviewable evidence for governed work.

Windows, macOS, LinuxPhone appBring your own AI
Watch one request, start to finish
Why Cuttlefish

Agents can reach your tools. Real work needs control.

Connecting a model to APIs, files and browsers is the easy part. Running real systems means knowing what an agent may see, what it may change, who approved it, and what proves the result. Cuttlefish answers all four in every piece of work.

Access becomes authority you define.

Each connected capability is classified before any agent can use it: read, prepare, require approval, or block. Anything undescribed stays off.

Governed work leaves reviewable evidence.

Approvals, evidence and signed receipts are captured as the work happens, so any result can be inspected later by the people accountable for it.

Your work outlives any model.

Memory, history, approvals and receipts belong to your organization. Switch providers and the work carries on where it was.

One environment

The work doesn't end when the window closes.

Start from the software already open. Cuttlefish builds the view, brings in agents and people, runs the live review, and keeps the work moving after everyone leaves.

Desktop Presence

Ask from wherever you're working.

A compact bar sits above your work. Call it with a shortcut or your voice, point it at the app in front of you, and describe the outcome. The full Cuttlefish window can stay closed.

  • Follows your focus

    Context tracks the active app, or the sources you pick.

  • Voice or keyboard

    Speak or type. Both take the same governed path.

  • Only when you ask

    Nothing on your screen is watched in the background.

  • Answers where you are

    A compact result, a Companion window, or Home.

Companions

A team of agents, each with its own job.

Each Companion is an independent agent runtime with its own tools and responsibilities, running on the AI connection you assign. Home sets the objective and keeps watch while Companions hand work directly to one another.

  • Independent by design

    Its own identity, context, memory and AI connection.

  • Direct handoffs

    Findings pass straight between Companions, always attributed.

  • Authority stays with you

    Permissions come from your organization's policy, never the agent or model.

  • Work that keeps going

    Close the window. Authorized work continues and reports back.

Living Surfaces

The right interface. Right where the work is.

Ask for the view, dashboard or tool the job needs. Cuttlefish builds it beside the software you already use, connects it to the sources your organization permits, and keeps it useful as the work moves on.

Living Surfaces in practice

Ask once. Then work in the answer.

A chat answer is text you read once. A Living Surface is built from the sources your team may use, responds when you change it, and stays connected while the data moves.

Working Groups and Stage

Bring people and their agents into the same work.

A Working Group gathers the people, agents, artifacts and decisions around one objective. Colleagues join with their own agents and keep their own accounts and private context. When it's time to present, Stage puts the approved result in front of the room.

  • Your environment stays yours

    Each person's models, apps and private context remain with them. Only permitted results are shared.

  • Every contribution attributed

    People and agents work toward one objective, and every message, handoff and result says who it came from.

  • Present from the work

    Stage shows the approved version to an audience while the group keeps working behind it.

  • Control you can pass

    Hand presenting to a colleague or an authorized agent, and take it back when you're ready.

Governance and proof

Policy before action. Proof after.

Cuttlefish doesn't rely on a model promising to behave. Approved access governs each operation, changes wait for additional approval when required, and action records and supporting evidence make the work reviewable.

CompilingClient Operations · 8 capabilities

Read-only

Look, don't change.

read_ticket
list_incidents

Prepare-only

Draft and stage. The real action waits.

draft_ticket_update
draft_customer_email

Needs approval

Runs after a person approves.

update_ticket
restart_service

Blocked

Never runs. Undescribed actions land here.

delete_ticket
export_all_records
ReceiptIllustrated record
Action
update_ticket · INC-4821
Requested
Ops Agent, for Riley Park
Approved
Riley Park · 10:43:12
Policy
Changes need approval
Evidence
Before and after state, 2 screenshots
Outcome
Verified · 10:43:51
Ed25519 · 9f2c 81d0 4b7e … e41aSigned
Governance guarantees

Rules that hold for every agent and every model.

Your organization sets the authority. Cuttlefish enforces it the same way for every connection, Companion and generated interface.

Classified before use

Allowed operations follow your organization’s permissions and required approvals.

Fails closed

Unknown actions, missing credentials and unregistered targets are blocked by default.

Approval where it matters

Reads and drafts stay within allowed access. Changes wait for additional approval when organization policy requires it.

Evidence with every result

Cuttlefish records what was used, what changed, what was denied and what proved the outcome.

Revocable at any time

Grants, connections and environment capabilities can be withdrawn, and the change takes effect on the next action.

No raw power for generated interfaces

Apps and views request actions through Cuttlefish. They never hold shell, file, browser or credential access themselves.

BYO AI

Bring your own AI. Keep the work.

Connect the providers and models you already use with your own API keys, or run them locally. Cuttlefish supplies the connections and the governance, never the models. Switch providers and the memory, history, approvals and receipts stay with you.

  • Your keys, your accounts

    Every connection runs on your own provider account. No resold access, no bundled credits.

  • Keys sealed, never shown

    Local model keys stay in the OS keychain. Cloud provider keys are stored encrypted by Cuttlefish. Never in plain files, never shown to a model.

  • Local models, first-class

    Ollama, LM Studio and any OpenAI-compatible endpoint work beside hosted providers.

  • Governed by your policy

    Your organization sets which connections each team and Companion may use.

Enterprise environments

Connect an environment, not a raw toolbox.

Connect an approved system to a project and review the operations your organization permits. Independent assistants use allowed access, request approval when required, and keep action evidence for review. This fictional demonstration illustrates the setup experience.

  • Tenant identity and policy

    Membership, roles, devices and policy come from your organization's identity.

  • Surface Packs

    Role-ready experiences for IT, support, compliance, platform and operations teams.

  • Private and hybrid routes

    Tenant-approved providers, private endpoints, or deployments that use no frontier model at all.

  • Audit and evidence access

    Approvals, receipts, run history and revocation stay under your administrators' control.

Mobile

Decide and continue from your phone.

Sign in with your organization and pick up the same conversations, decisions and Working Groups you have on the desktop. When work needs your computer, hand it over with one tap. Your organization decides which phones can link.

  • One "Needs you" inbox

    Every decision waiting on you, with the same risk shown as on the desktop. Decide on either device and both settle.

  • Linked with your approval

    Tap Link next to your computer or scan its code. You approve the phone on the computer before it connects.

  • Encrypted and signed

    Phone and computer talk over encrypted connections, and the phone signs each decision with its own key.

  • Hand-off, not dead ends

    Local files, models and apps continue on your computer with one tap, even if it's offline right now.

Built for

For the teams responsible for real systems.

These teams already manage permissions, change control, client boundaries and evidence. Cuttlefish lets them bring AI into that work without handing a model unrestricted access.

IT and MSP operators

Work across client environments with clear boundaries, evidence packs and approval paths.

IT and MSP

Platform engineering

Expose internal systems through governed capability maps instead of raw model tools.

Platform teams

DevOps and GitOps

Put approval gates, evidence and receipts around every operational change.

Architecture

Enterprise AI operations

Roll out AI work under tenant policy, role surfaces and a complete audit trail.

Enterprise
Infrastructure

Runs on AWS, locked down by default.

Cuttlefish uses Amazon Web Services for hosted services and public delivery. Device resources, model requests, hosted account data, and governance records follow their respective access and data-processing controls. See our privacy and security pages for their scope.

ClientsDesktop and phoneDevice and hosted credentials use protected storage
EdgeEncrypted in transitProtected connections to hosted services
ComputeProtected hosted servicesOrganization access controls
Data and keysEncrypted service dataAuthorized access and retention

Protected hosted services

Hosted work follows organization identity, access policy, and the supported service controls.

Protected account records

Hosted history and settings are protected in transit and at rest, as described in our Privacy Policy.

Protected credentials

Authorized connections use credentials held in the appropriate protected device or hosted store.

Data encryption

Hosted data uses encryption and access controls appropriate to the service and agreed processing arrangement.

Retained governance evidence

Governance records have separate integrity and retention requirements. Review the Privacy Policy and your signed agreement.

Least-authority access

Access to connected systems is limited by the permissions your organization grants.

Technical depth

Go deeper. It's all published.

The architecture, runtime contracts, security posture and operating guides, written for the people who review before they approve.

Platform overview The complete environment runtime Approved connections, reusable apps, browser work, and independent model choices. Read the overview Technical architecture Seven diagrams, end to end Independent assistants, approved access, saved work, and signed action evidence. Explore the architecture Environment runtime Connect a system by manifest How to define allowed work in an illustrated environment. Review the example
Get started

Start with one real environment.

Install Cuttlefish on your desktop, or map one environment with us and prove the approval and evidence loop on your own systems.

Desktop

Install Cuttlefish.

Bring your model access, connect approved sources, and start from Desktop Presence.

Latest releaseWindows, macOS and Linux installers, with release notes.
Download
Operator pilot

Map one environment.

Compile governed capabilities for one real system, test the approval boundaries, and turn a repeated workflow into an installed App.

Email sales@getcuttlefish.app

Request a pilot
Enterprise

Bring it under tenant control.

Tenant identity, policy, role surfaces, private model routes and evidence access, set up for your organization.

Email sales@getcuttlefish.app

Contact sales