ViewComfy
ViewComfy is an open-source TypeScript tool that converts ComfyUI workflows into deployable web applications with drag-and-drop form configuration. It supports multiple workflows, various input types, and can be deployed locally, on serverless infrastructure, or via ViewComfy Cloud with built-in user management and analytics.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | ViewComfy/ViewComfy |
| Owner | ViewComfy |
| Primary language | TypeScript |
| License | AGPL-3.0 — OSI-approved |
| Stars | 652 |
| Forks | 82 |
| Open issues | 12 |
| Latest release | v.0.3.23 (2026-01-08) |
| Last updated | 2026-03-19 |
| Source | https://github.com/ViewComfy/ViewComfy |
What ViewComfy is
A Next.js-based application that ingests ComfyUI workflow_api.json files, generates configurable input forms, and exposes workflows via API endpoints. Supports serverless deployment patterns, Clerk-based authentication, Docker containerization, and environment-driven feature toggles for playground mode and user management.
Get the ViewComfy source
Clone the repository and explore it locally.
git clone https://github.com/ViewComfy/ViewComfy.gitcd ViewComfy# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Node.js v20.18+ required; npm-based dependency management with standard Next.js toolchain. Local development straightforward but serverless deployment requires external hosting or ViewComfy Cloud account.
- Environment variables critical: VIEWCOMFY_CLIENT_ID/SECRET for cloud deployment, NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY/CLERK_SECRET_KEY for user auth, VIEW_COMFY_FILE_NAME for multi-config scenarios.
- ComfyUI server setup (local or cloud) must precede ViewComfy app configuration; workflow_api.json extraction and view_comfy.json generation are manual prerequisites.
- Playground Mode (VIEW_MODE) toggles between editor and production UI; consider this a hard architectural choice with implications for feature exposure.
- Docker build args must align with deployment environment (user management, Clerk keys); misalignment causes runtime feature degradation.
When to avoid it — and what to weigh
- Proprietary Commercial Use Without Legal Review — AGPL-3.0 requires derivative works and applications built on ViewComfy to be released under AGPL-3.0 or proprietary use may violate the license. Requires legal review before deployment in closed-source commercial products.
- Complex Real-Time Streaming or Long-Poll Requirements — No evidence of WebSocket or streaming support in the codebase; architecture appears request/response-oriented. Unsuitable for real-time interactive feedback loops.
- Enterprise Security and Compliance Mandates — No mention of SOC 2, HIPAA, PCI-DSS, or FedRAMP compliance. Reliance on Clerk for auth and ViewComfy Cloud for hosting introduces third-party dependencies. Requires security audit before enterprise deployment.
- Non-ComfyUI Workflow Ecosystems — Purpose-built for ComfyUI workflows; integration with other generative AI frameworks (e.g., LangChain, Hugging Face Inference) appears limited or absent.
License & commercial use
ViewComfy is licensed under AGPL-3.0 (GNU Affero General Public License v3.0). This is a strong copyleft license requiring that any modifications, derivative works, and networked applications using ViewComfy must be released under AGPL-3.0 or compatible terms, with source code made available to users.
AGPL-3.0 is NOT a permissive OSI license for proprietary commercial use. Any commercial product built on or derived from ViewComfy must comply with AGPL-3.0 obligations: release source code, allow user modification, and license under AGPL-3.0. Proprietary closed-source commercial deployment likely violates the license. Legal review REQUIRED before commercial use. ViewComfy Cloud (hosted service) may have separate terms; review separately.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
ViewComfy does not independently manage user credentials; Clerk integration required for auth. No security audit, penetration test results, or vulnerability disclosure policy mentioned. AGPL-3.0 source code is public; review recommended before deployment. Environment variables (API keys, Clerk secrets) must be managed securely (never commit to repo). ViewComfy Cloud infrastructure security posture unknown; third-party audit required. Inference workloads on serverless platforms inherit that platform's security model.
Alternatives to consider
Gradio (HuggingFace)
Python-first, built for Hugging Face models; broader ML ecosystem support. Permissive Apache 2.0 license. Steeper learning curve for TypeScript teams; less workflow-native UI customization.
Streamlit
Rapid Python prototyping with Pythonic DSL; large community. Permissive Apache 2.0 license. Python-only; requires separate deployment infrastructure; less suitable for ComfyUI-specific workflows.
Custom Next.js + Vercel/AWS deployment
Full control, no license constraints, mature deployment ecosystem. Requires significant engineering effort; no out-of-the-box workflow abstraction; higher time-to-market.
Build on ViewComfy with DEV.co software developers
Before adopting ViewComfy, confirm AGPL-3.0 compliance with your legal team, review security posture for production, and test serverless integration patterns with your infrastructure. Contact us for enterprise deployment guidance.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
ViewComfy FAQ
Can I use ViewComfy in a closed-source commercial product?
Do I need to run ComfyUI locally?
What happens if ViewComfy Cloud goes down or discontinues?
Is ViewComfy suitable for enterprise production workloads?
Custom software development services
From first prototype to production, DEV.co delivers software development services around tools like ViewComfy. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across ai frameworks and beyond.
Evaluate ViewComfy for Your AI Workflow Deployment
Before adopting ViewComfy, confirm AGPL-3.0 compliance with your legal team, review security posture for production, and test serverless integration patterns with your infrastructure. Contact us for enterprise deployment guidance.