Galpi · Mothership · Naru · Golden Image docs
Galpi, the chat that asks and builds; Mothership, the platform for internal AI apps; Naru, which offers legacy systems as AI tools; and Golden Image, the base for Mothership apps. How to install, use and run them.
The four repositories are one product family. Galpi, Mothership and Naru can each be installed and used alone, and connect to each other when they sit together. Golden Image is the base Mothership apps are built from, not a product on its own.
A chat that asks and builds
Every chat gets a workspace (a VM) where an agent reads, runs and changes files and repositories to answer. Start from files and conversation, or pick a project's git repositories, change the code and check it in a preview.
The platform for internal AI apps
Companies, members and permissions; app versions and environments (shared validation, production); and the data, files, AI, knowledge search and external tools apps use, behind one gateway. Apps ship as one ZIP.
Legacy systems as AI tools
Offers groupware and JSP screens, REST and SOAP, and databases like Oracle and Tibero as MCP tools. Naru handles authentication, network, approval, masking and audit; each system's business logic is a pack of TypeScript functions.
The base for Mothership apps
The React app template and SDKs, Python and Node workers, the checker and a document review example app. Upload the ZIP make build produces to Mothership and it's an app.
Who does what
| Product | Owns | Doesn't own |
|---|---|---|
| Galpi | Chats and the agent (with or without a project), projects and their repositories, per-chat VMs and previews, skills, MCP connections, connection keys | Production delivery and review decisions (Mothership), legacy sign-in and calls (Naru) |
| Mothership | Companies, members and permissions, app versions and environments, apps' data, files, AI and knowledge search, external tool connectors | Changing code (Galpi or other tools), per-system legacy logic (Naru packs) |
| Naru | System registration and auth chains, pack deployment, toolsets (MCP addresses) with approval, masking and audit | Pack source control and authoring (Galpi or a local editor) |
| Golden Image | The app template and SDKs, the checker, approved profiles | Running apps (Mothership), repositories and chats (Galpi) |
None of them depends on another's server at runtime. When a connected product is down, only that connection stops.
Where to start
- Try Galpi locallySee its screens and flow on this computer without VMs.
- Install GalpiOne server with Docker Compose and the setup wizard.
- Ship an app to MothershipUpload a Golden Image ZIP to a company and release it.
- Connect legacy systems with NaruRegister systems and add a toolset to an MCP client.
- Connecting the productsWhere and in what order Galpi, Mothership and Naru connect.
- Shared conventionsSign-in, language, and environment variables with one name.