eyeballdocs
Self-hosting

Open source and Cloud boundary

Know exactly which capabilities ship in the repository and which require eyeball Cloud or your own implementation.

Open source

  • canonical capability contracts and 37-toolkit default catalog;
  • provider adapters and execution engine;
  • validation, normalized errors, idempotency, in-memory defaults, and optional Postgres-backed records plus lease-fenced execution/webhook/voice-observer state, durable voice sources, executor AgentStore, and gateway SessionStore;
  • signed webhook endpoint registry, asynchronous delivery engine, delivery log, and verification helper;
  • TypeScript SDK;
  • Streamable HTTP MCP gateway and eyeball.search_tools;
  • Next.js dashboard;
  • EnvCredentialProvider, MockCredentialProvider, and opt-in development vault;
  • separate deterministic provider-mock workspace.

Private Cloud source

  • hosted OAuth authorization and callback endpoints;
  • encrypted end-user token vault and refresh lifecycle;
  • hosted connect/reconnect UI and consent repair;
  • tenancy, project-key lifecycle, audit, usage metering, and billing control-plane APIs.

The private repository implements those control-plane paths in source, but no hosted deployment, managed executor fleet, production scaling/operations layer, or live-provider certification is claimed for 0.2.0.

Bring your own

Self-hosters can implement the exported credential, execution, webhook endpoint, webhook delivery/work/source, job, file, agent, voice-observer, and session-store boundaries, plus their own TLS, identity, authorization, persistence, observability, egress policy, and secret management. The stock stores are in memory unless EYEBALL_DATABASE_URL enables the provided Postgres compositions: executor execution/file/webhook/trigger/usage/agent/observer/source stores and the gateway session/task store, each with its own migration history. Durable observer state is executor-owned and lease-fenced while the polling tasks and network reads remain per process. Trigger polling, rate limiting, toolkit concurrency, TLS, identity, observability, and secret management retain their documented deployment-owned or process-local boundaries.