PRESHaiPRESHai
A white scale model of a company campus beside the same campus drawn in cyan pixels, with a dotted pixel path running back to the original through a small gate.

Agents do the work. Your people stay in charge.

Who can do what and who signed off, how each request is checked, what every run cost, and how PRESHos connects to the systems you already run.

Talk about your AI projectPRESHos overview

Who can do what,and who signed off.

  • Permissions

    Roles for people and for agents. An agent never has more access than its owner.

  • Approvals

    The agent proposes, the owner decides. Reviews land in one inbox.

  • Audit

    A record of who did it, which agent, which tools and what changed.

PRESHos approval view: a document under review with a pinned comment, the reviewer's note beside it, and Reject and Approve buttons.
A deliverable in review, with a pinned comment and the decision.

Identity, policy and evidenceacross agent execution.

  1. Enterprise identity

    A white model gatehouse with a turnstile, figures waiting, and a pixel badge above.

    SSO and IdP integration

    • MFA support, directory sync
    • Active membership, session

  2. Authorization

    Tenant and membership binding
    User context

    Roles, ownership

    Agent identity

    Assigned roles

    RBAC and tool policy

    Object, field and record scopes

    A white model checkpoint with three lanes: one open, one with a barrier and a booth, one walled off.
    • Allow
    • Approval
    • Deny

  3. Runtime choice

    Three cubes drawn in cyan pixels beside a white model laptop on a desk.
    Cloud
    • Isolated session
    • microVMs
    Local
    • Enrolled Mac
    • User workspace

  4. Connected systems

    A white model gateway wall with pixel streams fanning out to a server rack, an office and a cloud.

    Configurable cloud egress

    • SSRF safeguards
    • Scoped access
    • MCP, APIs and AI models

Shared security services

  • White model storage drums under a dome of cyan pixels.

    Protected data

    • Encrypted storage
    • Private file access
    • Point-in-time recovery
  • A white model vault with its door ajar and cyan pixel keys inside.

    Secrets vault

    • Google Cloud Secret Manager
    • Scoped runtime grants
    • Server-side credentials
  • A white model ledger with a trail of cyan pixels ending in a check mark.

    Audit and approvals

    • Run and tool event traces
    • Human approval records
    • Actor, action, outcome

Usage, results and costfor every run.

PRESHos agent runs report listing sessions with run counts, token usage and effective cost.
Agent runs, with tokens and cost per session.

  • Cost per task

    Every run carries its steps, tokens and cost.

  • By work item

    Rolled up by person, agent and the work it was for.

  • Nothing hidden

    Costs are marked actual or estimated, never left blank.

Connectors, pluginsand automations.

  • Connectors

    Records sync with the systems you run, mapped field by field.

  • Plugins

    Bundles of skills and tools, installed once and granted to agents.

  • Automations

    A trigger starts an agent or an action.

PRESHos automation canvas: a trigger connected to an agent session, a comment action and a status change.
PRESHos integrations screen showing connector cards for Fireflies, Google Calendar, Gmail, Microsoft 365, Google Workspace, Ziflow, ConnectWise PSA, HubSpot, Slack, Twilio Voice, Webex and others.
The connector catalog.

Relatedreading.

More on Platform
The Tampa Riverwalk at night, with downtown towers on the right and a stream of cyan pixels following the railing.

See it on your own workflow.

Bring us the work you want agents to do. We will walk through the permissions, approvals and connections it needs.

Talk about your AI projectPRESHos overview