The questions buyers actually ask.

A free Linux workspace in development, built on Omarchy and shaped for working with multiple AI agents. It brings a customizable desktop and agent setup work into one environment. The wider vision includes shared knowledge, skills, connections, and visibility; the preview page distinguishes current work from optional client implementations.

The OS is intended to be free. Maslow charges for discovery, setup, organizational knowledge systems, integrations, workflow implementation, training, and ongoing support. Hardware, model usage, and third-party licenses are separate costs.

A public download is not offered through this website. We can discuss the current development candidate, your hardware, and a suitable evaluation scope. Broad hardware acceptance and a stable signed public release remain open milestones.

No. A technical champion can evaluate the workspace on a dedicated machine. We also deliver knowledge systems and workflows on existing infrastructure, including Ubuntu. Your team can continue using its existing business tools.

Yes. The goal is a useful shared foundation around supported tools, with Codex, Claude Code, and Hermes as the primary setup paths being developed. Each tool has its own sign-in, permissions, integrations, and compatibility requirements.

A place to retain useful notes, decisions, and approved lessons so the next task can build on them. Sharing that knowledge across agents requires a configured knowledge store and access rules. It does not automatically combine private conversations or memories.

We scope connections around the sources and actions a workflow needs. That can include folders, network drives, SharePoint libraries, and business applications through APIs, MCP, or computer use. Access, document quality, and integration reliability are evaluated before rollout.

No. The homepage explains the foundation we are working toward and the systems we deliver for clients. Current preview capabilities, optional integrations, and illustrative workflows are labeled. Client implementations demonstrate delivery experience rather than the contents of a standard OS installation.

Bring a use case or a point of friction. We can begin with discovery, a setup project, a knowledge system, or one workflow. A 90-Day Foundation is available for larger scopes. Fees, deliverables, decision points, and ownership are agreed before work starts.

That depends on the sources, integrations, and scope. We agree a first test and acceptance criteria early, then use the result to decide whether to continue. The 90-day example on How We Engage describes a larger foundation project, not a universal delivery promise.

The selected deployment and model configuration determine the data path. Local services can run on your hardware; an external model or connected application may receive scoped information. We document those paths with your IT counterpart. A Linux installation alone does not keep every agent action local.

Maslow does not use client data to train its own models. External provider use, retention, and training terms depend on the selected service, account, and configuration. These are reviewed for the scoped deployment rather than assumed from the tool name.

We agree whether your team operates it, Maslow provides scoped ongoing support, or responsibility is shared. Training, runbooks, monitoring, maintenance, and an exit path are part of that discussion.

Yes. The diligence page shows which documents are available and which are in preparation. Send your requirements early so we can identify gaps. Maslow does not currently hold SOC 2 certification.

Rakesh David leads the work with specialist engineers as the engagement needs them. You get a named accountable lead, documented scope, and progress you can inspect with your team.