What problem does it solve? Deploying third-party open-source suites like Harbor, Dify, or n8n onto a Rainbond platform requires translating upstream Compose files, Helm charts, or installer-generated configurations into correct components, dependencies, storage, and routing, which is error-prone when done manually. ## Core Features & Use Cases - Official Source Acquisition: Fetches and pins deployment inventories from upstream repositories, release assets, charts, and installer templates before touching the platform. - Per-Component Modeling: Maps Compose services or rendered Helm workloads into Rainbond components with ports, environment variables, dependency edges, persistent storage, config files, and probes. - Delivery Verification: Waits for terminal build states, diagnoses failures with a failure-mode playbook, and validates the real external entry with UI or core-flow smoke tests. - Use Case: Ask the agent to deploy Dify on Rainbond; it retrieves the official deployment material, models every component and dependency, deploys, repairs blockers, and confirms the login UI works through the real access URL. ## Quick Start Deploy the open-source suite Harbor on Rainbond and verify its web UI works through the real access address.
