Summary

TapCanvas Pro addresses fragmented long-form AI content creation with a unified, visual workspace. It targets teams and individuals engaged in complex AI pipelines, such as novel adaptations or multi-stage video production, offering a project-centric approach to streamline workflows and asset management.

How It Works

The platform centers on an infinite canvas where users orchestrate text, images, video, and storyboards via nodes and connections. It employs an "Agents Bridge" for AI task execution, supporting multi-model integration (text, image, video) under a unified node protocol. Assets are managed project-specifically, enabling continuous iteration and traceability across long-form creation.

Quick Start & Requirements

Two primary local setup methods are offered:

• Docker Compose: Execute docker compose up -d or ./scripts/dev.sh docker. Requires Docker and Docker Compose.
• Local Source Development: Requires Node.js, pnpm, and PostgreSQL. Install dependencies with pnpm -w install, configure .env files for API and frontend, and start services using ./scripts/dev.sh local or individual pnpm dev:* commands. Official documentation is available within the docs/ directory.

Highlighted Details

• Infinite Canvas Workflow: Visually organize and iterate on content production elements within a single, expandable workspace.
• Agents Pipeline Runs: Facilitates structured, multi-step AI production for projects/chapters, with results saved to asset libraries.
• Integrated Media Pipeline: Image nodes directly inform video generation as first/last frames or reference assets.
• Asset Reusability: Generated media and project assets are easily drag-and-dropped as inputs for subsequent nodes.
• Monorepo Architecture: Frontend, backend API, and Agents CLI managed cohesively in a single repository using pnpm workspaces.

Maintenance & Community

Contact for collaboration via email: beq.li@qq.com. WeChat QR code provided for deployment assistance. No dedicated community channels like Discord or Slack are explicitly linked.

Licensing & Compatibility

Released under Apache-2.0 with a supplementary commercial agreement. Distributing the software as a product to 2+ independent third parties requires written commercial authorization. Internal use by up to five legal entities is permitted without authorization. Modifications or removal of copyright notices are prohibited. Apache-2.0 is permissive, but the supplementary agreement adds distribution restrictions.

Limitations & Caveats

The supplementary commercial agreement imposes significant restrictions on product distribution to third parties, necessitating a paid license beyond internal use or specific revenue-sharing scenarios. No explicit mention of alpha/beta status is present.