Skip to content
Shroti Host
Built by Shroti HostIn use internally

AI employee OS

Internal AI operations system with founder approvals

The AI employee OS is an internal system Shroti Host built to run parts of its own business: 29 AI employees across support, sales, infrastructure, finance and other departments do daily routines, draft work and propose actions. Every risky action waits in a founder approvals queue, so no agent can act alone. It is not client work.

This is a private system, so there is no public link.

Screenshots

AI employee OS Command Center with demo data: six objectives in flight, such as a fictional customer's WordPress error and a duplicate payment, seven items waiting for the founder, and system health checks.
Command Center: what the AI employees are working on, and what is waiting for the founder. Demo data.
AI employee OS Today page with demo data: the morning plan, the evening report with 8 of 11 duties handed in, and one card per department with its routine work.
Today: the morning plan, the evening report and each department's routine work. Demo data.
AI employee OS approvals queue with demo data: a founder-only refund that needs a password, and a two-step bundle with an internal ticket note and a customer reply, each showing the exact action it will run.
Approvals: nothing runs until the founder approves the exact action. Demo data.
Profile of the Technical Support Engineer AI employee with demo data: its mission, a task waiting for approval, its 7-day record, and decision rights that allow read, analyze, propose and verify but never execute.
An AI employee's profile: it can read, analyze, propose and verify, but never execute a change on its own. Demo data.

Screens from a demo copy of the system with made-up data: every customer, ticket, amount and note is fictional. The live system is private.

Diagram

How an action moves through the AI employee OS
  1. 1

    AI employee

    Runs a daily routine and drafts work or proposes an action

  2. 2

    Approvals queue

    Every risky action waits for the founder

  3. 3

    Founder decision

    Approve or reject in the founder console

  4. 4

    Role-limited action

    Runs against WHMCS or the server with only the access that role has

  5. 5

    Lessons

    Proposed, approved by the founder, then used next time

What problem does the AI employee OS solve?

A small company has more routine work across support, sales, infrastructure and finance than a founder can do alone.

Handing that work to AI agents is only safe if nothing risky happens without a human saying yes.

What does the AI employee OS do?

  • 29 AI employees across departments that do daily routines, draft work and propose actions
  • A founder console with an approvals queue
  • A learning loop: lessons are proposed, approved by the founder, then used
  • A CEO agent that reviews work
  • A finance ledger
  • Integrations with WHMCS and the server through role-limited access

How did Shroti Host build the AI employee OS?

Shroti Host built the AI employee OS with Next.js, TypeScript and SQLite, connected to AI models through an AI model gateway.

  • Agents propose and humans approve: every risky action needs the founder's approval, and no agent can execute alone
  • Scenario tests cover the founder's mandatory checks
  • Access to WHMCS and the server is limited by role

What does the AI employee OS show about working with Shroti Host?

Shroti Host builds AI into real operations with safety designed in: clear approvals, limited access and tests for the checks that matter.

Services this project is evidence for

Next case studyAI request gateway and usage dashboardInternal AI infrastructure

Want something like this?

Written scope and quote before any work starts.