MarketingOS
DEOpenCLAW setup

MarketingOS addons / OpenCLAW + Hermes

Your runtime is running. Now teach it marketing.

MarketingOS does not place a second SaaS beside your setup. Addons move into an existing OpenCLAW or Hermes installation. They use its models, compute, sessions and tools. Model choice, compute load and deployment remain the responsibility of your runtime.

The first discipline is functional today: SEO/GEO.
Explore SEO/GEOReview installation
Addon index
  1. 01SEO/GEOFunctional
  2. 02Social MediaPlanned
  3. 03Lifecycle/CRMPlanned
  4. 04Paid PerformancePlanned
  5. B1Growth BundlePlanned
  6. A1Agency PackPlanned

Why addons

The expensive infrastructure already exists.

An OpenCLAW or Hermes instance already carries model access, compute, sessions, memory, tools and secrets. A conventional SaaS would rebuild much of that and pull the operation out of your environment. MarketingOS starts after the engine. It installs specialist roles, operating workflows and controls into the runtime you already manage.

Stays with you

  • Model and provider choice
  • Compute and sessions
  • Data and workspaces
  • Runtime cost and operation

Comes with the addon

  • Specialists and role contracts
  • Business context
  • Evidence and QA
  • Approvals and receipts

MarketingOS grows one discipline at a time, without becoming an opaque platform.

01 / SEO/GEOWorks today

Search was the hardest honest place to begin.

SEO and GEO expose empty agent promises quickly. A technical recommendation needs a crawl. A content decision needs search demand. A GEO claim needs repeatable observation. A change needs approval and later measurement. A text generator cannot imitate that chain for long. The first addon therefore forces expertise, evidence and operation into one workflow.

01

Technical SEO

Recurring website crawls, onpage health, canonicals, indexation signals, structured data, internal links and prioritized findings.

02

GEO and answerability

Topic coverage, source quality, answerability and repeatable citation observation with uncertainty kept visible.

03

Demand and content

Search demand, content gaps, briefs, editorial quality, brand and entity context from the same workspace.

04

Measurement and QA

Measurement plan, baseline, Search Console and Bing evidence, receipts, observation windows and separate outcome review.

OpenCLAW registers one orchestrator and eleven specialist agents. Hermes installs the same twelve roles as directly callable skills and adds one team bundle. Hermes runtime parity remains partial.

SiteOne is part of the addon

The crawler comes with it. It is not optional.

MarketingOS installs SiteOne 2.5.1 as a managed shared tool. Every role may use it to inspect technical sources. That enables recurring onpage health crawls, bounded external checks and source backed Technical SEO evidence without requiring another crawler service.

  1. 01

    The platform package includes the pinned SiteOne version and its license file.

  2. 02

    The first run checks path, version and health. A normal installation cannot skip the crawler.

  3. 03

    Every runtime role receives the same documented crawl command instead of building a shadow solution.

  4. 04

    A crawl proves a technical state. It does not yet prove rankings, clicks or business impact.

Read the installation flow

Two runtimes, one operating model

MarketingOS runs in your instance. Model traffic remains the job of your runtime.

The native installer works in a dedicated MarketingOS namespace, writes a backup before changes and records ownership and removal in a manifest. It replaces neither OpenCLAW nor Hermes and does not move model billing to MarketingOS.

Leading path

OpenCLAW

Twelve named agents work in separated MarketingOS workspaces. Model, sessions, memory, secrets and channels are inherited from OpenCLAW. A real orchestrator turn and one Technical SEO source assignment are verified.

OpenCLAW setup
Verified partial path

Hermes Agent

Twelve direct skills, dedicated slash commands and one team bundle are installed. Delegation runs in native leaf sessions. Persistent named specialist agents are not a Hermes promise. That difference remains visible.

Hermes setup

The next disciplines

What follows remains visibly unfinished.

These entries are target directions, not products for sale. Scope, order, licensing and release dates remain open. We show them so the direction of the system can still be challenged.

02

Social Media

A target direction for planning, publishing calendars, channel voice, approvals and measurement across several networks. Supported platforms and connectors are not fixed yet.

Planned. Not for sale.
03

Lifecycle/CRM

A target direction for lifecycle segments, events, sequences, CRM handoffs and consent rules. The data model and connector scope remain open.

Planned. Not for sale.
04

Paid Performance

A target direction for research, campaign briefs, creative variants, measurement and strict budget controls. MarketingOS does not launch campaigns or spend ad budget today.

Planned. Not for sale.
B1

Growth Bundle

A planned combination of released specialist addons. Its exact modules and licensing have not been decided.

Planned. Not for sale.
A1

Agency Pack

A target direction for separated client contexts, roles, approvals and audits. Tenant isolation is a security gate and not a product for sale today.

Planned. Not for sale.

SEO/GEO is the product today. Everything else is a direction we are not selling yet.

To judge the current state, read the native installation path and the technical evidence. Both also state what has not been proven.