Skip to content
Midstage Admit oneRequest a seat
Menu
Midstage / How it works

Three zones.One boundary.

Your team sits in the house and works downstage, in Zoho. The AI works upstage, in your AWS account. Midstage is the strip between them, where cues go up, results come back down, and the rules are kept.

The stage planUpstage is your AWS account, midstage is the connector, downstage is Zoho, and your team sits in the house. Cues travel up from Zoho; results travel back down into Zoho.UPSTAGE · YOUR AWS ACCOUNTagents · models · memory · logsMIDSTAGEcues · identity · policy · the doorsDOWNSTAGE · ZOHOCRM · Desk · Books · Analytics · CreatorTHE HOUSE · YOUR TEAM
The stage plan

What sits where.

Upstage

Your AWS account

The agents, models, memory and logs. Everything here is in an account you own, under your policies.

AgentCore RuntimeAgent sessions that run for up to eight hours
AgentCore GatewayTurns approved Zoho tools into tools an agent can call
AgentCore IdentityHolds each agent's Zoho OAuth token
AgentCore MemoryWhat an agent saw and said last time
Observability & PolicyEvery step traced; rules on what may be called
Bedrock + GuardrailsModels, with personal data masked in and out
Knowledge Bases & S3Your documents and exports, indexed in place
Step Functions & EventBridgeWaits, schedules and human approval tasks
Midstage

The doors between

Midstage only uses Zoho's own published interfaces. Nothing moves that a Zoho admin didn't authorize.

Zoho MCP serverAgents read and act on Zoho, scoped to their own user
Zoho Flow & webhooksRecord events sent out as cues
DataPrep & AppFlowScheduled bulk exports for analytics and models
Zoho REST APIsResults written back to fields, notes and tasks
Downstage

Zoho

Where your team works, and where every result lands. Nothing about how they use Zoho has to change.

CRM · BiginDeals, accounts and briefs
Desk · SalesIQTickets, triage and drafted replies
Books · InventoryOrders, invoices and collections
Analytics · DataPrepDashboards over all your data
Creator · WidgetsCards and screens inside the record
CliqNudges, answers and hand-offs
The run

Rehearsal. Preview. Opening night.

One role at a time, and a person approves every action until the record shows the role has earned more room.

  1. 01 · Rehearsal

    Cast one role.

    A one-hour walkthrough on your Zoho setup. We find where work stalls, what lives outside Zoho, and which single role should go first.

  2. 02 · Preview

    Run it on real records.

    Midstage is deployed in your AWS account and the role works live Zoho records, with a person approving each action through Zoho's own approval steps.

  3. 03 · Opening night

    Loosen what's earned.

    Where the audit trail shows the role gets it right, approvals relax. Then you cast the next role.

The boundary

Six things security will ask.

Identity

A named Zoho user

Each agent is a Zoho user with its own OAuth grant, and the token stays in your AWS account. No shared admin keys and no screen scraping.

Least privilege

Only approved tools

The agent sees only the Zoho tools your admin approved, and policy rules decide which of those it may call.

Human gates

Your approvals hold

Zoho approval processes and Blueprint stages stay in force. An agent cannot move a step that needs an approver.

Audit

Visible in Zoho

Every action shows in Zoho as that user. Every reasoning step is traced in your account, keyed to the record ID.

Data boundary

Your account, your data

Models, logs and indexes live in your AWS account. Amazon Bedrock does not use your data to train models. Personal data is masked on the way in and out.

Cost

Pay for what runs

AWS usage is billed to your own account, per call, with budget alarms set on day one and no idle servers. Zoho calls draw on your existing API limits.

Your seat for the walkthrough.

One hour on your own Zoho setup: where AI stalled, what lives outside Zoho, and which role would earn its keep first. No charge, and you keep the notes.

Admit oneRequest a seat