SlotDock Docs

Local-first MVP reference

This page explains what the public control plane does, what stays local, how the MVP trial works, and which endpoints are exposed for installation, license, promo, module and heartbeat checks.

Worker health Platform site Download page

Boundary

What local-first means

SlotDock keeps business data in the local business environment. Cloudflare is used only as a control plane for installation identity, license state, promo events, module availability, version state, heartbeat and audit visibility.

MVP flow

What the public MVP does

The public flow is simple: open the platform pages, review the docs, register a local installation, call health and module endpoints, check license and notice state, optionally apply promo code prometei, and keep only service heartbeat in the cloud.

Stored in control plane

  • installation_id
  • tenant_id
  • license_status
  • license_notice
  • module_status
  • app_version
  • heartbeat
  • promo_status
  • audit_events

Never uploaded

  • Clients and CRM history
  • Messages and chat transcripts
  • Documents and commercial offers
  • Knowledge bases with business content
  • Medical or financial business records
  • Operational tables used by the local installation
License, promo and offline behavior

Each local installation registers through the control plane and receives trial behavior plus offline grace logic in the local product. The MVP exposes a single static promo code, prometei, which extends trial access by 30 days and is logged only as a service event. Business payloads are not transferred to apply promo or check license state.

Modules and public MVP surface

The control plane can return an allowed module list from D1, while the actual business workflows still execute in the local installation. Public references currently point to SlotWidgets, Agent Chat Secretary, AI Consultant, AI Knowledge, CRM and owner-facing operational modules as examples of the product surface.

Public endpoints
  • /health
  • /api/modules/list
  • /api/installations/register
  • /api/installations/heartbeat
  • /api/license/check
  • /api/license/notice
  • /api/promo/apply
  • /api/update/manifest
  • /api/sync/status
Download and test access policy

The public download page is intentionally a testing and request-access page. It does not promise a public installer that is not yet packaged. When a local installer is ready, the page will describe how to obtain it and how to connect the first local installation to the control plane.