Mothership
About Mothership
Mothership is the platform a company builds and runs its internal AI apps on. Authentication, company-scoped data, files, models, knowledge search, tools and background work sit behind one gateway.


What it does
The default path is build a frontend app, declare the resources it uses, upload one ZIP. The platform is the app's backend. Add a Python or Node worker only for company-specific integrations or computation.
- Companies and people: one Mothership holds several isolated companies. Employees sign in, choose their company and open the apps available to them. Company SSO (OIDC) is configured per company.
- App versions and environments: an uploaded ZIP becomes an immutable version. It reaches employees only through review candidate → shared validation → approval → production. Each company and environment pins an exact release, so one company's update never changes another's.
- What apps get: record and state data, files and objects, AI generation, streaming and embeddings (OpenAI-compatible), private knowledge search (RAG), durable Runtime runs with human approval, automation (schedules, events, webhooks) and external tools (MCP connectors). → AI, Knowledge, Runtime and automation
- Isolation: app JavaScript runs in an opaque-origin iframe. Only the host holds sessions and keys; apps reach the API through a scoped SDK bridge.


Who does what
| Person | What they do |
|---|---|
| Employee (member) | Signs in, picks the company, uses the apps open to them |
| Company administrator (owner, admin) | Members and team spaces, app permissions, encrypted AI and tool connections, releasing and publishing tested versions, usage and run history |
| Developer | Uploads candidate versions of company apps and prepares shared validation. Production is the administrators' call |
| Service operator | Opens companies and invites their first owners, per-company OIDC, approves integration origins, watches infrastructure and usage |
Works with
- Golden Image — the app template and SDKs. Upload the ZIP
make buildproduces. - Galpi — connect a Galpi project to a Mothership app and change the app by chatting. Galpi sends the source, and Mothership builds it and makes previews and review candidates. Production rights are never handed over.
- Naru — add a Naru toolset as one of the company's external tools and apps call legacy systems in the person's name.
The steps are in Connecting the products.
The repository
| Path | What |
|---|---|
backend/ |
Django gateway (ASGI): auth, companies, app registry, data, files, AI, knowledge, Runtime and automation APIs, workers |
frontend/ |
React host console: catalog, company admin, service admin, the app iframe |
vendor/ |
SDK archives taken from Golden Image (checksums recorded) |
deploy/ |
Production Compose (compose.production.yaml), configuration tool, recovery command |
Next
internal AI apps · business apps · company apps · app catalog