Open-source AI workflow automation with deterministic execution, MCP tools, evidence, and replay.
Website | Docs | Blog | PyPI | YouTube | Discussions
pip install "flyto-core[browser]"
playwright install chromium
flyto recipe competitor-intel --url https://github.com/pricingFlyto2 is for builders who need agents to finish real browser and data work, not just suggest code. Workflows are explicit, every step emits trace and evidence, and failed runs can resume from the step that needs attention.
The generated Flyto2 Core catalog currently contains 466 registry-backed modules across 85 categories. The count comes from the runtime registry and is checked in CI, rather than maintained as marketing copy.
workflow -> deterministic steps -> trace -> evidence -> replay
| You want to... | Start here |
|---|---|
| Run YAML recipes, browser automation, MCP tools, queues, triggers, trace, evidence, and replay | flyto-core |
| Give a coding agent dependency, context, impact, security, and documentation gates | flyto-indexer |
| Self-host a source-available security warroom and inspect its public contracts | flyto-warroom |
| Read installation, API, configuration, recipe, and operations guides | docs.flyto2.com |
| Compare Flyto2 with n8n, Zapier, Make, Playwright, or LangGraph | flyto2.com and the Flyto2 blog |
| Ask a question, propose an integration, or share a workflow | Flyto2 Discussions |
Agents can select tools and compose workflows, but the execution layer keeps inputs, outputs, retries, timing, evidence, and replay explicit. That makes a failed step debuggable and a successful run repeatable.
Recipes can navigate, click, type, extract structured data, capture desktop and mobile screenshots, measure Web Vitals, create PDFs, and write reports. The artifacts belong to the run instead of disappearing into an opaque chat.
Flyto2 Indexer gives coding agents local repository context, dependency graphs, impact analysis, secret and taint checks, documentation coverage, and strict completion gates. It does not upload repository source for static analysis.
flyto-core and flyto-indexer are Apache-2.0 projects. Other repositories may
use MIT, source-available, or commercial terms. Check each repository's
LICENSE before use; the organization profile does not override it.
id: competitor_intel_v1steps:
- id: launchmodule: browser.launchparams: { headless: true }
- id: visitmodule: browser.gotoparams: { url: "{{target_url}}", wait_until: networkidle }
- id: capturemodule: browser.screenshotparams: { path: competitor.png, full_page: true }
- id: closemodule: browser.closeStart with the built-in recipes for competitor intelligence, full website audits, screenshots, SEO checks, and structured extraction. Use the module catalog when you need lower-level control.
| Repository | Responsibility |
|---|---|
| flyto-core | Python execution engine, CLI, YAML recipes, browser runtime, modules, MCP, evidence, and replay |
| flyto-indexer | Local code-intelligence CLI and MCP server for context, impact, dependency, security, and quality gates |
| flyto-i18n | Shared locale contracts and translation validation |
| flyto-design-tokens | Shared visual tokens and generated CSS/JavaScript references |
| flyto-plugins-js | JavaScript plugin SDK and integration contracts |
| Repository | Responsibility |
|---|---|
| flyto-warroom | Generated source-available Warroom CE distribution, public contracts, installer, and release evidence |
| flyto-cloud | Hosted automation and application surfaces |
| flyto-code | Security cockpit frontend and product interaction contracts |
| flyto-app | Flutter mobile command-center client |
| flyto-cortex | Knowledge workspace frontend |
| flyto-data | Data-product API and management surface |
| flyto-docs | Public technical documentation |
| flyto-landing-page | Product and comparison pages at flyto2.com |
| flyto-blog | Technical articles, release stories, and implementation notes |
| flyto2 | Deprecated legacy release and security-routing shell; not the active desktop source |
The remaining repositories hold engine services, blueprints, AI helpers, commercial extensions, admin tools, release memory, and editor integrations. Each repository README states its own authority and license.
- Ask usage and design questions in Discussions.
- Pick a scoped task from good first issues.
- Share a recipe, MCP setup, integration, or Warroom CE lab through the organization showcase template.
- Read
CONTRIBUTING.mdbefore changing shared contracts. - Report vulnerabilities privately through the repository Security tab or
security@flyto2.com, never through a public issue.
- Community: Flyto2 Discussions
- Documentation: docs.flyto2.com
- Partnerships and press:
hello@flyto2.com - Security:
security@flyto2.com
Built in Taiwan. License terms are declared per repository.