Is holaOS Open Source? License, Source Code, and Self-Hosting Guide

holaOS is open source under a modified Apache 2.0 license, with full source code publicly available on GitHub for self-hosting and modification.

The holaOS project by holaboss-ai maintains complete transparency through its public repository. The README.md explicitly labels the project as "Open source" and directs users to the LICENSE file for complete terms. While based on the permissive Apache 2.0 license, holaOS adds specific commercial usage restrictions that modify the standard terms.

holaOS License: Modified Apache 2.0 Explained

The LICENSE file in the repository root contains the full legal text governing holaOS usage. This modified Apache 2.0 approach provides the core benefits of open-source software—public source code, modification rights, and self-hosting capabilities—with additional guardrails around commercial deployment.

The license structure means you can:

• Access the complete source code at github.com/holaboss-ai/holaOS
• Self-host the entire stack locally without paying fees
• Modify components to fit your specific agent workflow needs
• Fork the repository for private experimentation

Commercial users should review the specific restrictions added to the base Apache 2.0 terms, as these differ from standard permissive licensing.

Complete Architecture: All Components Open Source

Every layer of holaOS resides in the public repository. The modular design allows selective deployment—you can run individual components or the full stack.

Component	Location	Purpose
Desktop Environment	apps/desktop/	Electron-based UI for agent-app interaction
Runtime API Server	runtime/api-server/src/	Fastify back-end exposing workspaces, skills, memory
MCP Integration	runtime/mcp/	Pluggable model-side server protocol
Memory System	runtime/memory/	Graph-based persistent storage on local filesystem
Runtime Client SDK	packages/runtime-client/	TypeScript client for API abstraction
App & Plugin SDKs	packages/app-sdk/, docs/plugin-sdk.md	Developer tools for extending the platform

This unified repository structure means no proprietary black boxes exist—every API endpoint, UI component, and storage mechanism is inspectable and modifiable.

Practical Implementation: Using the Open-Source Runtime

The packages/runtime-client/README.md documents the official SDK for interacting with holaOS programmatically. Below are verified patterns from the source code.

Listing Workspaces via TypeScript SDK

import { createRuntimeClient } from '@holaboss/runtime-client';

const client = createRuntimeClient({
  getBaseURL: () => 'http://localhost:8080',
});

async function listWorkspaces() {
  const workspaces = await client.workspaces.list();
  console.log('Available workspaces:', workspaces);
}

listWorkspaces().catch(console.error);

The createRuntimeClient function handles transport details and provides typed methods for all runtime operations. The getBaseURL pattern supports dynamic configuration for different deployment environments.

Calling Skills from a HolaApp

fetch('http://localhost:8080/api/v1/skills/run', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    skill: 'browser-qa',
    inputs: { url: 'https://example.com' },
  }),
})
  .then(r => r.json())
  .then(result => console.log('Skill result:', result));

Skill routing logic is implemented in runtime/harnesses/src/embedded-skills/, making skill execution behavior fully transparent and customizable.

Key Source Files for Verification

These files provide definitive evidence of holaOS's open-source status and implementation details:

• README.md — Project overview with explicit open-source declaration
• LICENSE — Complete modified Apache 2.0 license text
• packages/runtime-client/README.md — SDK documentation and usage patterns
• apps/desktop/README.md — Electron desktop architecture explanation
• docs/plugin-sdk.md — Extension development guide

Each file is publicly accessible and version-controlled, enabling audit trails for all changes.

Self-Hosting holaOS: Deployment Options

The repository structure supports flexible deployment scenarios:

1. Full Stack — Run apps/desktop/ with runtime/api-server/ for complete local-first experience
2. Runtime Only — Deploy runtime/api-server/ headless for server-based agent operations
3. Desktop Only — Connect the Electron app to a remote runtime instance
4. Custom Forks — Modify any component and rebuild with standard Node.js tooling

No external dependencies on proprietary services are required for core functionality. The shared memory layer in runtime/memory/ uses plain files on disk, eliminating database licensing concerns.

Summary

• holaOS is open source under a modified Apache 2.0 license with source code fully public at holaboss-ai/holaOS
• All architectural components—desktop, runtime, MCP, memory, and SDKs—are contained in a single repository
• Self-hosting is supported without mandatory commercial licensing for personal or internal use
• Modification rights include forking, skill customization, and UI extension via documented SDKs
• Commercial restrictions differ from standard Apache 2.0; review LICENSE for specific terms

Frequently Asked Questions

Can I modify holaOS and deploy it commercially?

The modified Apache 2.0 license permits modifications, but the specific commercial restrictions in the LICENSE file (lines 1-8) may require additional permissions for certain commercial deployments. Personal and internal business use cases are generally unrestricted. Review the full license text or contact holaboss-ai for clarification on your specific scenario.

Is the holaOS desktop app also open source?

Yes. The entire Electron-based desktop application lives in apps/desktop/ with complete source availability. The README.md in that directory documents the build process, dependency structure, and how the UI communicates with the runtime server. No proprietary binaries or obfuscated code are present.

What does "modified Apache 2.0" mean compared to standard Apache 2.0?

Standard Apache 2.0 grants broad patent, copyright, and usage rights with minimal restrictions. holaOS adds commercial usage clauses that limit certain revenue-generating deployments without explicit permission. All other Apache 2.0 provisions—including source availability, modification rights, and warranty disclaimers—remain in effect.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}