Get started

Introduction

Inhaus puts the tools you build with AI live behind your company login, and shares them with the people you choose.

You asked Claude, ChatGPT or Cursor to build a commission calculator, a lead tracker or an onboarding checklist. It works. Now your team needs to use it, and the usual options are bad: a public link anyone can open, API keys written into the code, and no way to see who opened what.

Inhaus is the step after the AI writes the app. Add one connector to your AI tool, then ask it to deploy:

"Deploy this commission calculator and share it with the sales team, view only."

ClaudeChatGPTCursorVS CodeWindsurf

Your AI tool calls Inhaus. A minute later the app is live at commissions--acme.inhaus.dev, behind your company's Google or Microsoft login, checked for leaked keys, and shared with the eight people on the sales team.

What you get

Deploy from the chat

No hosting account, no build settings. Your AI tool sends the files and gets back a URL.

Company login on every app

Every app sits behind Google or Microsoft sign-in. The app never handles passwords.

Share like a doc

Add people, teams or the whole company as Viewer or Editor.

Security scan

Each deploy is checked for keys in code, data sent to unknown sites and risky packages.

Built-in data

Every app gets its own database, file storage and secrets.

Admin visibility

Admins see every app, owner and viewer, plus a log of every open, share and deploy.

Who Inhaus is for

Builders

The ops manager, sales lead or analyst who built something useful with AI. You deploy, share and fix your apps without leaving the chat, and without asking a developer.

Viewers

The people who use the apps. They sign in with the company account they already have. They never need an Inhaus account and they are never charged.

Admins

IT, the founder or the ops lead. You see every app in the company, decide which outside sites apps may call, review apps before they go company-wide, and hand over apps when someone leaves.