Engineered by Dalian Fidwell Technology (fidwell.cn)
ZeroOS AI · Runs on your own Linux servers

Run multi-step AI tasks on your own servers with tracked state and deliverable outputs

Submit a multi-step job in the WebUI. The built-in CEO calls the model API you configure directly to decompose work, acquire exclusive leases, and dispatch open-source executors such as Hermes. Every step is recorded in PostgreSQL so you can inspect outputs, retry failed steps, or route exceptions to a person.

Data disclaimer: test records below reflect Fidwell isolated internal test runs and have not been independently audited. Workflow steps below illustrate system architecture with sample data.

How ZeroOS Executes a Multi-Step Job

Illustrative sample workflow — inspect how task breakdown, execution isolation, and recovery work before booking a live walkthrough.

Architecture walkthrough · sample data ZeroOSAI.com
Operator Action

Enter the deliverable goal, repository/file boundaries, and target verification criteria in the ZeroOS WebUI.

ZeroOS Control Plane

Validates project authority rules, registers the task record in PostgreSQL, and writes an initial execution lease.

State Saved

Status: QUEUED -> PLANNING · Assigned owner and target workspace logged with audit timestamp.

POST /api/tasks { "goal": "Audit 3 repos for outdated dependencies", "workspace": "readonly-mirror" }

Core Control Plane Capabilities

Focused on deterministic task tracking, crash recovery, and clear ownership rather than black-box chat loops.

Available

Direct Model API Routing

Configure Gemini, GPT-series, Claude, DeepSeek, or internal vLLM endpoints in the control plane. Built-in planning calls your API directly.

Available

Lease Locking & Idempotency

Distributed step leases prevent two executors from editing the same target simultaneously, while idempotency keys guard re-runs.

Available

PostgreSQL Persistent Ledger

Task hierarchies, transcripts, tool receipts, and artifact hashes survive server restarts so long tasks resume cleanly from the last verified step.

Available

Scoped Authority Policies

Define read-only paths, secret isolation rules, and explicit operator handoff gates per project workspace.

Available

Automated Verification Gates

Pair every execution step with shell tests, build checks, or content rules before marking a deliverable complete.

Optional

Plug-In LongMemOS Memory

Attach LongMemOS (MemoryBox 2.0) locally over MCP so every ZeroOS executor shares exact past decisions instead of starting cold.

Native Subsystem · LongMemOS.com

LongMemOS: Persistent Long-Term Memory OS for ZeroOS & Standalone Coding Tools

Agents lose project rules and debugging decisions whenever sessions reset. LongMemOS (packaged locally as MemoryBox 2.0 v2.0.4) runs inside your own Linux or Windows network and exposes a standard MCP & HTTP endpoint. ZeroOS workers, Claude Code, Cursor, and Codex read and write shared project memory anchored to exact source passages — with no built-in LLM inside the memory engine.

  • Traceable source passages with original timestamps instead of opaque lossy summaries.
  • ~3.1 MB compressed binary distribution with no embedded model files; change your reasoning LLM anytime without re-indexing.
  • Dedicated product portal also registered at LongMemOS.com (routes to this official documentation hub).
Open LongMemOS Product Page

Recorded Internal Test Evidence & Scope Boundaries

Figures below come from Fidwell engineering records in isolated test environments. They are not third-party certifications or hardware SLAs.

← Swipe horizontally to view full record →
Subject Version / Scope Recorded Outcome Conditions & Boundaries
ZeroOS Control Plane Failover Internal staging build · Nov 2026 ~6.99s failover recovery observed Measured on Fidwell isolated test cluster under simulated worker disconnect; network latency and hardware affect real deployments.
LongMemOS (MemoryBox 2.0) Recall v2.0.4 (embedded_models=false) 463 / 500 (92.6%) on public LongMemEval Internal automated evaluation script on public LongMemEval dataset with external model endpoint; not independently audited.
Hardware Targets Verified v2.0.4 binary release (~3.1 MB) Win11 x86_64 · Linux x86_64 · ARM64 RK3588 Tested on physical devices by Fidwell engineering; macOS is currently in compatibility validation.

Deployment Editions

Choose standalone local memory or full server-hosted agent coordination.

Self-Hosted Core

ZeroOS Server Edition

WebUI control plane, PostgreSQL ledger, lease manager, and worker runtime connectors deployed on your Linux servers or private cloud.

Request Architecture Review
Memory Subsystem

LongMemOS / MemoryBox 2.0

Software release (~3.1 MB) or pre-configured ARM64 RK3588 local appliance for teams sharing context across coding IDEs and agents.

Compare Memory Specs
Combined Stack

ZeroOS + LongMemOS Bundle

Full task orchestration paired with local shared memory across teams, internal codebases, and operational workflows.

Book Joint Walkthrough
Technical Reference & Integration Details (expand to read)

Control Plane Architecture

  • Task state machine backed by PostgreSQL tables for jobs, leases, step transitions, and artifact checksums.
  • Built-in planner communicates directly with operator-configured LLM APIs using explicit API keys or cloud IAM credentials.
  • Executors (Hermes or custom CLI workers) pull leased steps and emit structured verification evidence back to the server.

Network, Privacy & Security Boundaries

  • Designed for intranet, VPC, or sovereign server deployment where source code and credentials remain on operator infrastructure.
  • Secret material is loaded strictly from controlled credential paths at runtime and isolated from LLM prompt logs where configured.

Frequently Asked Questions

Does ZeroOS require a specific cloud LLM provider?

No. The built-in CEO planner calls whichever model endpoint you configure, including OpenAI-compatible APIs, Google Gemini, Anthropic Claude, or private self-hosted models.

Is Hermes required to run ZeroOS?

No for task planning: the built-in CEO talks to your model API directly. Open-source executors such as Hermes run as modular task workers assigned by the control plane.

How do ZeroOS and LongMemOS relate?

ZeroOS coordinates multi-step execution; LongMemOS (formerly MemoryBox 2.0) is the pluggable long-term memory subsystem that lets ZeroOS workers and developer IDEs recall prior decisions from original records.

Can LongMemOS be used without ZeroOS?

Yes. LongMemOS exposes a standard MCP server and local HTTP API so individual developers and teams can connect Claude Code, Cursor, or Codex directly.

Book an Engineering Walkthrough

Share how your team runs coding tools or internal automation today. Only your name and one contact method are required.

Direct Contact · Dalian Fidwell Technology

All consultation records go directly to Fidwell engineering support. We respond during standard business hours (UTC+8).

Email: fidwellservice@fidwell.cn

Tel: +86-411-81981709

Address: Room 1303, Bank of East Asia Tower, No. 7 Renmin Road, Zhongshan District, Dalian, Liaoning, China

Send Inquiry

Information submitted here is stored only for responding to your demo or evaluation request and is never sold or shared with unrelated third parties.