Deploy internal tools built with AI: a 3-step guide

You can deploy an internal tool built with AI in three steps: add the Inhaus connector to your AI tool, ask it to put the tool live, then ask it to share the tool with your team. The tool goes live behind your company login, so only the people you choose can open it.

It works with any AI tool that supports MCP connectors, including Claude, ChatGPT, Cursor, Claude Code, VS Code and Windsurf. You don't need a hosting account or build settings.

Before you start

• A tool your AI built: a calculator, tracker, checklist, dashboard or form. It should be a web app in HTML, JavaScript or TypeScript, with or without server code.
• An Inhaus account and a workspace. Create one at inhaus.dev/getstarted. Pick Company if you want to share with people at your company behind your company login. Your first 7 days are free.

The 3 steps

1. Connect your AI tool to Inhaus

   Add this connector URL to your AI tool's connector or MCP settings:

   Copy

   https://mcp.inhaus.dev/mcp

   Your browser opens inhaus.dev. Sign in, pick the workspace and choose Allow. You only do this once. Setup for each tool: Claude, ChatGPT, Cursor, Claude Code, VS Code, others.

2. Ask it to put the tool live

   In the chat or project where the tool is, ask:

   Copy

   Deploy this to Inhaus as "Commission Calculator".

   Your AI tool sends every file to Inhaus. Inhaus installs packages, bundles the code, runs a security scan and puts it live. Usually in under a minute, you get back the link (https://commission-calculator--acme.inhaus.dev), the version number and the scan result. Only you can open it so far.

3. Share it with your team
   Copy

   Share it with priya@acme.com and the sales team, view only.

   Inhaus emails each person the link. They sign in with their company Google or Microsoft account and use the tool. They don't need an Inhaus account.

That's it. The rest of this page covers what happens next.

What happens on each deploy

1. Queued. Inhaus stores the files and creates a new version. Large apps are zipped and uploaded first, on their own.
2. Building. Packages from package.json are installed and TypeScript and JSX are bundled.
3. Scanning. The security scan checks for keys in code, calls to outside websites and known vulnerable packages.
4. Live. The version goes live behind the Inhaus gateway.

If the build fails, the previous version stays live, and your AI tool gets the error so it can fix it and try again. See Deploy an app.

Keep it working

• Change it. Ask for the change and say "redeploy". It becomes a new version at the same link. Everyone keeps their access.
• Undo a change. "Roll back the commission calculator to the old version." It's live again in seconds.
• Fix errors. "Check the logs for the commission calculator and fix the errors." Logs are kept for 7 days. See Logs.
• See who uses it. "Who opened the commission calculator this week?" See Access log.

FAQ

Next steps

• Quickstart: the same flow, with the setup for each AI tool.
• How to deploy vibe-coded internal tools securely
• Share an app