Visual AI Flows. In Your Codebase. Open-source, runs in VS Code.
Integrates with existing TypeScript code.
VSCode Extension ✔️ · Runtime Library ✔️ · Integrates with Existing Code ✔️
Rich Standard Library ✔️ · Visual Debugger ✔️ · TypeScript Support ✔️
Runs directly in your codebase with access to runtime code and existing backend frameworks. Unlike standalone tools, Flyde is integrated as a library into your existing tools and CI/CD pipelines.
Prototype, integrate, evaluate and iterate on AI-heavy backend logic visually. Build backend AI agents, prompt chains, and agentic workflows with a visual interface while maintaining full code control.
A visual extension of TypeScript that bridges the gap between developers and non-developers. Enable your entire team to contribute to backend AI workflow development.
🚀 Flyde 1.0.0 is coming soon! We're working on a complete platform overhaul with improved documentation, comprehensive examples, and a revamped VS Code extension. Stay tuned!
Flyde
is a holistic solution for prototyping, integrating, evaluating and iterating on AI-heavy backend logic. It's a visual extension of TypeScript that runs in-codebase, providing the missing link between developers and non-developers working on backend AI workflows.
Flyde allows you to create visual flows for backend services like AI agents, prompt chains, API orchestration, and agentic workflows - directly integrated with your existing codebase. It includes a VSCode extension and seamlessly integrates with existing TypeScript/JavaScript code.
The easiest way to experiment with Flyde is to visit the online playground, which allows you to create and run flows in the browser.
- Install the VSCode extension
mkdir my-flyde-project && cd my-flyde-project
- Open your project in VSCode
- Command Palette (Ctrl+Shift+P) ->
Flyde: New visual flow
- Check out the Integrating with Existing Code guide to learn how to integrate your flows with your code
-
Product Teams & Developers: Flyde bridges the gap between technical and non-technical team members. Product managers, designers, and backend developers can collaborate on the same visual flows, making complex backend logic transparent and enabling everyone to contribute meaningfully to the development process.
-
Developers Building AI-Powered Backends: If you're dealing with complex prompt chains, AI agents, or multi-step backend AI workflows, Flyde provides a more manageable way to build, debug, and maintain these systems while keeping everything in your codebase.
-
Teams Seeking Visual Clarity: Whether you're prototyping new backend features, managing complex business logic, API orchestration, or simply looking for a better way to document and understand your backend application flow, Flyde's visual approach helps you see the big picture while maintaining the power of code.
Flyde is an open-source project. We are committed to a fully transparent development process and highly appreciate any contributions. Whether you are helping us fix bugs, proposing new features, improving our documentation, or spreading the word - we would love to have you as a part of the Flyde community. Please refer to our contribution guidelines and code of conduct.
-
Bug Report: If you see an error message or encounter an issue while using Flyde, please create a bug report.
-
Feature Request: If you have an idea or if there is a capability that is missing, please submit a feature request.
-
Documentation Request: If you're reading the Flyde docs and feel like you're missing something, please submit a documentation request.
Not sure where to start? Join our discord and we will help you get started!
Check out the official website at https://flyde.dev for more information.
Everything needed to run a Flyde file is MIT-licensed. That includes:
@flyde/core
@flyde/resolver
@flyde/runtime
@flyde/stdlib
The UI library and other nodes of the toolkit are GNU AGPLv3 licensed.
In other words, using Flyde flows in your software is permitted without any limitation. However, if you use Flyde's visual editor in your own work, it must be open-sourced as well. More about GNU APGLv3 here