Skip to content

Minimum hosted-capable control plane #2

Description

@mathaix

Goal

Reduce the repo to a minimum control plane that can run locally or be hosted by an operator, while keeping commercial hosted-service policy out of public core.

Rubric gates

  • Control-plane dependencies are explicit and documented.
  • Deployment profiles separate local, BYO-host, and hosted operator modes.
  • Core APIs manage accounts, machines, hosts, credentials, sessions, and routing without assuming OpenClaw Machines commercial billing.
  • Hosted-only infrastructure integrations are optional adapters, not required for core startup.

Starting points

  • backend/cmd
  • backend/internal/config
  • backend/internal/api
  • backend/internal/store
  • docs/designs/deployment-profiles.md
  • docs/configuration.md

Expected output

  • A minimal documented startup profile for local/operator-hosted control plane.
  • Config flags or profile structure that makes hosted-only services optional.
  • Removal or isolation of hard dependencies on commercial hosted settings in startup paths.
  • Tests around config/profile behavior where possible.

Non-goals

  • Do not implement billing.
  • Do not add SaaS admin features.
  • Do not move private overlay behavior into public core under different names.

Metadata

Metadata

Assignees

No one assigned

    Labels

    core-control-planeMinimum hosted-capable control planereadinessPublic-core readiness work

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions