Deployment optionsRun the engine yourself, or have us run it for you.
The Hi, Moose engine collects AI search answers and keeps the record. It can run in the desktop app on your own computer, or on a dedicated server that we set up and maintain for your organization.
Where it runs is a separate choice from how you connect. Agents use MCP and applications use the REST API in either case, and both require sign-in.
mcp.himoose.com/mcpapi.himoose.com/v1Managed
Dedicated server we run for you
Set up by our team
An engine that stays on, without anyone on your team looking after it.
On the desktop app, the engine works while the computer it's installed on is running. That suits a practitioner who uses the app every day. It's a weaker fit when agents and applications need answers at any hour, or when no one wants to be responsible for keeping a machine on.
With a managed environment, we provision a dedicated Windows server for your organization and keep the engine running on it. Your agents and apps connect to the same MCP and REST addresses. The difference is that the work no longer depends on a computer someone has to keep on, updated, and checked.
- Provisioning a dedicated Windows server for your organization
- Keeping the engine on and signed in, so scheduled collection and agent jobs run at any hour
- Engine updates, including changes when an AI search engine changes how it answers
- Watching for failed or incomplete runs, so gaps in your history are caught and flagged
- Keeping your environment separate from other customers'
- The agents and applications that connect to it
- What you track: projects, prompts, engines and competitors
- Who on your team gets access, and with which key scopes
Each environment is set up by our team. The support, access and maintenance it includes are agreed with you before it goes live.
Your agent can set up a server. Someone still has to look after it.
Standing up an always-on machine is a short job for a coding agent. Keeping it useful is ongoing: the server needs to stay up, the engine needs updates, and failed runs need to be noticed before they leave gaps in a record your reports depend on.
A managed environment moves that work to us. We run the same engine for other customers, so the upkeep is shared work for our team rather than a new job for yours.
Who runs what, in each option.
Self-hosted setups are agreed case by case. We confirm the configuration, MCP and REST access, and who maintains what before we describe one as supported.
| Compare | Local | Managed |
Self-hosted |
|---|---|---|---|
| Status | Available now | Available. Set up by our team for each customer. | By arrangement |
| Where the engine runs | The desktop app on a supported Mac or Windows computer | A dedicated server instance for your organization | An environment your organization controls |
| Who sets it up | You install the app | Our team provisions it | Agreed with you |
| Who keeps it running | You keep the computer on with Hi, Moose open | Hi, Moose | Agreed with you |
| Scheduled collection | While the computer is on and the app is open | On schedule, independent of anyone's machine | Confirmed for your configuration |
| MCP jobs | While the computer is on, the app is open and signed in | Any time | Confirmed for your configuration |
| REST API reads | From the cloud, with the app closed | From the cloud | Confirmed for your configuration |
| REST-started runs | Wait up to 24 hours for the computer | Picked up by the managed server | Confirmed for your configuration |
| Sign-in | Required: OAuth for MCP, API key for REST | Required: OAuth for MCP, API key for REST | Required: OAuth for MCP, API key for REST |
Which one fits.
One practitioner works in the app most days, and agent requests can wait until their computer is on.
Local Download the desktop appAgents or applications need the engine at any hour, and you don't want someone on your team maintaining a machine for it.
Managed Ask about a managed environmentYour policies require the engine to run in an environment your organization controls.
Self-hosted Talk to us about your environmentA managed environment can be part of a team engagement.
In a forward-deployed engagement, our practitioners and engineers set up the engine, connect it to your agents and systems, and work with your marketing team on what to fix and publish. If a managed environment suits your stack better than the desktop app, we include it in the setup.
Tell us what your agents need to reach.
For a managed or self-hosted environment, tell us which agents and applications will connect, what you want tracked, and any requirements for where your data lives. We'll come back with what we can set up and what it includes.