Skip to content
Frond

Roadmap

Near term

  • Real-time collaboration (InfiniPaint-style lobbies): presence, live strokes, and “jump to player” over a WebSocket/AppSync channel; the document model and DynamoDB change stream are already shaped for it.
  • Lasso refinement: partial-path eraser splitting and lasso rotation.
  • Palette sync to the account.
  • Status page (status.<domain>) with synthetic canaries.
  • Telemetry — privacy-preserving, opt-in error reporting only (never canvas content).

Open-source transition

The repository starts private (see LICENSE). The plan, in order:

  1. Legal review of dependencies and the dual-license strategy (engine + infra: Apache-2.0; brand assets: reserved).
  2. Publish the repo with the placeholder brand; keep infra/config as the only per-deployment customization (see Self-hosting).
  3. Accept community contributions behind the standard process (CONTRIBUTING.md, DCO or CLA).

Brand

“Frond” is a working title. The brand name, domains, and legal entities will be assigned before public launch; all of it is configuration, not code.