Get started
How Inhaus works
The handful of ideas behind every page in these docs.
The pieces
- The connector is an MCP server at
https://mcp.inhaus.dev/mcp. Your AI tool calls its thirteen tools to deploy, share and manage apps. - The control plane stores your apps, versions, permissions and policies. The dashboard at
<workspace>.inhaus.devtalks to it too. - The gateway sits in front of every app. Before any request reaches your code, it checks that the person is signed in and has a role on the app. Your app never sees a password.
- The security scan checks every version for the outside websites your app calls. A domain that is not on your workspace's allowed list is flagged before the app goes live.
Workspaces
A workspace holds apps and people. There are two kinds:
| Personal | Company | |
|---|---|---|
| Address | <name>.inhaus.dev | <company>.inhaus.dev |
| Who signs in to apps | Anyone you share with, by email | People with a company Google or Microsoft account, plus guests if allowed |
| Company directory | No | Yes |
| Admin controls and policies | No | Yes |
Read more in Workspaces.
Apps and versions
An app has a name, an address (<app>--<workspace>.inhaus.dev), an owner and a list of versions. Every deploy creates a new version. Each version is built, scanned and then put live. You can roll back to any earlier version in seconds, without a rebuild.
Each app also gets, at no extra setup:
- its own PostgreSQL database that no other app can see
- its own file storage
- its own secrets, read from
env - logs kept for 7 days
Roles
There are two sets of roles.
On an app: Owner, Editor and Viewer. Viewers can open the app. Editors can also deploy new versions, read logs, manage secrets and query data. The Owner can do everything, including deleting the app and changing who has general access. See Roles.
In a company workspace: Admin and Member. Admins see every app and manage members, teams, policies and the security queue. See Admin.
A company workspace's teams are its groups, made by an admin or synced from your company directory. You can share an app with a team, and every app in the company directory is listed under one.
The security scan
Every deploy runs a security scan: fixed rules first (keys in code, outside domains, known vulnerable packages), then an AI review. A failed scan does not stop the deploy. The app goes live for its owner and the people already added, but it cannot be listed in the company directory, which is how the whole company gets it, until the blocking issues are fixed.
The access log
Every open, share, deploy, export and blocked request is recorded. Admins see the whole workspace. Owners see their own apps. See Access log.