Discover and explore top open-source AI tools and projects—updated daily.
abhinavkale-devBuild and monitor self-hosted workflows visually
New!
Top 94.1% on SourcePulse
Fynt is a self-hostable, open-source platform for building, running, and monitoring multi-step workflow automations using a visual node editor. It targets developers and power users seeking a flexible, on-premises solution for complex task orchestration, offering a visual interface to chain diverse operations, from AI model interactions to data synchronization and event handling.
How It Works
Fynt employs a visual node-based architecture where users construct workflows by connecting pre-defined nodes representing triggers, AI models, integrations, and logic. The execution engine distributes tasks via a job queue (BullMQ on Redis), streams live run updates to the browser over WebSockets, and encrypts all sensitive credentials at rest using AES-256-GCM. This approach enables complex, distributed automation pipelines with real-time visibility.
Quick Start & Requirements
.env.docker.example to .env.docker and fill required secrets, then run docker compose up --build. Services are accessible at http://localhost:3000 (Web).pnpm install, copy .env.example to .env and configure database (PostgreSQL), Redis, authentication, and encryption keys. Run migrations (pnpm --filter @repo/prisma exec prisma migrate dev) and seed data (pnpm db:seed). Start services using pnpm --filter @fynt/web dev (web-only) or pnpm dev (full self-host).Highlighted Details
Maintenance & Community
Information regarding specific contributors, community channels (e.g., Discord, Slack), or a public roadmap is not detailed in the provided README.
Licensing & Compatibility
The README does not explicitly state the project's license. This omission presents a significant adoption blocker, as the terms for use, modification, and distribution are unclear, particularly concerning commercial applications or linking with closed-source software.
Limitations & Caveats
The "Web only" deployment mode allows workflow building but blocks execution, requiring a "full self-host" setup for actual automation runs. Enabling automation in production necessitates setting FYNT_ENABLE_AUTOMATION_IN_PRODUCTION=true. The lack of a specified license is a critical caveat for any potential adoption.
1 day ago
Inactive
temporalio
activepieces