Bring AI to Your Data, Not Your Data to Public AI
Every Reeve box runs Reeve: open AI models, your documents and the connections to your tools, all on one machine on your network. The data and the model sit in the same locked room, and you decide who holds the keys.
One Box, Only Your Data
Each client gets its own box. It holds only your data and learns only from your data.
Open Models, Licensed for Business
Every standard model is Apache 2.0 or MIT licensed and runs on the box. No cloud AI service is called unless you choose to turn one on.
Controls Built In, Not Bolted On
Roles and departments are enforced in code. Every change goes through one recorded path, with brakes Reeve can't loosen.
Your business already has the knowledge. Reeve helps you use it.
Empower Your Team. Protect Your Data.
What Your Team Can Do
- Search policies, procedures, manuals, contracts and internal documentation
- Summarize large documents and complex information
- Draft proposals, reports, emails and customer communications
- Answer internal IT, HR, compliance and operations questions, with the source cited
- Keep institutional knowledge when experienced employees leave
- Speed up onboarding and training
What Reeve Runs for IT and Security
- Triages security alerts and gathers the evidence, so a person can decide quickly
- Works tickets from open to close, inside the change windows you set
- Keeps tool policies, user accounts and device health in line
- Writes, enforces and evidences SOC 2, CIS, CMMC and NIST 800-171 policies, each one approved by you
- Runs weekly, read-only threat hunts in your CrowdStrike SIEM
- Sends each person a morning brief, and you a weekly health report
How Your Information Is Protected
- One dedicated box per client, on your own network
- Encryption in transit and at rest
- Single sign-on through your identity provider, so your existing multifactor sign-in applies, plus role-based access
- Each tool's credential lives only in that tool's connector, never in the AI model
- Content is data, never orders: nothing Reeve reads can authorize an action
- Every action recorded: proposal, approval, before-snapshot, change and check
Private AI That Still Works With Your Cloud Apps
Keeping the AI under your control doesn’t mean cutting it off. On a Connected box, Reeve can read from and work in the SaaS tools your team already uses, through their APIs or MCP servers. The AI model still runs on your box. Only the data a task needs goes to the app, and only to apps you approve.
Standard APIs
Ready at launch: Microsoft 365, CrowdStrike, ticketing and PSA tools, and CRM and accounting systems, all through their published APIs. More are added as clients need them.
MCP Servers
The Model Context Protocol (MCP) is an open standard for connecting AI to tools and data. Reeve connects to MCP servers today, whether an app vendor hosts it or we run it on your network.
Custom Connectors
No ready-made connector? Reeve’s coder model builds and maintains one for your system, and its vision model can work tools that have no API at all.
How Every Connection Stays Under Your Control
- You approve every connection, and each one is limited to the actions you allow, read-only or read-write
- Outbound traffic goes only to approved destinations. Everything else is blocked
- Each connection’s credential lives only in its connector, never in the AI model
- What comes back from an app is data, never orders: nothing Reeve reads can authorize an action
- Every call is recorded: what was sent, to which app, and why
- Changes in your apps go through the same Propose, Approve, Snapshot, Change path as every other change
- Your prompts go to a cloud AI model only if you opt in, and only for the tasks you choose
Sealed boxes have no outside connections, except the single allow-listed CrowdStrike connection used in pilots. Other app connections are available on Connected boxes.
You Decide How Much Reeve Does on Its Own
Some clients want a person to approve every change. Others let Reeve close routine work itself. Either way, the same guards apply, and they work without anyone watching. Pilots start with a person approving every change.
Every change Reeve makes takes this path. The before-snapshot is kept with the record.
Brakes It Can't Loosen
Limits per hour, per tool and per client. Bulk changes always go to a person: by default, anything touching 10 or more devices or 5 or more users. Reeve pauses itself if errors or reopened tickets spike. A person can tighten a brake; Reeve can never loosen one.
Approvals Never Approve Themselves
Every approver has a backup. An approval nobody answers expires and moves to the next person. It never approves itself.
A Watchdog Outside the Box
A heartbeat is checked from outside the box. If it goes quiet, a ticket opens and on-call is paged, and people work from the runbooks until Reeve is back.
Change Windows You Set
Set change hours and freeze dates. Outside them, Reeve proposes and queues. Containment during an incident follows your rule.
Updates in Stages
New versions pass a test suite, then run on Inceptus's own box, then one client, then everyone. If the report card drops, the update rolls back automatically.
A Monthly Report Card
Accuracy confirmed by your people, tickets handled, time to resolve, time saved, overrides and reopens, per tool. It decides how much autonomy Reeve earns.